Auggie becomes unresponsive and has to be restarted

[Heise IT-Markt [Crawler]]

I have realized I have to run the ribbon cable from the test port to the G540 through a jumper box to get the pin-outs right. Meanwhile I have just been mucking about with Augie and the PoKeys to get the feel of things first. I find Augie "goes away" often and must be restarted. Of course I have no idea what I am doing. Somebody who knows what buttons they "should" be pushing  would likely not do some of the things I do.

I just came back to the machine after typing the above and found it would not jog.... I restarted Augie and the tool-path display did not fill in until I passed the mouse cursor over it. And no jogging or response to commands. Restarted again and everything came up normal. Now its gone again...  I'll restart aug... yep all fixed.. I wait a bit and see what happens. Yep had to restart a few more times..

I'll keep on playing

[Heise IT-Markt [Crawler]]

By the way I am only connected with USB I have not gotten around to connecting the Ethernet. Win 10/64...

[Heise IT-Markt [Crawler]]

It was working fine so I stopped and read a news article... then when a came back it was toast again.

OK after deleting many lines of the log file I got it down from over 6 megs to something I can upload. I see now the error log is over 11 megs, time to shut Augie down, I was not doing anything and its still logging the same error.

[Heise IT-Markt [Crawler]]

Just started it, made a couple of moves and the just checked the log now and then... and it took off.

I'll upload this one and call it a day.

[BobL]

Joemac;

I believe you must use the Ethernet plug of the pokey found on 56 or 57's, not USB.. I suspect this is where problems come from in your case.


Bob

[ArtF]

Hi Joe:

  Actually, ethernet or USB should be fine, but I havent tested USB in several versions. That error datum is showing a serious problem in your transmissions, Ill investigate, thx for the notification. I use net on the 57, so Ill switch to a usb device. Was this the 57 your using?

Thx
Art

[ArtF]

Sorry Joe:

I see its the 57.. Im running tests on a 56U, its been runnign a spiral cut for awhile, but Ill look into the error
to see what it means, likely I pushed the envelop a bit far.

Art

[ArtF]

Joe:

Thx for that report. Ill try to get a usb long enough to plug my 57 in on it, my 56u seems to run fine. Im probably messing up somewhere,
but its reports like that which will point me to it. After the holidays, I'll check the error datum with the guys at Pokeys to see
if it helps pinpoint anything.. When you see a line like this..

Error datum:
58:52:919  AA 85 04 00 00 00 B1 E4 00 00 00 00 00 00 00 00 00 00 01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 7D 80 0A 01 00 00 61
 
  it basically means the Pokeys reset itself beacuse it became confused. Ill switch the system responce to disconnect so you wont seem locked up.. it will stop the error from repeating and filling your log, which Ill be making more selective shortly..

Thx
Art

[Heise IT-Markt [Crawler]]

I switched it over to Ethernet and all seems to be fine Art. I went out to run some errands and left Auggie sitting there doing nothing. When I got home the screensaver had timed out and shut off the monitors and somewhere along the line it triggered the estop, but just reset the estop and all was well. Of course if I was running an actual machine I would have screensaver turned off. USB is the problem. And yes it is a PoKeys57CNC.

[ArtF]

cool , thx Joe,

  I'll shcedule a check to see if I can find that error just in case a person wants USB

Art