@droftarts
wiring diagram
Screenshot 2023-03-05 180213.png

@mendelevium
Basically, the PS-ON pin supplies a switched negative ground. Taking a positive from the PSU 12v provides a supply of 12vdc. I use simplify 3d so I put M80 in my start script when a print is started and M81 when a print is finished after all cools down and machine returns to idle state. This can be used to trip my contactor and switches everything off. Thanks for the tip DIY-O_Sphere.

I know this is an old topic, but I'm running into exactly the same issue. Did you find a solution to this??

My bad, it turns out my coordinates for the leadscrews were way off, I honestly don't even know what I was doing!

@dc42 I was only able to get them to work together on a home by creating a second axis and hiding that axis and homing them together.

@JabawokJayUK said in Toolboard 1LC Address not recognised?:

M950 F3 C"!121.out1+121.out1.tach" T3

The CAN address must always come right at the start of the port name string and should not be repeated. So this should be:

M950 F3 C"121.!out1+out1.tach" T3

Thanks @Phaedrux ! I got it back up n running

@dc42 Thank you for your answer.
So for the moment, I will wire the serial port to the IO_1 of the mainboard 6XD as it is working and move my button (in this io for the moment) toward the expansion board. It is not a problem I think.

The commands that I send to the UART are just json data.
The WLED support json API via Serial : https://kno.wled.ge/interfaces/json-api/
JSON over Serial
You can send commands to the WLED instance via Serial using the JSON API.
To request a JSON response containing the state and info objects, send {"v":true}.

for example I send such command :

; TURN ON ALL THE STRIPS M118 P5 S"{""on"":true}" ;LAUNCH HOMING ANIMATION M118 P5 S"{""ps"":1}" ; LAUNCH ALERT ANIMATION M118 P5 S"{""ps"":99}" ; PUT BRIGHTNESS TO 255 M118 P5 S"{""bri"":255}"

@JabawokJayUK So the main thing is that the resistance will increase with temperature when using a PTC but it will decrease with temperature when using an NTC. The Steinhart formula should fit either curve if it's given the right values.

@dc42 interesting. io5&6 are currently unused. So potentially, the idea would be to use "!out6+io6.in" to maintain the tach signal and pwm control with offloaded power.

I profess to having a spare Toolboard 1LC so I am currently redrawing my diagram to move the cab control, which this fan is a part of, to it entirely, mitigating the problem. I was just interested to see if I could get it all on the mini5, all be it with both temp & stepper daughter boards installed for extra connectivity!

@lormal Hope you get a chance to see this - I was able to control likely the same motors using the G320x method. Hopefully if you see it, it is some help!
https://forum.duet3d.com/topic/31642/duet-2-wifi-and-geckodrive-g320x-on-stepper-channels-10-and-11/10

@Phaedrux Thanks

Just coming back around to this, I've found it's the fans spec'd for the v0, which are gdstime 3010. They're known to die after being exposed to the heat from the chamber % hotend.

https://github.com/VoronDesign/Voron-0/issues/121

I've swapped them out the the Winsinn fans suggested and they seem to be fine now.

bmgoncu created this issue in VoronDesign/Voron-0 open 30mm blower fans sensitive to the hotend heat and stops working #121

Good Tips. Thanks @achrn.

Yes. I need to read analog input data from sensor.
Using the analog data I want to control the heater. I presume it should be realtime, so that the heaters can quickly adjust to the sensor value.

I was not aware of daemon.g and object model properties. Good points. I will explore these possibilities.

Thanks much.

@Tinchus I guess you have a Duet 3 6HC mainboard. The drivers on board are stepper drivers, and there is no inputs on the board that are fast enough to read and process encoder inputs. The 6HC also does not have any external stepper/servo driver pins directly onboard (it can drive small PWM-based hobby servos though, but that's not what you asked about!). However, we produce two CAN-FD-connected boards for external drivers; the Duet 3 1XD and the Duet 3 1HCL.

The 1XD supports the connection of external motor drivers. These can be stepper or servo drivers. If there is feedback from the driver (eg an alarm when position can't be reached), the firmware can react to that and pause the print. However, position information is not returned to the Duet, so the axis will need to be rehomed before the job can continue.

The 1HCL supports the direct connection of stepper motors with encoders, and more tightly integrates these motors with the firmware. It uses the same stepper driver as the 6HC, but has it's own onboard processor to be able to read the encoder and adjust current to the stepper driver to get it to where it needs to be. If there is a loss of position, the firmware on the mainboard will still know the position of the axis. The user can then decided what action to take, without the need to rehome the axis.

Search the forum for examples of the motors users are using with these boards:
1XD https://forum.duet3d.com/search/?term=servo+1xd&in=titlesposts
1HCL: https://forum.duet3d.com/search?term=servo+1hcl&in=titlesposts

Ian

@Daniel-0 It's the cable itself that is causing the issue, not the accelerometer. There isn't really any other option other than disconnecting the accelerometer cable, at the Duet end, to stop signals bouncing up and down it and interfering, at least as I understand it.

Ian

On the github they write:

USB communication Keep the usb connection is ok between the MKS THR36/42 and your Klipper host board, and power on. SSH login to your Klipper console and run ls /dev/serial/by-id/*

If this should work, is it possible to use a USB Hub to connect the toolboard and the Raspberry Pi to the duet?

Please try this method to try and determine your R parameter.

Measuring the heating rate (M307 R parameter)
Turn the heater on from cold, wait a few seconds for the temperature to start rising, then time how long it takes for the temperature to rise by a further amount e.g. 10C (for a slow bed heater you might wish to use a smaller amount e.g. 5C). Divide that temperature rise by the time in seconds to get the heating rate.

@alankilian @deckingman
Looks like daemon.g with a G4 command should do the trick. Thanks for the tip on the timers!