How are you powering the servo? On my tool changer I have a separate 5v bus for things like the servos so that they don't overdraw from the duet 5v bus. My RPI4 sometimes indicates a low power situation with JUST it and the duet, no usb in the pi, no servos or other 5v draws from the duet 3 board.
Posts made by RobMink
-
RE: Issues with servo on Tool Changer after firmware update 3.1.1
-
RE: Here's my printable optical encoder wheel filament sensor!
@fractalengineer Whoops, thanks, that was dumb.
-
Sequencing issues with Duet3 and Exp boards
I am still getting occasional sequencing issues with my Duet3 and exp03 boards. The printer will not wait for the gantry to be in the right position to execute a tool change using the servo. The servo is on the main board and the core xy motors are on exp03 board 1.
This does not happen all the time, but often enough to mess up a print. DWC 3.1.1, RC11. I am wondering if this issue would go away if I put the core XY motors on the same board as the servo.Thanks in advance!
-
RE: Temporary failure resolving 'pkg.duet3d.com'
Its working again. Consider it solved.
Thanks! -
Temporary failure resolving 'pkg.duet3d.com'
I am having issues upgrading my SBC Pi4 with a Duet3.
pi@duet3:~ $ sudo apt-get update Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease Err:3 https://pkg.duet3d.com unstable InRelease Temporary failure resolving 'pkg.duet3d.com' Err:4 https://pkg.duet3d.com stable InRelease Temporary failure resolving 'pkg.duet3d.com' Reading package lists... Done W: Failed to fetch https://pkg.duet3d.com/dists/unstable/InRelease Temporary failure resolving 'pkg.duet3d.com' W: Failed to fetch https://pkg.duet3d.com/dists/stable/InRelease Temporary failure resolving 'pkg.duet3d.com' W: Some index files failed to download. They have been ignored, or old ones used instead. pi@duet3:~ $
I don't know if it is a DNS issue on my end or if something is down.
Thanks!
-
RE: Here's my printable optical encoder wheel filament sensor!
What size bearing does it use?
-
RE: Duet3 requires BOSSA flash if more than 1 exp boards.
Just did the latest FW update, it went flawlessly.
-
RE: Duet3 requires BOSSA flash if more than 1 exp boards.
Hmm, Ok. I will try that as soon as the printer is done printing and I have a wee bit of down time. Thanks!
-
RE: Duet3 requires BOSSA flash if more than 1 exp boards.
Hmm, thanks for the info. I am 99.99% sure that right now if I where to upload a new firmware file for the Duet3 or an expansion board I would have to re-flash the firmware using Bossa.
Here is my setup.
-
Duet3 requires BOSSA flash if more than 1 exp boards.
If i leave more than 1 exp board connected to the duet3 main board and run an upgrade from the RPI CLI or upload new firmware and let DWC run an upgrade the duet3 bricks. I must then erase, flash using bossa, then update each board by setting its id to 1, hooking it up as the only board and then M997 B1 ing it. The last board in the series (#3 for me) updates fine. (I have issues with M997 B1 if it is not the only board and always an issue with M997 B2) I get errors that the Duet3 has lost connection when upgrading the exp boards, and lots of can errors. I also get an error blink on the board I am attempting to upgrade
In short, if more than one exp board is attached firmware upgrades always fail through DWC. To update the exp boards they must be the last board on the can bus.
This has been an issue throughout all upgrades I have done. I wanted to explore the bug a little more than just 'upgrades fail.'
-
RE: M400 / G4 P0 Not working?
Yep! Thanks for all the great work! I thought it would give it a shot when I saw that release note.
-
RE: M400 / G4 P0 Not working?
Upgrading all using a sudo apt-get/apt-upgrade to RC10 and removing the M400 fixed the issue.
-
RE: M400 / G4 P0 Not working?
Ok, I gave that a go. It releases the tool correctly and pulls back, pauses, but does the 'grab' command (M280 P0 S150) for T3 en route to T3. I can post a video if that would help.
-
RE: M400 / G4 P0 Not working?
It happend after I went from T0 to T3.
M280 P0 S40 is the tool release command, and the M280 P0 S150 tool grab command happens before the printer isin position to grab the tool.
Here is
; tfree0.g ; called when tool 0 is freed G1 X96 Y760 F5000 G1 Y800 F1200 M280 P0 S40 G1 Y830 F2400 G1 Y760 F2400
Should I put a G4 P1000 or something in the end of this file and test?
-
RE: M400 / G4 P0 Not working?
I tried a USB connection again, and this time it (USB) worked. Not sure what caused the issue the first time.
SENDING:M111 P3 S1 Debugging enabled for modules: GCodes(3) Debugging disabled for modules: Platform(0) Network(1) Webserver(2) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16) >>> T0 SENDING:T0 USB: T0 USB: G1 X96 Y760 F5000 USB: G1 Y830 F2400 USB: M400 USB: M280 P0 S150 USB: G4 P500 USB: G1 Y800 F2400 USB: G1 Y760 F3600 USB: M116 P0 USB: M105 >>> T3 SENDING:T3 USB: T3 USB: G1 X96 Y760 F5000 USB: G1 Y800 F1200 USB: M280 P0 S40 USB: G1 Y830 F2400 USB: G1 Y760 F2400 Queue: M280 P0 S40 USB: G1 X306 Y760 F5000 USB: G1 Y830 F2400 USB: M400 USB: M280 P0 S150 USB: G4 P400 USB: G1 Y800 F2400 USB: G1 Y760 F3600 USB: M105
All the edits! Oops!
Ok, so a little clarification, the tool 0 docking in the last chunk after T3 ends at USB: G1 Y760 F2400 and T3 picks up at USB: G1 X306 Y760 F5000
-
RE: M400 / G4 P0 Not working?
Thanks for the info!
If I run the command M98 P"tpre3.g" it works, but if I just go T0 T3 it does not. T0 will load correctly the first time, then exhibit the same behavior. I apologize if this is a bug on my end!
EDIT: I tried plugging the duet into my laptop and running pronterface. I get "Board 1 does not have input handle 1000" when I try and home until I reboot the printer afterwards.
-
RE: M400 / G4 P0 Not working?
Sorry, I forgot what the abbreviation was and had to look it up. I gleaned this from the apt-get upgrade
Setting up duetsoftwareframework (2.1.0) ...
Thanks again! -
RE: M400 / G4 P0 Not working?
Sorry, yes, Duet3 with 3 exp boards, RPI4 with DSF 2.1.4
The Servo is on the main board and the core xy moment system is on the EXP1 board. Could that be causing the issue?
-
M400 / G4 P0 Not working?
Latest Release 3.01 - RC9
My tool changer used to wait to activate the servo for tool changing. Now after updating today the servo moves right at the beginning of the moment for the tool change.
This is my 0:/sys/tpre3.g For tool 3. This happens with all tools.
G1 X306 Y760 F5000 - Servo Moves concurrently with this commnad.
G1 Y830 F2400
M400 - I know this is redundant
G4 P400
M280 P0 S150 - Should move here, of course, after finishing above moves.
G4 P400
G1 Y800 F2400
G1 Y760 F3600
G10 P3 Z0.9Thanks for taking the time to read this!