@dc42 thank you, here is an alternative link from Stepperonline of the full kit. It should be the same hardware, just a different lable.

Stepperonline Servo Kit
The Datasheet is in the download sektion

Here are the broken links, I hope the'll work fine this time.
Leadshine EL6 Manual Dowanload

Leadshine EL6 Product Page

Leadshine ELM1S-1000FH80F-HH2 Servo

@skrotz They were sadistic. Black = 24v, Dark grey = ground, light grey = tach, and white = pwm control. PWM needs to be inverted. Hooking up 24v and ground to an always on fan port and control to fan2 ground works fine. It puts out a ton of air, but the shroud spreads it out less than I expected.

I haven't confirmed tach as working but seems likely it would, although I'm not sure it's useful.

@id_pqr it does. there are several ground connections in fact

@flipps does each fan spin when you connect it to the always-on fan output instead of to the Fan0 or Fan1 output?

@Scara_Arm when using drivers with single-ended opto isolated inputs, it is better to use the alternate wiring scheme between the expansion breakout board and the external driver. See https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/Duet_Expansion_Breakout_Board#signalling-voltages.

@moris please post your config.g file so that we can check what settings you are using.

@Duckers Oh wow, been a long while!

I never got around to this experiment - its gotten to the point where I've switched from a duet mini5+ on klipper to a duet 6hc on klipper - the mini5+ used 2209's, and didn't really notice any changes between the mini and the 6hc, other than speed!

I don't use interpolation on either - experiments with encoders revealed small issues with positioning while using interpolation, but these are also very small!

@droftarts
I'm using usb to uart converter connected with jumper wires to paneldue connector on duet2wifi.

Ps. Yes, sorry, i meant YAT

@jay_s_uk I always respect your support. As mentioned that you have supported me lot of times. I know that.

Sorry, that my words have hurt you. My apologies for that.

I know that you are supporting from outside, not from Duet Team.

@e4d said in Problem with Duet3D Magnetic filament sensor:

measured sensitivity 2609.32mm/rev

This is one hundred times less sensitive than expected.

I suspect that the rotation-part is not able to rotate smoothly.

Try pushing a piece of filament through the sensor and watch the back of the shaft that has the magnet on it and see if it rotates smoothly.

Sometimes it takes a little adjusting of the thickness of the case to get the magnet-to-sensor distance right.

Also, your agc of 58 is quite low which indicates the magnet is very close to the sensor. Take it apart and look for scratches on the top of the sensor to make sure they are not touching. If so, just add some paper shims in the case and try again.

Somethig works, others no: I can see sensors state (and create them) from the main board. In my main config I have this to test:

M950 J9 C"!1.io1.in"

And It works, I can see the state of that ping on the objects model page. So the CAN connection is there.

On the other board, the config file is:

; Enable network
M552 P0.0.0.0 S1

M669 K0
M569 P0 S1 D2
M569 P1 S0 D2
M569 P2 S1 D2
M569 P3 S1 D2
M569 P4 S1 D2
M569 P5 S0 D2
M584 X0 Y1 Z2

M350 X16 Y16 Z16 I1
M92 X320 Y320 Z1600
M566 X200.00 Y200.00 Z300.00
M906 X1000 Y1000 Z1000
M208 X0 Y0 Z0 S1
M208 X220 Y220 Z200 S0

M950 J9 C"!1.io1.in"
;M581 P9 T4 S1 R0

M954 A1

That M950 doesnt work, I cant create a sensor located on the same board, but I can do it from the main board.
BUT, the motion system on the secondary board works. I have access through the web iterface and I can move the axes with no problem or issue movements commands indepently from the can connection.
daemon.g is also not working on the secondary board.

I think the project will stop here 😞

As a wich list to think about: having the ability to connect 2 duet3 boards is usefull, but if they cant have some kind of freedom, I dont really see why this would be better than using other extension biards, for sure would be cheaper.
So to unleash all the power, wouldnt it be super good to be able to connect them with the CAN but each board can have its independency?

@achrn the serial port is the PanelDue port. The M575 command can be used to put it in PanelDue mode or in raw mode.

@Phaedrux Thanks for the support.

The below issue came up repeatedly.
'M997: File DuetWiFiServer.bin not found'

Then we read another topic in which it is suggested to use 'M21 to remount the SD card'.

After that, it updated the firmware. Now it is connected to the Wifi

@cj19944 might be recoverable then. feel free to drop me a PM

@bubblevisor said in Induction probe false triggering:

Do you mean I need to fully define M558 in the bed.g as well as in config.g? such as M558 K0 P5 C"^zprobe.in" H10 F1000 T6000 A20 S0.01

No, not the full M558, but you would need to include the K0 or K1 in addition to the parameter you wanted to change.

@Tortuga yes

@knuxvomica I spotted this. From your config.g:

M569 P20.0 S0 ; assign physical drive 0 at can 20
M569 P10.0 S1 ;T2.6:2.6:5:0 ; assign physical drive 0 at can 10
M569 P10.1 S1 ;T2.6:2.6:5:0 ; assign physical drive 1 at can 10
M569 P0.0 S0 ; assign physical drive 0
M569 P0.1 S1 ; assign physical drive 1
M569 P0.2 S1 ; assign physical drive 2
M584 Y10.0 X10.1 E20.0 Z0.0:0.1:0.2 ; map drives
;Drive settings
M350 X16 Y16 Z32 E16 I1 ; configure microstepping with interpolation
M92 X160 Y160 Z320 E562 ; set steps per mm
M566 X1000 Y1000 Z500 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X100000 Y100000 Z3000 E3000 ; set maximum speeds (mm/min)
M201 X4000 Y4000 Z20.00 E1500 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E650 I30 ; set motor currents (mA) and motor idle factor in per cent

From your M122 B10 report:

Driver 0: pos 0, 80.0 steps/mm,ok, SG min 0, mspos 0, reads 40162, writes 0 timeouts 0, steps req 0 done 0
Driver 1: pos 1599840, 160.0 steps/mm,ok, SG min 9, mspos 9, reads 40161, writes 0 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm,ok, SG min 9, mspos 9, reads 40161, writes 0 timeouts 0, steps req 0 done 0
Moves scheduled 1, completed 1, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0

This indicates that driver 1 is correctly configured and 1 move has been executed, which has moved driver 1. However, driver 0 indicates 80 steps/mm which is the default, whereas your config.g maps axis Y to driver 10.0 and the subsequent M92 command sets the Y steps/mm to 160. So I suspect that some commands in config.g may not be working as intended.

Please can you try sending the M584, M92 and M906 commands manually from the command line with the same parameters as used in config.g. Then send M584, M92 and M906 without parameters to check that the correct values are reported. Also send M913 to check that all axes are set to 100% motor current. Finally, test whether you can make X or Y moves using e.g. G91 G1 H2 X10.

@dom-tr that looks to me like the TS30041 12V regulator chip.

@SignPostMan said in Thermistor Temperatur od T2 and T3 are not correct:

@dc42 said in Thermistor Temperatur od T2 and T3 are not correct:

R2200

Same problem, Same Fix

Firmware 3.4 and later detect the DueX version automatically and adjust the default R parameter for M308 accordingly.

@infiniteloop thanks. it's probably the same on the previous board. I haven't measured the wires yet