@dc42 I'm using a 3HC.
I can try using 2 27K resistors like you mention and see if that helps.
Thank you.
@dc42 I'm using a 3HC.
I can try using 2 27K resistors like you mention and see if that helps.
Thank you.
I'm using some 24V pressure sensors on my printer that require pulldown resistors. I'm using 10K resistors, so the IO_IN pins are sinking 0.0024A, is that ok? They seem to be working but intermittently they sometimes read incorrectly. I don't see anywhere in the documentation how much current the IOs can tolerate, other than a voltage spec.
Thanks.
I have a safety system in place on my printer where multiple sensors (door close sensors, air pressure relays, overtravel switches, etc.) must be in a certain state for the heating elements and motion system to work. I would like to control this external system with the Duet like this:
-Door is closed (servos and heaters are powered), user attempts to move axis with PanelDue, axis moves.
Is there some sort of state-change script that could be run, like inactiveToActive.g or ActiveToInactive.g where I could write a script to check the status of a series of inputs and bail with an M99 if they aren't met?
@Phaedrux daemon.g
heaterFaultBed.g
heaterFaultChamber.g
Also, I'm stuck at connecting... again.
I modified config.g so that my bed and chamber heaters were no longer combined and I think that solved the entire issue. I was experiencing it in this thread but never got it resolved.
https://forum.duet3d.com/topic/34758/tips-for-autotuning-a-very-large-heated-chamber?_=1710270256740
It seems to be correlated with my config.g file. Adding that back in sometimes, but not all the time, prevents it from connecting...
See anything that might cause the instability?
config.g
DriveSetup.g
startup.g
@jay_s_uk No dice. Even tried updating the web control files according to the documentation.
@jay_s_uk It shouldn't have changed, it was working great on 3.5.0 RC3. During the ordeal, I did attempt switching to stable and doing a downgrade according the documentation, which worked and DWC was connecting, but then when switched back to unstable, it started getting stuck at connecting... again. I want to also mention, that I have the printer beep at the end of the config.g file, and I hear it, so that means the code is at least running. It makes me think the issue is more on the web-interface side. I will try BOSSA and get back to you soon.
I've been banging my head against the wall all day, installed new images from scratch and no matter what I do, I get stuck at connecting.
My printer use to work fine, tried switching to a raspberry pi 5, didn't work, wanting to roll back to a 4 and now I can't get past this.
Setup:
6XD
(5) 3HC
(2) 1XD
Raspberry pi 4 in sbc mode
running 3.5.0 RC3
Worked great up until I tried to switch. Now I'm back with a freshly imaged sd card, ran updates, etc. The crazy thing is that it works fine for a while until I reboot, and then it's stuck. Note that I get this issue directly on the pi with a monitor/keyboard/mouse attached, and over the network.
Please help
@chrishamm I just installed a fresh image, and ran sudo apt update & sudo apt dist-upgrade, also ctrl+shift+r and am getting the same message. I updated the eeprom on the raspberry pi so hopefully that'll resolve the freezing issue.
running M997 S2 gives "Error: M997: Failed to perform update: Upgrade process return non-zero exit code"
Update: the issue seems to be that the sudo apt update/upgrade commands aren't doing anything regarding the duet board firmware. I confirmed this by connecting a Raspberry Pi 4 and running the commands again, and it was able to upgrade
However, after upgrading I still get this "incompatible software versions" popup no matter how many times I ctrl+F5. Note, this is on the raspberry pi itself with a monitor attached.
Also for the life of me, I can't get M997 S2 to work.
Edit: Just an update for anybody with a similar issue, I went back to a raspbery pi 4 with a SD card and updated to the latest firmware, then copy/pasted my sys and macros over to a newly imaged NVMe and that did the trick. My best guess is that it was the drive I was using. TeamGroup MP33 stalled but a Patriot P310 seems to work fine.
Any ideas what might be causing this "incompatible software versions error?"
Also I'm running this on a Raspberry Pi 5 8GB with an NVMe hat and noticed that I'm getting freezing every few seconds. Any ideas there?
@T3P3Tony refreshing the page seems to work fine. I know what you mean though, sometimes before when I refreshed the page it wouldn't reconnect.
@chrishamm So far I'm not getting any more issues connecting to the web interface with the heaters combined now, just errors that the DWC versions don't match.
@chrishamm I can, I'll get back to you on it...
@chrishamm How do I generate that?
@chrishamm I'm powering the pi via a usb C supply. My suspicion is that because the freezing happens at a regular pace, perhaps it has to do with the daemon.g. Is that possible?
@chrishamm I changed the settings and restarted and got the error, I didn't even have to autotune.
journalctl -u duetcontrolserver -f
Also I should mention that putty freezes up very frequently when this error happens.
@chrishamm I'll have to put that code back and run a PID autotune again, I'll get back to you with an update.