G32 Error on Kossel (Delta)

Other_Dave

After recently re-flashing firmware with Repetier .92 on my Delta I went to autolevel (G32) and start in to some basic calibration stuff again when I hit this brick wall. I noticed that it was giving me an Error:ng byte early in the command but it kept going like there was no issue. Then after a few probes around the center (not using a grid but oddly probing two spots adjacent to each other near the center) it would "pause" the print job. After I unpaused, it kicked a whole bunch more errors and I'm pretty sure just thought it had plowed in to the bed so it wouldn't move until I reset it. Log to follow:

--------------------------------

18:02:02.702 : OpenGL version:4.5.0 - Build 23.20.16.4973

18:02:02.703 : OpenGL extensions:GL_3DFX_texture_compression_FXT1 GL_AMD_depth_clamp_separate

18:02:02.703 : OpenGL renderer:Intel(R) HD Graphics 530

18:02:02.703 : Using fast VBOs for rendering is possible

18:02:05.315 : Printer reset detected - initializing

18:02:05.329 : start

18:02:05.329 : Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000

18:02:05.591 : Free RAM:1366

18:02:05.591 : Autoretract:0

18:02:05.593 : X:0.00 Y:0.00 Z:0.000 E:0.0000

18:02:05.594 : SelectExtruder:0

18:02:05.606 : FIRMWARE_NAME:Repetier_0.92.9 FIRMWARE_URL:https://github.com/repetier/Repetier-Firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Delta EXTRUDER_COUNT:1 REPETIER_PROTOCOL:3

18:02:05.606 : Printed filament:137.47m Printing time:1 days 6 hours 11 min

18:02:05.606 : PrinterMode:FFF

18:02:05.622 : X:0.00 Y:0.00 Z:0.000 E:0.0000

18:02:05.622 : DebugLevel:6

18:02:05.622 : SelectExtruder:0

18:02:05.622 : Begin file list

18:02:05.623 : End file list

18:02:05.624 : DebugLevel:6

18:02:05.625 : SelectExtruder:0

18:02:10.699 : SelectExtruder:0

18:02:10.706 : X:0.00 Y:0.00 Z:300.000 E:0.0000

18:02:22.669 : SelectExtruder:0

18:02:22.675 : X:0.00 Y:0.00 Z:300.000 E:0.0000

18:02:22.678 : Error:ng byte

18:02:31.638 : Z-probe:7.49 X:0.00 Y:0.00

18:02:34.645 : Z-probe:7.48 X:0.00 Y:0.00

18:02:37.797 : Z-probe:7.56 X:4.30 Y:0.00

18:02:39.305 : plane: a = NAN b = NAN c = NAN

18:02:39.308 : Transformation matrix: NAN NAN NAN NAN NAN NAN NAN NAN NAN

18:02:39.309 : CurrentZ:NAN atZ:5.00

18:02:39.310 : Z after rotation:5.00

18:02:39.310 : Printer height:NAN

18:02:39.312 : Error:A hit floor

18:02:39.313 : Info:Autoleveling enabled

18:02:39.313 : Error:G32

18:02:39.314 : X:NAN Y:NAN Z:NAN E:0.0000

18:02:39.316 : Info:Autoleveling disabled

18:02:39.343 : RequestPause:Homing failed!

18:02:39.346 : Error:A hit floor

18:02:39.346 : Warning:Invalid delta coordinate - move ignored x:0 y:0 z:2147483548

18:02:39.346 : Warning:in queueDeltaMove to calculateDeltaSubSegments returns error.

18:02:39.346 : Warning:moveRelativeDistanceInSteps / queueDeltaMove returns error

18:02:39.346 : Error:A hit floor

18:02:39.348 : SelectExtruder:0

18:02:39.348 : X:0.00 Y:0.00 Z:-21474836.000 E:0.0000

18:02:39.348 : Info:Autoleveling enabled

18:02:46.470 : Error:isPositionAllowed

18:02:46.472 : X:NAN Y:NAN Z:NAN E:0.0000

18:02:46.473 : Error:isPositionAllowed

18:02:46.473 : X:NAN Y:NAN Z:NAN E:0.0000

18:02:46.476 : Error:isPositionAllowed

18:02:46.477 : X:NAN Y:NAN Z:NAN E:0.0000

--------------------------------

I've tried returning my EEPROM to default and nothing works. Other commands seem to work fine but and I can heat things up, cool them down, etc.

Repetier

Disable some languages for lcd to reduce text usage. If you are over 64kb usage you will start getting wrong messages and also other things can go wrong.

NAN is Not a Number so seeing it means you operate with illegal numbers. Most likely eeprom not having meaningful content. Try uploading with different EEPROM_MODE to force reinitialization.

