Posts made by kiendeleo

@chrishamm okay, I just wanted to submit the bug

With Duet 3.5.0 being released, I decided I would run

apt update && apt upgrade

on my RPI5. I am getting the following errors.

rr:1 https://pkg.duet3d.com stable/armv7 arm64 duetpimanagementplugin arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:2 https://pkg.duet3d.com stable/armv7 arm64 duetpluginservice arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:3 https://pkg.duet3d.com stable/armv7 arm64 duetsoftwareframework arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:4 https://pkg.duet3d.com stable/armv7 arm64 duettools arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:5 https://pkg.duet3d.com stable/armv7 arm64 duetcontrolserver arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:6 https://pkg.duet3d.com stable/armv7 arm64 duetruntime arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Err:7 https://pkg.duet3d.com stable/armv7 arm64 duetwebserver arm64 3.5.0~rc.4+2
  404  Not Found [IP: 134.209.94.168 443]
Ign:8 https://pkg.duet3d.com stable/armv7 arm64 reprapfirmware all 3.5.0~rc.4+2-1
Err:8 https://pkg.duet3d.com stable/armv7 arm64 reprapfirmware all 3.5.0~rc.4+2-1
  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetpimanagementplugin_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetpluginservice_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetsoftwareframework_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duettools_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetcontrolserver_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetruntime_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-arm64/duetwebserver_3.5.0%7erc.4%2b2_arm64.deb  404  Not Found [IP: 134.209.94.168 443]
E: Failed to fetch https://pkg.duet3d.com/dists/stable/armv7/binary-armhf/reprapfirmware_3.5.0%7erc.4%2b2-1_all.deb  404  Not Found [IP: 134.209.94.168 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Is this something wrong on my end?

@jay_s_uk I didn't know that existed; I will try that...

@chrishamm I found this thread while trying to get a new RPI 5 working with my duet board using this guide: https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other

I am getting an SPI buffer size error. I am not sure if I am doing something wrong or if this is a known issue that you are working on, but I thought I would drop it here and see if it helps.

After crashing my printer several times in the middle of a print because I ran out of space, I would like to figure out a way to save the images from the Motion plugin to a USB drive. It seems that the Pi automatically mounts the USB drive to /media/pi/[Name of USB Drive]. I can probably change how the device automatically mounts on insert, but I am curious about what user the motion server runs through the plugin. Am I pursuing the correct method to solve this problem?

@dc42 Good to know thank you

I am working on the proper implementation of the Toolboard connected directly to the 6HC Mainboard on a CoreXY machine. In the documentation, I noticed this:

We recommend connecting the hot end metalwork to ground on the toolboard via a resistor (10k to 1M Ohm), if it is not grounded through its mounting system. This will prevent the hot end building up static charge, which might otherwise occur as filament is extruded and may then flash over to the tool board thermistor input, causing damage.

What are the best practices for this?
Can you hook the resister to the ground of an unused port or does it need to be the primary power port?
Is there a ground plane on the tool board that is hooked to the screw mounts like on a computer motherboard?

@phaedrux I didn't find that forum post when I searched for this error, weird. Thank you for your help.

This was the fix:
@chrishamm said in MotionWebcamServer plugin - Missing library:

