One of the requirements:
"Each Z motor must be driven from a separate stepper motor output on the Duet + optional DueX expansion board"
Guess there is no way around this requirement? Like reasigning the E1 or E0 to be the second Z?
EDIT: Reading up on M584 now...
EDIT2: and I think I answered my own question. Thanks again for leading me down the right path.
@dc42 Got it figured out. When I moved the pins around I think I must've messed up the crimp for the data pin. I tested continuety across all pins the first time around but not after moving the pin to the correct position. It's actually showing readings now. Thank you.
Duet3D laser filament monitor on endstop input 4, disabled, allowed movement 60% to 160%, check every 3.0mm, current position -6.7, brightness 94, shutter 17, measured minimum 95%, average 95%, maximum 95% over 12.1mm
I think I have the same end stop. It should be labeled G S V for the pins. Make sure it's connected like so (however don't take my word for it try and find documentation of both the switch and the board, I don't want to be responsible for a damaged board and I believe you can damage the board if you wire it wrong to the endstop) :
G - Ground
V - Voltage 3.3v Pin
S - Signal
I had to rewire my cable because the pins were not in the same order.
If you have that right you should be able to see the light on the board next to the corresponding motor go on or off if you block the sensor.
Lastly if it's not working you can try to change the endstop modes from S1 to S0 or S0 to S1.
It should not be too difficult as long as the wiring is correct.
So I've noticed if I trigger some command from the web console, I can only see any type of results from the command in the web console. Same with commands triggered from the PanelDue, they only show up on the PanelDue console.
Is there any changes I can make in order to have the outputs always show up in all consoles?
Ran a few additional tests. Uploaded a 100MB gcode file to the printer then renamed it and downloaded it. Diff showed quite a bit of differences...
383344c383344
< G1 X159.187 Y158.973 0.0064
---
> G1 X159.187 Y158.973 E0.0064
383378c383378
< G1 X142.123 Y162.035 E0.0064
---
> G1 X142.123 Y162.035 E0.0064
654509c654509
< G1 662.429 Y157.011 E0.0041
---
> G1 X62.429 Y157.011 E0.0041
1052118c1052118
< G1 X27.83 Y248.237 E0.0060
---
> G1 X27.883 Y248.237 E0.0060
1052158c1052158
< G1 X28.993 Y237.054 E0 .0054
---
> G1 X28.993 Y237.054 E0.0054
1218337c1218337,1218338
< G1 X121.249 Y126.937 E0.0060G1 X121.480 Y127.361 E0.0066
---
> G1 X121.249 Y126.937 E0.0060
> G1 X121.480 Y127.361 E0.0066
1218372c1218373
< G1 X130.009 Y118.655 E0.01094
---
> G1 X130.009 Y118.655 E0.0109
1424671c1424672
< G1 X151.592 Y110.16 E0.0031
---
> G1 X151.592 Y110.164 E0.0031
1479890c1479891
< G1 X95.562 Y146.417F4025
---
> G1 X95.562 Y146.417 F4025
1479938c1479939
< G1 X86.659 Y129.117 E0.005Y1
---
> G1 X86.659 Y129.117 E0.0051
1811283c1811284
< G1 X223.60 Y172.224 E0.0024
---
> G1 X223.608 Y172.224 E0.0024
1908715c1908716
< G1 X196.599 Y177.845 E0.0083
---
> G1 X196.599 Y157.845 E0.0083
1909045c1909046
< G1 X180.891 Y10.748
---
> G1 X180.891 Y160.748
1909077c1909078
< G1 X1778.748 Y169.827 E0.0030
---
> G1 X177.748 Y169.827 E0.0030
2153494c2153495
< G1 X123.799 Y177.45 E0.0066
---
> G1 X123.799 Y177.455 E0.0066
2153496c2153497
< G1 X123.279 Y176.563 E0.075
---
> G1 X123.279 Y176.563 E0.0075
2153503c2153504
< G1 X1.722.086 Y173.193 E0.0017
---
> G1 X122.086 Y173.193 E0.0017
2250709c2250710
< ; tool H0.10 W0.083
---
> ; tool H0.100 W0.083
2250711c2250712
< G1 X183.407 Y170.883 E0.0005 F450
---
> G1 X183.407 Y170.883 E0.0005 F3450
2250730c2250731
< G1 X187.241 Y1Y171.521 E0.0039
---
> G1 X187.241 Y171.521 E0.0039
2328424c2328425
< G1 X230.623 Y243.489 E0.004
---
> G1 X230.623 Y243.489 E0.0046
2328466c2328467
< G1 X233.370 Y244.366 E0.60727
---
> G1 X233.370 Y244.366 E0.0727
2505308c2505309
< G1 X235129 Y238.909 E0.0022
---
> G1 X235.129 Y238.909 E0.0022
2505361c2505362
< G1 X231.4252 Y239.061
---
> G1 X231.422 Y239.061
2981519c2981520
< G1 X162.74 Y153.592 E0.0030
---
> G1 X162.741 Y153.592 E0.0030
2981521c2981522
< G1 X162.338 Y153.98 E0.0029
---
> G1 X162.338 Y153.498 E0.0029
2981561c2981562
< G1 X154.133G Y152.263 E0.0029
---
> G1 X154.133 Y152.263 E0.0029
Ended up downgrading to 2.02 and after two tests there were no differences between the uploaded file and downloaded file. Considering going back to 2.03 B3 but I've got a few things I need to print.
Don't know if I had a bad firmware flash or something else but it's working correctly for now.
@dc42 said in Bad command & Missing characters in Gcode since firmware upgrade:
I am still hoping that one of you can send me a comparison of the original vs. corrupted files, using Windows fc /b or some similar command. See my reply of 20 September.
diff Orig.gcode Downloaded.gcode
863362c863362
< G1 X69.968 Y5.986 E0.00274
---
> G1 X69.968 Y59.986 E0.00274
863364c863364
< G1 X70.502 Y59.729 E.00274
---
> G1 X70.502 Y59.729 E0.00274
863391c863391
< G1 X57.055 Y6 X4.310 E0.00357
---
> G1 X57.055 Y64.310 E0.00357
908950c908950
< 1 X62.824 Y98.654
---
> G1 X62.824 Y98.654
908990c908990
< G1 X1G02.446 Y66.725 E0.00361
---
> G1 X102.446 Y66.725 E0.00361
909168c909168
< G1 X103.024Y66.246 E0.00529
---
> G1 X103.024 Y66.246 E0.00529
909193c909193
< G1 X109.288 YY66.944 E0.00303
---
> G1 X109.288 Y66.944 E0.00303
909325c909325
< G1 105.718 Y70.234 E0.00378
---
> G1 X105.718 Y70.234 E0.00378
909346c909346
< G1 X103.8273 Y65.606 E0.00274
---
> G1 X103.873 Y65.606 E0.00274
909374c909374
< G1X108.523 Y68.658 E0.00274
---
> G1 X108.523 Y68.658 E0.00274
909399c909399
< G1 F21800
---
> G1 F1800
909426c909426
< G1 X05.883 Y46.145 E0.00355
---
> G1 X105.883 Y46.145 E0.00355
909435c909435
< G1 X08.937 Y47.507 E0.00355
---
> G1 X108.937 Y47.507 E0.00355
909450c909450
< G1 X1F207.974 Y52.969 E0.00373
---
> G1 X107.974 Y52.969 E0.00373
909488c909488
< G1 X06.991 Y46.409 E0.00341
---
> G1 X106.991 Y46.409 E0.00341
909501c909501
< G1 X2109.593 Y50.121 E0.00329
---
> G1 X109.593 Y50.121 E0.00329
909799c909799
< G1 X108.652 Y50891 E0.00274
---
> G1 X108.652 Y50.891 E0.00274
909806c909806
< G1 X106.9987 Y52.455 E0.00269
---
> G1 X106.987 Y52.455 E0.00269
933045c933045
< G1 X129.607 Y68.005 F1000.000
---
> G1 X129.607 Y68.005 F18000.000
933048c933048
< G1 X133.198 Y70.51 F18000.000
---
> G1 X133.198 Y70.751 F18000.000
933062c933062
< G1 X122.179 Y59.2 319 E0.00576
---
> G1 X122.179 Y59.319 E0.00576
933509c933509
< G1 X68.243 Y2.863 E0.00312
---
> G1 X68.243 Y62.863 E0.00312
933546c933546
< G1 X7Y3.197 Y64.893 E0.00307
---
> G1 X73.197 Y64.893 E0.00307
933736c933736
< G1 X53.455 Y66.03 E0.00355
---
> G1 X53.455 Y66.003 E0.00355
933738c933738
< G1 X52.239 Y65.621 E0.0009
---
> G1 X52.239 Y65.621 E0.00609
933760c933760
< G1 X53.400 Y.058.721 E0.00358
---
> G1 X53.400 Y58.721 E0.00358
1181427c1181427
< G1 X27.108 Y2.058 E0.00194
---
> G1 X27.108 Y42.058 E0.00194
1181429c1181429
< G1 X31.272 Y46.431 0.00343
---
> G1 X31.272 Y46.431 E0.00343
1181461c1181461
< G.01 X27.108 Y45.205 E0.12357
---
> G1 X27.108 Y45.205 E0.12357
1181488c1181488
< G1 X34.926 Y55.959 E000139
---
> G1 X34.926 Y55.959 E0.00139
1181513c1181513
< G1 X207.108 Y50.658 E0.09256
---
> G1 X27.108 Y50.658 E0.09256
I'll have to toy around with it more later. I actually found out today I had a faulty PSU causing most of my headaches. On any load change it was causing my lighting to flicker a little. It was not enough to cause printing issues but it was noticable in the lighting and the main reason I was trying to get hardware PWM working (so I could do higher PWM frequencies and avoid the communication from klipper). But now that I got hardware PWM on the lights and the issue persisted, I realized it could be a bad PSU. I finally tried a different PSU and everything is perfect. Working on RMA now.
Either way, I appreciate all the info and quick responses as always.
@dc42 said in Safe to add capacitor to smooth LED powered by PWMed bed output?:
..all Duet heater and fan outputs provide.
Sorry missed the first time around.
I ended up moving to E0 pin and klipper allowed me to enable hardware PWM there. Not sure why the bed didn't work but this works fine too.
Thank you for the info.
OK, kind of thought it would would not be that simple. Though I was thinking I could maybe get around that issue by using a smaller cap.
Klipper does have option for hardware PWM but maybe just not on the heater bed port. Is it only the fan ports that support hardware PWM?
So I'm using klipper with a duet ethernet and because of the recommended limits on the PWM frequency in Klipper, it's a bit irritating to look at. Would it be safe to add a capacitor to the LED bar (i'm using the bed output pins)? If so what spec capacitor is recommended for a 24v system?
Just wondering if I could use the External PanelDue SD card slot for the Duet and not use the onboard slot at all?
Just thinking this could be useful if there was something wrong with the onboard slot or just for convenience.
So I'm using m42 to control pins, is there any way to read their current state with gcode?
@dc42 said in Bad command & Missing characters in Gcode since firmware upgrade:
@BlueDust said in Bad command & Missing characters in Gcode since firmware upgrade:
I assume the CRC checking is enabled by default. How do you enable/disable them?
It's at the bottom left of the Settings/Machine Specific page of DWC 2.04.
If the CRC errors only occur if you upload while printing, then maybe we need to reduce the SPI transfer speed to the Ethernet module if you upload while a print is active, or else adjust the bus priorities.
Would be possible to somehow make the SPI speed user configurable? I've got two boards, one that I just stopped using because of this and another that only works as long as I'm not printing. Would be awesome to recover the other board and use it for something.
@kmhudgins said in Bad command & Missing characters in Gcode since firmware upgrade:
Hi,
I am starting to have the same issue with bad commands. Was this problem every resolved?
I ended up just avoiding uploading during a print that seems to have solved the issue for one board. I still have another board somewhere that it happens to all the time no matter if I'm printing or not that I gave up on.
OK thanks for pointing me in the right direction. It was connected to E1, moved the cable to E0 now. Going to try again but I'm fairly certain that was it. And yes, the led on the board blinks along with the led on the sensor. Thanks again.
EDIT: Just to confirm, everything works now. 
Sorry if this has been discussed but I did some searching and didn't have time to keep digging.
The lights all look correct, blinks a few times on power on, then flashes red/green when idle and rapidly blinks green when filament is moving. However, when I run a "M591 D0" I simply get the below, does not matter if the printer is printing or not. I'm assuming "no data received" is bad. Is there a limit to the wire length? I'd say I'm using close to 400mm of wire and could probably cut it down to 300mm but I want to make sure that's the issue. first.
Duet3D magnetic filament monitor on input 3, disabled, sensitivity 24.80mm/rev, allow 70% to 130%, check every 3.0mm, no data received