@omtek I've got a bug fix ready for v3.5.2 which we will release sometime soon.
Posts made by chrishamm
-
RE: 3.5.1 - 'Error: Pop(): stack underflow on Aux'
-
RE: No more free sessions
@tomasf It sounds like the web interface keeps losing the connection and attempts to create new sessions too frequently. Can you please do the following:
- Try to connect using the IP address (get it via
M552
) - Open the browser dev tools via F12 and check if there are HTTP
503
responses
Do you have a PanelDue as well?
- Try to connect using the IP address (get it via
-
RE: SPI connection reset on Duet 3 Mini 5+
@sgomes And the built-in reset button next to the USB jack has enough clearance?
-
RE: SPI connection reset on Duet 3 Mini 5+
@sgomes @droftarts I find it rather odd that the disconnect counters do not show anything, if there had been a protocol error, at least one of the counters should have been increased. Did you reset the board straight after the SPI connection reset? Or do you have a physical reset button connected anywhere? I'd suggest to disconnect that (if present) or check if the physical reset button does not make intermittent contact, because a reset button press is reported as the board's last reset reason.
If that does not change anything, you could replace the ribbon cable and/or shield it, and check if that helps.
-
RE: SPI connection reset on Duet 3 Mini 5+
@sgomes Can you please share the M122 output after the reset? Your first dump doesn't show an unexpected reset reason or a disconnect event.
What kind of microSD card are you using in the SBC? If it is only a standard microSD card, consider replacing it with an A1- or A2-rated microSD card.
-
RE: does duetpi support firstrun.sh?
@jhalewood It works just fine but note that the RPi imager also adjusts cmdline.txt AFAIK. I guess you need to do the same as well.
-
RE: Cannot expand global arrays in Object Model Plugin
@robotsneversleep Thanks for reporting this, I'm going to fix it in v3.5.2.
-
RE: duetpi will not run on usb ssd - raspbian will
@jhalewood You already did that by running the
rm
command. i suppose you could edit the file you removed again and exclude your boot device, but you'd have to look up how exactly (search for udev rules, I believe there's a statement to ignore certain UUIDs/names [sda1/sda2 in your case]). If you can live without auto USB mount support, just leave that file deleted.It's possible to rebuild DuetPi without that particular feature (see here and delete
stage-dsf/04-usb-automount
before you build it). -
RE: duetpi will not run on usb ssd - raspbian will
@jhalewood Thanks, that log shows more. It may be a conflict with the USB auto-mount setup that is exclusive to DuetPi:
Apr 19 19:37:01 duet3 (udev-worker)[299]: sda2: Process '/bin/systemctl start usb-mount@sda2.service' failed with exit code 1. Apr 19 19:37:01 duet3 (udev-worker)[311]: sda1: Process '/bin/systemctl start usb-mount@sda1.service' failed with exit code 1.
I suggest you disable that feature or edit the udev rule (
rm /etc/udev/rules.d/99-usb-automount.rules
) and check if that fixes it. -
RE: Duet 2 Ethernet DWC disconnecting since upgrading to 3.5.1
@clegg78 Try to increase the number of AJAX retries in the DWC settings -> Machine-Specific -> Communication to 4 or 5, that should help. We're working on a fix.
-
RE: duetpi will not run on usb ssd - raspbian will
@jhalewood The main difference between the standard RasPi OS and DuetPi is AppArmor. You could try to disable that (remove
lsm=apparmor
from the cmdline and disable theapparmor
service) and check if it boots up correctly then.I can't see any obvious reason why it starts the emergency shell but perhaps a more verbose boot screen shows more (remove
quiet
andsplash
from the cmdline). -
RE: 3.5.1 forgets whether filament is loaded with M999
@achrn Thanks for the config, I could reproduce this problem and I will work out a fix. It looks like something in your config prevents the
move
key from being properly refreshed. If I runM906 E1234
(as an example), the assigned filament shows up as expected.Edit: I've got a bug fix ready. I suggest you change something that modifies the
move
key at the end of your config.g (as I did with M906 E...) to work-around this problem for now. -
RE: Raspberry PI camera issue with AppArmor
@Ant1 Did you add
webcamAccess
to your plugin privileges (see here)? Note that you need v3.5 and ideally the latest DuetPi image based on Debian Bookworm to access the new Pi webcam interface. It does work with the Spyglass webcam server plugin on Bookworm and with 3.5. -
RE: Odd appearance in M291 window
@OwenD Thanks for reporting this, I'm going to fix it in v3.5.2.
-
RE: 3.5.1: Duet2+SBC firmware crash-loops
@resam I've updated the reprapfirmware package again with a working 2SBC build of RRF 3.5.1. A regular system update should work correctly now.
-
RE: 3.5.1: Duet2+SBC firmware crash-loops
@resam I can confirm this problem and we're working on a fix. For the moment, you can use the 3.5.0-rc.4 2SBC build which does not suffer from this problem.
-
RE: Duet web control connection interrupted
@Gamefanatic3D Do you have a PanelDue connected as well? We're investigating another bug report that might be related. I suspect your object model response exceeds a given size causing random disconnects. You may also find that increasing the AJAX retries on the Settings -> Machine-Specific -> Communication panel to e.g. 4 or 5 may help.
-
RE: 3.5.1 forgets whether filament is loaded with M999
@achrn Odd, it comes back correctly on my setup after
M999
. A few questions: Does a page reload show the correct filament again? And if you open the browser dev tools via F12, can you see any errors in the JS console? DoesM409 K"move.extruders" F"d99"
show the correct filament? Your config.g may be helpful, too. -
RE: 3.5.1 forgets whether filament is loaded with M999
@achrn I don't think I've seen that problem before and the underlying code hasn't changed for ages. Is it possible that you upgraded to Debian Bookworm and/or uploaded filament.csv via FileZilla to the SD directory? If yes, you may need to adjust the permissions again, else RRF cannot overwrite that file and it will "forget" the last mapping. You can fix the permissions via SSH by running
sudo chown -R dsf:dsf /opt/dsf/sd
. Please check if that fixes it. -
RE: /usr/bin/env: ‘python3’: Permission denied
@Ant1 Can you share the full plugin ZIP?