Invalid delta coordinate...

[mhackney]

Ok, this one has me stumped. I turned on my machine this morning and warmed up the hot end and bed in Repetier Host. I then loaded a gcode program that I print literally everyday. When I hit "Run" I got this in the log panel:

Code: Select all

> 9:56:24 AM: N166 G28 *50
> 9:56:24 AM: N167 M104 S195 *72
> 9:56:24 AM: N168 M190 S50 *114
> 9:56:24 AM: N169 M109 S195 *75
> 9:56:24 AM: N170 G92 E0.0000 *79
> 9:56:24 AM: N171 T0 *29
> 9:56:24 AM: N172 M104 S195 *76
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:28 AM: Warning:Invalid delta coordinate - move ignored
> 9:56:28 AM: N174 G92 E0.0000 *75
> 9:56:29 AM: N175 G1 X45.14 Y22.31 Z1.20 E0.0000 F12000.00 *107
> 9:56:29 AM: N176 G1 X45.14 Y22.31 Z0.20 E0.0000 *18
> 9:56:29 AM: N177 G1 E3.0000 F1200.00 *58
> 9:56:29 AM: N178 G1 X44.83 Y22.57 E3.0267 F300.00 *14
< 9:56:29 AM: Warning:Invalid delta coordinate - move ignored
< 9:56:29 AM: Warning:Invalid delta coordinate - move ignored

I spent some time debugging - rebooting the RAMBo, shutting down / starting RH, loading a different known good gcode file and had the same problem. Then I switched to using my Raspberry Pi with Octoprint and again have the same problem. The RAMBo is frozen when this happens and I have to pull the USB power to get it to cycle.

I thought maybe my firmware had somehow got corrupt so I re-uploaded Repetier. No luck, still getting this problem.

I an jog the printer in Z but if I try any X or Y moves from RH (either using buttons or entering gcode in the entry field) I get this Invalid delta coordinate warning and no movement. Something odd is going on. Anyone seen this or have any ideas on what else to check?

[Eaglezsoar]

What happens if you put the same GCode on an SD card?

[mhackney]

Same problem. Any movement in X or Y results in this warning and no movement. I can jog in Z all day long.

[guanu]

you said you re-uploaded the firmware, but did you wipe the eeprom before doing so? in aruduino go to file -> examples -> EEPROM -> eeprom_clear upload that first, then re-upload the firmware and see if it still has the problem, you may have an error in the eeprom, and that remains when you re-upload firmware...

Guanu

[mhackney]

No, didn't think of that, thanks. I'll give that a shot now.

[mhackney]

Thanks guano, clearing the EEPROM did it. Interestingly, I had looked at the EEPROM earlier but everything displayed was normal looking. There must be other stuff in there.

cheers,
Michael

[Eaglezsoar]

Thanks guano, clearing the EEPROM did it. Interestingly, I had looked at the EEPROM earlier but everything displayed was normal looking. There must be other stuff in there.

cheers,
Michael

Even though we are not sure why, when the computer is broken, reboot. When the printer is broken clear EEProm. Question, after you clear the EEProm do you have to write the configuration to the
EEProm or should you let it build up data naturally.

[mhackney]

I'm not sure of your question Eagle? I took a screen capture of the EEPROM window (Mac does not create a text file of it). I then updated my Configuration.h to capture everything, compiled and uploaded with EEPROM enabled. That put all of my values back in the EEPROM ready to go.

[Eaglezsoar]

I'm not sure of your question Eagle? I took a screen capture of the EEPROM window (Mac does not create a text file of it). I then updated my Configuration.h to capture everything, compiled and uploaded with EEPROM enabled. That put all of my values back in the EEPROM ready to go.

That answers my question, I didn't word it very well but your answer was the info I was looking for. Thanks and I am glad you are working again. I was feeling the panic clear down here.

[mhackney]

Yes, I was a little panicked! A problem like this cuts into production!

[guanu]

yeah, if he didnt take down all the data from the eeprom, the only thing you really need to do is the calibration process again, unless something else was changed from when it was built...

Guanu

[Eaglezsoar]

Yes, I was a little panicked! A problem like this cuts into production!

And with your busy season coming up you don't need downtime. Have a good one.