@SupraGuy said in Duet 3 Mini 5 + 1LC toolboard:

if I'm going to mount the accellerometer to match X and Y axes, the mount will need to be different from what looks like it's intended.

It doesn't matter which way you mount it, as long as the tool board XYZ axes match up with the machine XYZ axes in some order, with signs reversed if necessary. You can configure the mapping between accelerometer and machine XYZ axes. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer#orientation.

@klinkerstein said in CoreXY + linear encoders + 1HCL closed loop expansion board:

Another thought was, if we use two controllers, one for A motor and one for B motor, and just connect the (45°) X/Y axis encoders directly to those, ignoring the CoreXY kinematics.. couldn't it still work? The position for X would be controlled through motor A, resulting in diagonal move but since we have the second controller seeing this as a disturbance, it corrects motor B automatically to keep Y axis constant? I am just not sure if such a control scheme is stable or might start to oscillate because in essence you have two controllers in series.

I thought about it and I am pretty sure this doesn't work, since the response of one of the linear rails with respect to motor A changes depending on what motor B does.

I have perused the code a bit and I think I have an okay picture on what's where.

@lazy_mosquito I wouldn't slap the G92 into config.g, just emit it on the console with the effector in a well known position so tuning can happen

I see you've already sent an email for a warranty replacement. We arrange for a replacement there.

For your other printing issues, please start a new thread for those if they remain after your new card arrives.

I delivered m111 p1 s1, and this is the changed repeating output:

WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns 1ResponseTimeout, pending=1 WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Con^?/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578 ): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 WiFi: /hom^?s/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 ResponseTimeout, pending=1 ResponseTimeout, pending=1 Debugging enabled for modules: Network(1 - 0xffffffff) WiFi(14 - 0xffffffff) Debugging disabled for modules: Platform(0) Webserver(2) Gcodes(3) Move(4) Heat(5) Kinematics(6) InputShaping(7) unused(8) Print Monitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) Display(15) SbcInterface(16) CAN(17) Expansion(18) ResponseTimeout, pending=1 Bad recv status size ResponseTimeout, pending=1 Bad recv status size ResponseTimeout, pending=1 Bad recv status size ResponseTimeout, pending=1 Bad recv status size ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projec^?/home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Con^?uet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/^?t 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size WiFi: /home/renz/Projects/Duet3D/WiFiSocketServerRTOS/src/Connection.cpp(578): refused conn on po^?/Connection.cpp(578): refused conn on port 80 already 4 conns ResponseTimeout, pending=1 Bad recv status size ResponseTimeout, pending=1 Bad recv status size

Wondering how your progress is going. I'm picking up a 6 axis robot and hoping to use a duet board for main the control. Any advise would be appreciated.

@dc42 Thanks! Got a converter and it's working through IO_0 on the board!

@Kiwi3D your steps per mm for z should be the same as X I would expect

It turns out I must have burned up my Out6 while poking around with a multimeter. I switched to Out3 and the hotend fan thermostatic control is working as it should now.

@droftarts

Thank you for confirmation. PID in progress now

@tino_ber48 Oops, yes, you're right, two of the IO ports are input only. So 12 inputs on the Mini 5+. Plus 4 on the 1HCL.

If you need more expansion, I'd probably go with a 3HC, which has 6x IO with in and out, plus 3x larger stepper drivers. See https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_3HC

Ian

@theBAHNFreak I had a similar Issue with a Toolboard 1LC v1.2 after disconnecting everything from the board I still got the same bad Vssa error so I checked the schematics and measured the board. I found that the Resistor R47 had a value in the range of 2.2kOhm instead of 10Ohm and replaced it. After that, the temperature reading on both temp0 and temp1 was working.
ee405fca-79ad-4d68-96a8-7d37073026c6-image.png

@moth4017 Thank you Will look into this
Made some up using a dupont terminal but will save this link for future use
Thank you for the fast response

@RockB @droftarts @dc42 any suggestions?

@tristanryerparke not yet.

@oliof said in BIQU microprobe issues:

@Craigrobbo are you saying BLTouch works after separating out the wiring, or Microprobe, or both?

The BLtouch worked when the cables re within the wiring loom and the same when seperated too.

@achrn had same error. I have 2 24v power units, one for board and one for bed. Just swapped outputs around and system now works ok

Well got the endstops working on my own.
for anybody having similar issues,
I grounded the shielding on all the endstop and z probe cables and after ordering a trifield meter to test for efi, I moved the duet and pi to a more shielded location with some metal between them and the stepper motor transformers.

hope this helps someone in the future.
an aluminum, case for the duet would probably be a good idea,

Wonder if a 3d printed case from some ferromagnetic fillament would work for shielding.

the duet seems to be more sensitive to noise than my old controller was

@Ironman777 We recommend 32V maximum for the 6HC v1.01. This gives some headroom for voltage generated by stepper motors coming to a sudden stop.

Ian

@dc42 Thanks for the reply. I took a look at the link, but decided that's quite a departure from the Arduino and would be quite a lot of work to re-implement everything for a new development environment that's otherwise low on my radar. I'll hopefully set up a quick test in the coming days to have a look at the M118 command in more depth.