GearHeads Forum

26ms is the worst there is only the pokeys and computer are communicating, there is a network adapter fault what's a win10 thing, something is missing that's all it says.

so for now to I can work out what is missing Ethernet is out.

there is a pokeys update to do and auggie I will run it again after that.

Auggie shows no problems

Dan:

It still possible its Auggie, in fact the facts make it seem likely.. If Mach3 runs OK, then Auggie should as well,
but though Im not seeing it, its possible your system is experiencing a slowdown I havent yet found. It does
try to check, the Diags tab Anomolies shows any time the filler thread is missed by more than 100ms.. yours is zero,
then theres a "bog" counter, that will spit in the log if it sees the planning isnt gotten to very 80ms or so, and finally,
in todays, theres an auto Jog Kill if more than 80 ms goes by without the jog planner being called. So if it isnt stopping job, and theres now count, Im still stumped.. but still looking. Eventually we'll find it, could be near anything, Auggie is pretty young..

Art

I will do the update tonight post back if there is anything different, I will run the roadrunner again see if it crashes in the middle of it.

and double check M3 on Ethernet after update

Dan:

  Ill be updating again tomorrow anyway, this version is a bit buggy in spindle handling..

Art

it's a little bit better 21 instead of 26 ms it's patchy it wont happen for a minute then it will go ruff for a bit then come right, M3 is fine, pokeys is fine. it's to hot so I have given up for the night 33 degrees 

33 here too. with a foot of snow on the ground..

  I have a buffering test version, Ill upload it in a few minutes and leave it up all day to
see if if quiets your motors any, it just reduced buffer traffic, dont think it will help, but
yanvrno..

Art

Thanks for the input DanL, I'll keep that in mind when time comes to buy. I also tried Auggie latest release last night Art, had no issues with the 80ms trigger when jogging. Nothing longer than 0.010 in Wireshark for my net either.  I see another pokey upgrade version is available, will attempt that today, see how it goes.


Cheers
Bob

Thx guys..

  Curious.. it may be computer, I felt constrained in Mach3 to keep overhead low ,in Auggie Im pushing
the envelope pretty hard.  Ill give some thought as to how to test thatheory.. I have triggers that check for it that arent going off for you so I'm kinda stumped as to cause at this point..

Art

I will test soon I got to drop my son of to granddad they have a project on.

Its a old laptop I am using, it ran fusion360 fine what needs 1 gig of graphics it only has 1/2 a gig.

I will try my gaming laptop it's fast.

no improvement but I get this error now

57:8:748  Script complete,end wait on thread.
57:8:748  OverSpeed: GLine:2, s0:0.0000 s1:0.0000 d:0.2000 t:1.#INF
57:8:748  On Stop called.
57:8:748  On Stop called.
57:8:748  Disabling Control via EStop button
57:8:748  On Stop called.
57:8:748  --System -- System Disabled. 
57:8:748  Spindle speed zeroed 
57:8:748  Disabling Control via EStop button
57:8:748  On Stop called.
57:8:748  --System -- System Disabled. 
57:8:748  Spindle speed zeroed 
57:8:763  Motion Disabled
57:8:763  Clearing Motion buffer of 5 entries
57:8:763  On Stop called.
57:8:763  Disabling Control via EStop button
57:8:763  On Stop called.
57:8:763  --System -- System Disabled. 
57:8:763  Spindle speed zeroed 
57:12:826  Show log initiated