Topics created by Nuramori

@chrishamm so far so good. It looks like all the reset issues have gone away.

@Gianluca @Nuramori I think we've found why this happens: check that 'Single bed control` in DWC Settings > Machine-Specific is not enabled. It's a bug that's being fixed for the next release.

You can tell if this is turned on, as there's a drop down arrow next to 'Bed' in the 'Tools' section. Same for Chambers, if you use that.

Ian

@Nuramori Please post the output for M122 B22 so we can check the build you have installed and the reset reason.

@nuramori I have 5v and 24v on my Duet 3 and 5v, 24v and 48v on my fysetc spider. Each are connected to the same SSR and triggered by PSON

@dc42 I hadn’t seen any other errors. In the abundance of caution I am replacing the heater and sensor, and will run prints again. The stoppage is rather random and doesn’t happen all the time, but I e posted about the issue since the first beta. It had not been happening prior to that.

That being said I have had with the previous beta where the printer hadn’t stopped but the head was cold and had not been extruding at all; without an error report of some kind, the head was moving, but the heater was not operational.

Im not sure if this is related, but ever since the following happened, things are now printing well.

After the mid print stalls, I had a temp sensor fault. The sensor itself was fine, so I performed an auto tune with the new beta. The result was notably different than the values I had before (which were generated with beta 2). Once I did that, I then was getting temp faults on the bed. I then auto tuned the bed and that too were notably different values.

Once I used the new values for the heaters, everything has been running perfectly fine. The same gcode has completed without a stall for multiple prints of the same file.

@nuramori Thanks for the report, I am looking into it.

@droftarts said in Keep getting random crashes.:

@phaedrux it’s there, from line 23.

Trip to the eye doctor for me I think. 👓

@dc42 Great, thanks for confirming that, I'll work on switching over.

@Nuramori flagging you so you see this - from my understanding of your logs, I think you're running in SBC mode as well.

@nuramori Functionally on Duet 3, they are the same, and the way we use them, they are pin compatible. We don't use the motion controller part of the TMC5160 (see the datasheet for each here https://www.trinamic.com/products/integrated-circuits/) or control them by UART. I believe all boards shipped so far use TMC5160 (though I may be wrong), but that's just down to cost and availability.

Ian

@lbi yeah, I posted this before that was even up, as Filastruder jumped the gun, or were quicker on the draw than even Tony to get it on the internet 🙂

@nuramori
@dc42 said, I could change the whole kinematic model 'on the fly', so it's worth a try..
Some parameters can't be changed mid-print, it would be nice to have a table about those do's and don'ts

AFAIR we didn't remove any fields from the JSON response, although we may have added some.

One more observation from digging around in the logs. The lost connection seems to also happen when the cron job to update the pi4 clock kicks in.

@jdumoulin said in Not clear on properly configuring M591 on Duet3/Toolboard...:

I think it should work in 3.0-RC12 if you connect a switch-type endstop across the temp1 pins and specify port "xx.temp1" in the M574 command, where xx is the CAN address. Let me know if it doesn't work.

So far I have not been able to get it going. I am running Rc12 on the main board, RC11 on the tool board. I borrowed the Y end stop M574 command to see if I could see the trigger on webcontrol but no luck.

Config was M574 Y1 S1 P"20.temp1"

@Nuramori said in PanelDue no longer connecting on Duet3/io0 with 3.01-RC11:

I decided to just avoid the issue by reprogramming the arduino (Adafruit Metro Mini) to create and use a soft serial port, and poll a different digital pin instead. I'm suspecting that there's something odd about the Rx pin on that board, since it also shares the built-in USB comms with that UART pin. The documentation says I can use it as a normal UART Rx, but hmmmmm......

I recoded it, and now everything is working. Thanks for the input, I hope I didn't waste anyone's time (too much).

Yay! No time wasted but yeah, I got my directions mixed up with the setPullup. It was late (for me anyway). 🙂

@bearer said in Needing info on the toolboard harness end crimps.:

https://www.duet3d.com/Duet3Toolboard1LC ?

Looks like
supply or heater? is 3.96mm VH
motor is 2.0mm PH
rest are 1.5mm ZH
all from JST.

Suppose https://duet3d.dozuki.com/Wiki/Connector_and_spare_part_numbers#Section_Duet_Num_3 could be updated to reflect the new boards.

That's all correct.