@nightlonk42 Please share your config.g and config-override.g if it is present in /sys.

@simon0362

Set "Maximum carriage travel" before setting "Homed height"

I got caught by that one also with my Delta.

Capture.PNG

@jay_s_uk Thanks! Now they're actually in sync that should be much easier through DWC. Back on track 😊

I'm a newbie and also was getting message 'Your DUET rejected the HTTP request Check SD card."
Found there's a great guide available on what's required to configure the SD Card.
https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure

@jnofsinger
Thank you for replay.

I solved this problem as the homeall.g and homez.g was broke. Now all work fine.

May you post link for me. This is the only problem prevent me the print.

Should I see it on control?

@dougal1957 said in Error installing FW update from DWC:

@thedragonlord said in Error installing FW update from DWC:

@dougal1957 said in Error installing FW update from DWC:

@thedragonlord make sure that the sdiap file is in the firmware directory I suspect that will fix your issue!

if it's not where do I find it?

You said you had downloaded it from the repository but did you then upload it to the Firmware directory on the Duet a change was made around 3.3 that changed where the upgrades should go

89bd4adb-e374-4d31-afd3-11dae6bd16b9-image.png on the system tab click on the drop down at top of the files list and select Firmware Directory

uh i missed this!!!! thanks

i found the mistake. it was an incorrect homex.g and homeall.g

Thanks for the Help

Figured it out! It seems to be a software bug related to InputShaper plugin. Posted more info here https://forum.duet3d.com/topic/24859/inputshaping-plugin-0-1-0-rc7-released-repacked

@dc42 Thank you! Solved.

@t3p3tony 3.4.0.b4

@dc42 ok, i shall rewire and set the z probe / endstop to io.1

@phaedrux said in Error: This kinematics does not support auto-calibration:

Basically. The feature was deprecated in favour of something better. To approximate the old style you can just define a sparse grid with 4 or 9 points, ie a 2x2 or 3x3

Okay fair enough. I was able to make this work with a G29 4-corners probe.
M557 like this:
M557 X3:353 Y5:354 P2:2

Lastly I edited my bed.g to run a G29 S0 & S1 instead of the series of G1/G30 commands i had before, then I put the same G29 S0 & S1in my Start Gcode.

Thanks for your help.

@Phaedrux I ordered a board and expect it to arrive by October. If I don't manage to find the offending change by a couple bisecting builds, I'm happy to send it over to Duet3D for inspection.

@siam said in Warning: M500: No M501 command was executed in config.g:

M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

Thanks Slam that seems to have fixed it.
Just have to recalibrate it now.
Have to say this hasn't been as easy a transition from a legacy duet to a duet 2 has I had hoped.
Thanks to all for their help.

@michaelr123 It appears I was able to fix the issue by updating the board through BOSSA, now I just need to get the config all setup again...

I was able to get the board to update by using a powered usb hub. Then the win 10 pc recognized the board and let me flash the firmware.

@rein3003 said in 1LC V1.1 firmware fault:

@dc42 are there serial numbers on the toolboards? I have to fill them in in the form...

If unable to locate, just put N/A in the field.

@dc42 said in How to define print bed area versus M208:

Avoid using G92 if possible because it will mark the axis as homed even if homing

In the example I gave if homing failed would not the "plain" G1 move immediately preceding the G92 also fail thus preventing the G92 from being executed?

Frederick

@jckray I haven't tried myself, but documentation is here: https://duet3d.dozuki.com/Wiki/Duet_2_Maestro_12864_display_menu_system#Section_File_format_for_image_command

Ian