@WOPR73 I think you have a 6HC, not a Mini 5+. The mainboard has built in 120ohm resistor for termination, so you don't have to worry about terminating that end. At the other end of the CAN bus, the SZP provides the termination.
Ian
@WOPR73 I think you have a 6HC, not a Mini 5+. The mainboard has built in 120ohm resistor for termination, so you don't have to worry about terminating that end. At the other end of the CAN bus, the SZP provides the termination.
Ian
@P_a3 @chrishamm can you take a look at the error log?
From the dim LED on the Duet, it looks like the firmware has been erased. You will need to flash the firmware manually. You can do this from the SBC by connecting a USB cable between it and the 6HC, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards specifically the Bossa > Linux and Raspberry Pi tab.
Ian
@airscapes It's just been pointed out to me that the Duet 2 WiFi is EOL: https://www.duet3d.com/duetwifi
As of January 2024 The Duet 2 Wifi External Antenna and Duet 2 Ethernet are not recommended for new designs. The Duet 2 Wifi with Internal Antenna is End Of Life and no longer available directly from us, although some reseller may have limited stock. It is recommended to use one of the Duet 3 range for new designs going forward.
If you still want one, and Matterhackers don't have stock, then Filastruder probably does, and if they don't they order frequently enough that I'm sure they'd add one to their order if you pre-ordered it from them.
Ian
@airscapes There are some wiring differences, and some connector locations are different. Stepper driver connectors and thermistors/PT1000 are unchanged, and fans and BLTouch are all still Molex KK, you'll probably just need to use a different connector and move pins around. Heaters and VIN are different, using JST VH crimps and a barrier strip respectively, rather than screw terminals. See https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#description-of-connections versus https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mini_5+_Hardware_Overview
Pin names are different, but that should largely be limited to changing config.g, so I would imagine most macros should work unchanged. Yes, still uses the same DWC, and the SBC is optional.
Ian
@airscapes For a comparison table, see https://docs.duet3d.com/en/Duet3D_hardware/Hardware_overview
It really depends on your application, though if it's just a printer upgrade, I'd say go for the Duet 3 Mini5+. It is cheaper, has double the RAM and flash storage, can run with an SBC, and is CAN expandable. The Duet 2 is still supported by the current firmware, but due to the limited RAM and storage, features are being removed (mostly different kinematic models at present), and some new features (multiple motion systems, keepout zones) won't ever make it to Duet 2. It has the advantage of slightly more powerful stepper drivers (though without stealthChop), and having the Duex5 or EBoB for expansion, but that brings wiring headaches that CAN makes a lot easier.
We still have some demand for Duet 2's from OEMs, and make them in small batches, though we are encouraging them to move to Duet 3. No firm EOL date has been scheduled, as far as I am aware.
I mostly reach for a Mini 5+ over a Duet 2 nowadays. Though I have to keep my pre-production white PCB Duet 2 going in something!
Ian
@appjaws It's M950 with J parameter to create inputs/triggers, not P, which is for outputs. So should be:
M950 J6 C"zstop"
M581 P6 T2 R0 ; Set Z stop as fail safe for Z zeroing and run /sys/trigger2.g
M950 J7 C"e2stop"
M581 P7 T3 R0 ; Set Emergency stop and run/sys/trigger3.g
Make sure zstop and e2stop are not defined anywhere else.
Ian
@Gianluca Hi, I have watched your videos, and also tested updating here on a v1.2a 1LC.
One thing I noticed is that if I disconnect the CAN cable, then I hold down the buttons and power up, I get an initial flash of the STATUS LED (like yours does), then let go of the buttons after a few seconds, I get a constant flashing on the red STATUS LED. I think the bootloader falls back to the firmware if it doesn't receive a response from the mainboard, but yours is then crashing. This makes me think that the firmware on your board is corrupted, and possibly stuck in a boot loop. However, pressing the two buttons on power up should allow it to request a new firmware, even if the current firmware is corrupt. Which makes me think there is a problem with the CAN cable, but it's possible there is some other fault with the board.
With the 1LC not finding a CAN connection, I think the main issue is with the CAN cable. Even with no firmware, or when pressing the buttons, you should still get a CAN connection. You said you replaced the cable, but to me it appears to still be a problem. Please try making a new cable. Do you have a working toolboard at the moment that you can test with?
Also, check your CAN termination. I see you have a resistor connected to the CAN connector on the toolboard, does that mean you have NOT soldered the CAN termination jumper on the back of the board? You shouldn't do both. We recommend bridging the CAN termination jumper on the back of the board, see https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#terminating-resistor
If you stick with the resistor, make sure it is properly connected and providing resistance. Measure the resistance on the pins of the CAN cable connector.
I'm not sure what was causing the initial problem of the memory error, but hopefully we can get back to that.
Ian
@developeralgo222 said in Does Duet 6XD support RS485 communication:
i have 6XD not 6HC
6XD is the same: https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#inputoutput-port-capabilities
Ian
@developeralgo222 on the 6HC io1 and io2 are UART. The Paneldue connector shares pins with io1. See https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6HC_Hardware_Overview#inputoutput
M260 may be sufficient to send what you need, I don’t know the communication protocol your device uses: https://docs.duet3d.com/User_manual/Reference/Gcodes#m260-i2c-send-andor-request-data
@DonStauffer recently did something similar to control an external NeoPixel driver https://forum.duet3d.com/topic/35384/neopixel-driver-results
Ian
@developeralgo222 Currently, RRF doesn't support RS485, or ModBus.
RS485 and ModBus support has come up a few times in the past, though there doesn't seem to have been a feature request for it in https://github.com/Duet3D/RepRapFirmware/issues
In the past, @dc42 has said that it should be relatively easy to add support, by connecting a RS485 adapter to one of the UART ports. Modbus RTU support requires adding a relatively small amount of firmware to RRF including a MCode command to read is, perhaps a variant of M260/261.
If you're using a Raspberry Pi in SBC mode, you can get RS485 hats eg https://thepihut.com/products/rs422-rs485-serial-hat, and set up ModBus RTU eg https://www.instructables.com/How-to-Use-Modbus-With-Raspberry-Pi/. You may be able to use custom Gcode to control this, though you might need a little signposting from @chrishamm on how to set this up.
Ian
@kcorbedsellig Macs have a particular problem flashing the 6HC; we’ve tried to update Bossa to work, but it steadfastly refuses. However, if you have an SBC, you can flash it from that, using the terminal command line version of Bossa. You’ll need to manually erase the board using the erase jumper first. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards specifically the Bossa > Linux and Raspberry Pi tab.
Ian
@kcorbedsellig would love to see that!
Yes, for the firmware update, just upload your .bin file in DWC. It should ask you if you want to install it.
Ian
@NeoDue I did an example diagram of M599 for a talk @dc42 did last year. I could probably share that.
Ian
@HeidiH I've edited your macros with how they should look, with the forum code tags. Please check it is correct.
Ian
@achrn I think soldering is best. When soldering wires together, I tend to do a 'Lineman splice' - https://en.wikipedia.org/wiki/Western_Union_splice. You strip off more insulation than you expect, then bend the wires around each other tightly, a bit like tying a fisherman's bed in rope, before soldering (not forgetting the heatshrink). The twisted joint stays together a bit easier, so you can put each side in the helping hands without it coming apart. There are plenty of guides around.
There are also low temperature solder sleeves, which are a bit easier to use, and seems to be what NASA likes to use: https://workmanship.nasa.gov/lib/insp/2 books/links/sections/407 Splices.html. That also shows crimped splices. Or Wago connectors, if you want to stay away from soldering irons, but I haven't tried them.
Ian
@aytact Were you able to capture an M122 report? While your may be running from a UPS, your PSU may be failing. Or there was a momentary power loss, and it takes time for the UPS to kick in. Hard to say without more info.
Ian
@omtek I'm asking the same questions! I'll let you know.
Ian
@omtek We think the issue is the deployprobe.g file that controls the probe. If you have an M400
in there, change it to M400 S1
. I think this change has been brought about by some tweaking to the multiple motion system code. @Nurgelrot and @gloomyandy have been investigating this today, tip-o-the-hat to them!
Ian
@Festivejelly Can you have a look at the tests I posted here https://forum.duet3d.com/post/337624, and see if it helps? Otherwise, I think a(nother) warranty replacement is in order.
If so, please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
Ian