Re: getting the 57cnc to work with G540

DanL · Post by **DanL** » Thu Jan 21, 2016 4:13 pm

found another big problem Ethernet is bad, it runs ruff as gut when using the ethernet not changing anything just cables. going back to USB it comes good.

Bob a test for ya USB compared to ethernet.

Post by **ArtF** » Fri Jan 22, 2016 1:54 am

Hi Dan:

  Bobs 57E only has Ethernet, no USB on board.

Its possible your Ethernet is boggy, I had trouble on mine
until I shut down my router monitor for example.

Does the time anomalies DRO in the diags panel
show a count while you run in E Net? If so there is a way to
troubleshoot why, but Ill have to do a video on it to show how.
E Net is actually faster generally, and should give better performance,
but it does rely on the network not to be bogged down with address
resolution calls. Checking the time anomalies is one way to check if your network
needs some tuning.. it should read 0.

A time anomaly is a time period where your network locked up for
more than 100ms..

Art

BobL · Post by **BobL** » Fri Jan 22, 2016 3:57 am

Hi;

Art's right, I do not have USB on the 57E, only Ethernet..  It's an interesting problem that's for sure, why it only acts up on some boards and not others?  Is it possible to monitor the network going to one of these Pokey's via one computer while using another to repeat these tests? Could it reveal maybe something?

Bob

DanL · Post by **DanL** » Fri Jan 22, 2016 9:30 am

it jumps from 0 to 15ms I was hoping that ethernet would be faster and better, it's meant to be. it could be a win10 fault it was hard enough getting it going in first places.

a vid would be good I don't mind doing test's my back is out so I am stuck at home need something useful to do.

Bob you should ask if you can try the new 57CNC out on Auggie, I only know there is a new one don't know if it's the one I have or newer.

DanL · Post by **DanL** » Fri Jan 22, 2016 2:36 pm

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

Post by **ArtF** » Fri Jan 22, 2016 3:30 pm

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

DanL · Post by **DanL** » Fri Jan 22, 2016 5:30 pm

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

Post by **ArtF** » Fri Jan 22, 2016 5:41 pm

Dan:

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

Art

DanL · Post by **DanL** » Fri Jan 22, 2016 8:06 pm

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 

Post by **ArtF** » Sat Jan 23, 2016 2:03 am

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

BobL · Post by **BobL** » Sat Jan 23, 2016 4:27 am

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

Post by **ArtF** » Sat Jan 23, 2016 6:06 am

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

DanL · Post by **DanL** » Sat Jan 23, 2016 8:42 am

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.

DanL · Post by **DanL** » Sat Jan 23, 2016 10:23 am

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

Post by **ArtF** » Sat Jan 23, 2016 11:18 am

Dan:

Was that an arc move it did that overspeed detection on?

(Looks like your spindle code is working at any rate..

Art

GearHeads Corner