Hello All!

I gutted my CR-10 MAX and installed a Duet 2 Ethernet inside. I apologize for the seemingly simple issue, but I am at a total loss. For some time, zits have plagued me. From what I can tell, this is not a retraction issue, it happens as the nozzle goes from an inner perimeter to outer. It sits there for a fraction of a second and spews a bit too much plastic. This can be seen even on my skirt. The zits are always in the exact same place no matter what changes were made in S3D, always right where a new perimeter begins. Using S3D I have done the following changes/tests, with absolutely no change (Link here for picture)

• Turned off forced retractions between layers
• Turned on Perform retraction during wipe (wipe = 5mm)
• Turned on coast (coast = .3mm)
• Adjusted Extra Restart Distance between -0.4 to +0.2

I definitely thought that coast or extra restart would fix the issue or at least make some change. I don't believe this is a conversion issue (creality to duet) but I could always be wrong. I haven't had issues with Duet on my deltas. My config file can be found below (probably some issues in there) and sample gcode from S3D.

Any help would be extremely appreciated as I have let this problem go on for far too long. Thank you!

CR10 MAX Config File.txt
3DBenchy3.gcode

@dc42 said in Unable to Connect to Duet Ethernet after Calibration:

Please post your config.g file.

See attached, thank you!

0_1523635076460_config.g

So everything is now up to date. Both firmware and DWC are running 1.21.

Now even with the printer hooked up to USB its now throwing an error.

After running M408 S2 this is what came out:

SENT: M408 S2
READ: {"status":"I","coords":{"axesHomed":[1,1,1],"xyz":[0.000,0.000,150.000],"machine":[0.000,0.000,150.000],"extr":[0.0]},"currentTool":0,"params":{"atxPower":0,"fanPercent":[0.00,100.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00],"speedFactor":100.00,"extrFactors":[100.00],"babystep":0.000},"sensors":{"probeValue":0,"fanRPM":0},"temps":{"bed":{"current":19.7,"active":0.0,"state":0,"heater":0},"current":[19.7,20.4,2000.0,2000.0,2000.0,2000.0,2000.0,2000.0],"state":[0,2,0,0,0,0,0,0],"heads":{"current":[20.4],"active":[0.0],"standby":[0.0],"state":[2]},"tools":{"active":[[0.0]],"standby":[[0.0]]},"extra":[{"name":"MCU","temp":34.3}]},"time":122.0,"spindle":{"current":0,"active":0}}

Also after updating to v1.21 I am getting this error on the PanelDue Console:

Error: M665: M665 parameters do not apply to Cartesian kinematics Network running, IP address = 192

I was not getting this before the update.
As always thanks for your help

• Herrm

@dc42 said in Unable to Connect to Duet Ethernet after Calibration:

Which firmware and DWC versions are you using?

Looking at DWC it says

• Firmware Version: 1.19.2 (2017-09-01)
• Web Interface Version: 1.19.3

I will look into the 1.21 Release, I thought I actually had updated recently, but apparently I hadn't!

@dc42 said in Unable to Connect to Duet Ethernet after Calibration:

I'm glad you got it sorted.

It seems that the issue has reemerged, but I have some new information. So before posting again I attempted to do your suggestion from before (Hook up to USB and run the M408 S2) However, when the printer is hooked up to USB and connected to, it will not timeout of DWC.

This leads me to believe that the error isn't caused by the autocalibrate. But I have no idea what is causing it. DWC will not timeout if the printer is just on and connected. But if I send enough move commands from DWC it will timeout. This may be more like something you said before with the calculations?

I am completely out of ideas of what to test. I even went through my config.g and cleaned it up and got rid of unnecessary things.

If you can give any assistance that would be wonderful.

• Herrm

Okay….well apparently I am a liar. I truly have no idea what happened, but I was experiencing the issues I stated in the post above, and just for shiggles I plugged in the ethernet and now it doesn't throw AJAX errors, it auto calibrates just fine and the issue above is now magically gone.

My best guess is that I was possibly experiencing some EMI from the stepper motors, because I moved the motor wires away from the probe wire to reseat the connector. And then plugged it in and it magically started working.

Thank you Dave for your constant support, even when it is my own foolish fault!

• Herrm

@dc42:

Another thing that would be useful is to auto calibrate, then after DWC has disconnected, send M408 S2 from USB and post the response here.

Sorry for the delay, midterms took importance the last couple days.

Also however before I did any of the above I noticed something really strange that I know wasn't happening last week. When I run the smart calibration there is a single point that sets off before it gets to the bed. And its always the same point at the roughly the same height.

This is really strange because two weeks ago I was printing (albeit not perfect) and had no leveling issues. And the only thing I have done since then is update the firmware. I am wondering if I updated the firmware incorrectly somehow?

Any ideas DC42? All I have got is possibly resetting the duet and doing a fresh install, but I don't know how recommended that is.

@dc42:

Please post your config.g, homedelta.g and bed.g files.

You can find the link for my config.g, config-override.g, homedelta.g and bed.g in the Google Drive below:
https://drive.google.com/drive/folders/1YqmvTnD0Gy7mISWlkMhoZ1G7fogomSj4?usp=sharing

As always thank you

• Herrm

Hello All!

I just did a rebuild of my printer and finally have gotten it set back up on the DWC, however I can't get it to connect during or following an auto calibration.

The DuetEthernet will connect when it is first turned on. I can home, move the axis', and heat the bed/extruder, but if I play with the controls enough it will throw an AJAX error. And then when running an auto calibration or a mesh it will throw an AJAX error before the first probe or sooner.

Once DWC throws the AJAX error I can't get it to connect, short of a reboot, or M999. The printer does finish the calibration, but when I look at the console, where it would normally say:
[c]Calibrated 6 factors using 10 points, deviation before #.### after #.###[/c]
When its connected to ethernet, it will show:
[c]Calibrated 6 factors using 10 points, deviation before[/c]
Obviously lacking anything after the word before.

I am able to print from the SD card without issue. I have tried updating both the DWC and the Ethernet Firmware to the latest Version 1.21RC5 - Duet2CombinedFirmware.bin, but unfortunately did not help. Also when I run the calibration without connecting the ethernet it will run fine, but if I plug it in after the calibration has completed then it is still unable to connect.

Any help would be incredible, I'm looking forward to get my printer back up and running for good!

• Herrminator117

It doesn't seem to be. If I hold the carriage and twist it, I can definitely some play from side to side. But that is inherent on how the injected molded seemecnc carriages work. Because the use the flexible plastic parts to keep it snug against the extrusion there is play of it is forced.

I did run a mesh and watched the carriage and didn't observe any twist as it moved. Looking at the heat maps the high points are where the mesh starts a new row and then the readings get lower and lower until the start of a new row and its only on the edges furthest from the x and y towers. Again however I don't know what that means unfortunately.

I am going to run a mesh with a smaller diameter and see how that comes out.