Other_Dave

I have already deleted all languages in firmware except for English (preferred language) and still receive the error.

I'm not sure I understand what operating "with illegal numbers" means. I'll try an old EEPROM set I saved from an old firmware boot but I don't see how that would help unless the problem itself was EEPROM related, which from your earlier comment, it's not.

Repetier

Try different EEPROM_MODE first. Uploading old eeprom maps from different firmware versions can also break things. Most important is to have the NAN go away. The error message could also mean a forgotten PSTR in the message print. After all 0.92.9 is an old version.

Other_Dave

Repetier said:

Try different EEPROM_MODE first. Uploading old eeprom maps from different firmware versions can also break things. Most important is to have the NAN go away. The error message could also mean a forgotten PSTR in the message print. After all 0.92.9 is an old version.

As I've said on the forums before, I'm feeling a bit dense here (sorry). How would I, "Try a different EEPROM_MODE," and is there a variable within the EEPROM that I can change to accomplish this or is this a firmware change? I don't really know where to begin, I've tried searching for solutions but they're all fairly vague. I'm happy to send you the firmware I'm using and/or my EEPROM values.

Second, I don't know how I would find a forgotten PSTR in the message print...

I hope I'm not bothering anyone too much. Thank you in advance.

Repetier

EEPROM_MODE is a setting if you compile firmware. Alternatively send
M502
M500
from host which does at least in theory the same, also I'm quite sure it does not reset e.g. autoleveling matrix or distortion matrix. So you might want to recreate them with G32/G33 if you use them.

Forgot the PSTR thing. That is more an explaination why message is wrong, nothing you need to fix.

Other_Dave

I have already tried that but tried again for the sake of testing and got this:
https://pastebin.com/biVu1wBK

Basically the same errors as before. I'll just attach my firmware to try and expedite this hopefully.
https://drive.google.com/open?id=1yGSlIkKXIRKiqcN15VWGUQ5kDvT49WA3<br/><br/>I have tried generating my own firmware using the builder but honestly, it makes more problems than solutions as I am too inexperienced. If this firmware is simply too messed up or outdated (and thus the problem), could you help me to create a more updated version?

Repetier

Eeprom I see in log looks good, transformation is off. Maybe add G33 R0 to reset distortion matrix as well.

Upgrading if you used the config tool is easy. Just upload old configuration.h to e.g. dev version and tool will add new settings with good defaults. So it is just an upload and download of new version which is what I'd try first.

Your log does not contain commands so I do not see what you send to get the NAN. Interesting would be
G28
M114

and see if that works.

Other_Dave

Repetier wrote
Eeprom I see in log looks good, transformation is off. Maybe add G33 R0 to reset distortion matrix as well.

Upgrading if you used the config tool is easy. Just upload old configuration.h to e.g. dev version and tool will add new settings with good defaults. So it is just an upload and download of new version which is what I'd try first.

Your log does not contain commands so I do not see what you send to get the NAN. Interesting would be
G28
M114

and see if that works.

Right, I've tried configuring both to 1.0 and just to a "refreshed" 92.9 from an old configuration.h file but get this message when I upload my old file:
"No valid configuration from previous session found. Looks like you have uploaded a plain configuration.h and not a version generated with the configuration tool."

Accidentally had my commands off because I got frustrated with the M105's, sorry. The commands causing the NAN are G29 and G32. G33 is not in my firmware it appears, likely an edit by the manufacturer.

Repetier

Can you try G28 and move around and see if that works? If it works we know all normal settings are ok and problem is a z probe setting.

To use the config tool you in deed need a version created with it or tool will not know the settings in it. So upgrading is a bit more complicated. You see how the defines are named in tool but need to check all manually in config file and enter them.

Other_Dave

Repetier said:

Can you try G28 and move around and see if that works? If it works we know all normal settings are ok and problem is a z probe setting.

To use the config tool you in deed need a version created with it or tool will not know the settings in it. So upgrading is a bit more complicated. You see how the defines are named in tool but need to check all manually in config file and enter them.

It homes just fine, so yes, it must be a Z-probe issue.

Again, I understand the premise of how to use the config tool but my old config file doesn't work and I am too unskilled to do it myself manually. I have tried before and I didn't know enough and/or missed values and I had to roll back my firmware to square 1... Is there anywhere I can get help to get updated/ upgraded genuine Repetier firmware? At this point I will honestly pay for it, I'm feeling kind of hopeless.

Repetier

Since kossel is a frequent printer I think googling for it might show configs that work. And maybe someone having a kossel can send it here. But there are too many combination possible especially with self build printers it is nearly impossible to find a identical hardware.