@adammhaile @luckyflyer Very odd, it looks like something changed because this definitely worked for me before on another image. The problem is indeed that motion cannot open /opt/vc/lib/libvchiq_arm.so. To fix this, you can edit /etc/apparmor.d/dsf.MotionWebcamServer and insert a new line below /usr/local/lib...:

  /opt/vc/lib/** rm,

Then reboot the Pi or run sudo apparmor_parser -r /etc/apparmor.d/dsf.MotionWebcamServer and you should be able to start the plugin from DWC.

It looks like there is also an issue with Motion's custom log file location for permission:

motion[1762]: [0:motion] [EMG] [ALL] motion_startup: Exit motion, cannot create log file /var/log/motion/motion.log: Permission denied

This is an optional configuration item though so the short-term fix is to just disable the feature.

@phaedrux yes

@phaedrux Here you go

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9FA-3SJ6M-1B0UG
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 66280 of which 128 recycled
Never used RAM 133192, free system stack 154 words
Tasks: SBC(resourceWait:,17.1%,474) HEAT(notifyWait,0.4%,321) Move(notifyWait,0.1%,262) CanReceiv(notifyWait,0.7%,772) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.2%,339) TMC(notifyWait,257.6%,92) MAIN(running,3003.1%,923) IDLE(ready,0.4%,30), total 3279.5%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:38:26 ago, cause: software
Last software reset at 2022-03-30 10:18, reason: User, GCodes spinning, available RAM 133480, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 39.0, current 40.2, max 40.4
Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.7, current 12.0, max 12.6, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 328, reads 16547, writes 24 timeouts 0
Driver 1: standstill, SG min 0, mspos 888, reads 16548, writes 24 timeouts 0
Driver 2: standstill, SG min 0, mspos 600, reads 16553, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 824, reads 16553, writes 19 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 16561, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 16561, writes 11 timeouts 0
Date/time: 2022-03-30 11:56:50
Slowest loop: 55.18ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 4478021ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 11, completed 11, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 53162, received 121055, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 264, free buffers 50 (min 49), ts 29534/29533/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 9912/9912
SPI underruns 0, overruns 0
State: 5, disconnects: 2, timeouts: 2, IAP RAM available 0x2b880
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.02, max time between full transfers: 56.3ms, max pin wait times: 53.6ms/4.2ms
Codes per second: 0.01
Maximum length of RX/TX data transfers: 3184/252

I am getting the following error in the syslog when I try to start the webcam server plugin:

Mar 30 10:30:30 TRONXY-X5SA-Pro DuetPluginService[688]: [info] Plugin MotionWebcamServer: Process has been started (pid 986)
Mar 30 10:30:30 TRONXY-X5SA-Pro kernel: [  110.702719] audit: type=1400 audit(1648661430.736:18): apparmor="DENIED" operation="open" profile="/opt/dsf/plugins/MotionWebcamServer/**" name="/opt/vc/lib/libvchiq_arm.so" pid=986 comm="motion" requested_mask="r" denied_mask="r" fsuid=996 ouid=0
Mar 30 10:30:30 TRONXY-X5SA-Pro DuetPluginService[688]: [error] Plugin MotionWebcamServer: /opt/dsf/plugins/MotionWebcamServer/dsf/arm/motion: error while loading shared libraries: libvchiq_arm.so: cannot open shared object file: No such file or directory
Mar 30 10:30:30 TRONXY-X5SA-Pro DuetPluginService[688]: [info] Plugin MotionWebcamServer: Process has been stopped with exit code 127

I have a Duet 3 with a Tool Board with an SBC running the official image.

Any help would be appreciated.

It looks like the issue was a reversed power and ground wire on my magnetic filament monitor.

@phaedrux Well, I might have figured out what this might be.... @ctilley79's comment made me think so I unplugged everything except the thermistor and heater cartridge, and now the thermistor is responding correctly... weird

@phaedrux M98 P"config.g" did not create a result in the console

@phaedrux Here you go:

config.g

M112.txt

M112 B20.txt

I purchased a tool board and distribution board from Filastruder. I wired the tool distribution board to my Duet 3 6HC control board and my printer's 24v Power Supply using the included data cable and some 20 Gage wire for power. I hooked the Tool board to the Distribution board with more 20 Gage for power and some 22 Gage wire crimped onto the provided tool board connectors. I was able to get the tool board to connect and the led's on the tool board and the 6HC stay in sync. I was even able to do a firmware push from the mainboard. However, nothing plugged into the tool board seems to work. Both thermister ports give wildly fluctuating readings, both with a thermister (Slice 300C) plugged in and the same reading with the thermister unplugged.

Am I doing something wrong?

By way of wrapping up this thread, the solution I found that works well is as follows:

Power Supply 24v to the board, a 5v Converter, and a USBC Converter. The 5v converter is wired to the 5v external power header on the board with the jumper selected to the External 5v. The 5v converter is also wired directly to the Neopixels that I am running to ensure that they get sufficient power in case there is a limit through the board ( I am using 60 Neopixels for this printer) only ground and signal are hooked to the LED header on the board. I am powering the Pi4 off of the 24v to USBC converter.

Links to the parts on amazon:
24v to 5v converter: https://smile.amazon.com/gp/product/B01M03288J/
24v to USBC Converter: https://smile.amazon.com/gp/product/B07ZQB6S3L/

I have a 1.01 version Duet 3 Mainboard that I am trying to run with a Pi4 attached via the included ribbon cable. I am getting low voltage warnings regardless of whether I use the internal power supply or if I add an external voltage regulator. From what I can find, the Pi4 had too great of power requirements for it to be powered from the board, especially if DotStar/NeoPixels are used. I have not tried to add LEDs yet, but I plan to. What is the proper way to make sure that the Pi and the LED's are powered correctly and the grounds are maintained for all of the components?

My current setup:

24v 15a Power Supply connected to Power In, Out0 Power In, and Power in on a 5v 10a power regulator.
5v out on the power regulator is also attached to EXT 5v
Internal 5v Jumper is removed.

I assume this is not going to work as I am still getting power drops on the Pi. Should I create my own SBC Cable that exposes the power and ground pins and power via the GPIO so the common ground is maintained? Can the Pi be powered via USBC when the Shipped SBC cable is used? What is the "right" way to do this?

@t3p3tony Thank you for the quick responce. Is there somewhere I can go to track the progress of the Magnetic filament sensor?

I have been looking to buy a duet 3 mainboard and a filament monitor for a while, but I have noticed that stock seems to be a bit unreliable. I know there are worldwide supply-chain issues with electronics, but I am curious if this is what is affecting the supply of these devices.

I am also curious if the laser filament monitor or the magnetic filament monitor are the recommended device for future use.