@droftarts Thank you for the replies, I now have my head around the object model's Arrays, Objects and Value. I installed the plug in, studied it and was able to 'pluck' values using the echo command for eg;

echo boards[0].mcuTemp.current

boards is an array, element 0 holds mcuTemp with the value current

I seem to have run into another problem on using the 6XD I/Os. There are opto isolated inputs and outputs as well as the GPIO inputs and outputs.

Maybe I am not understanding but if I try to configure number 8 opto as well as number 8 GPIO out like the following in config ;

M950 S9 C"io8.out" ; GPIO 8 M950 S8 C"!io8.out.iso" ; Isolated out 8

Then save, reset, and run

M98 P"config.g"

Returns

Error: Pin 'io8.out.iso' is not free

Another bruise on my head, This the only use of io8.out.iso
Not sure how io8.out.iso is the same as io8.out ???

The same happens with io8.in.iso and io8.in .

Is it a case of only being able to use one or the other??

On the positive,
I linked io8.out to io8.in with a jumper wire.
The following worked to setup a digital output and input.

M950 P9 C"io8.out" M950 J2 C"io8.in"

In config.g, save and reset

M42 P9 S0 ;Turn off the output echo sensors.gpIn[2].value ;Check the input M42 P9 S1 ;Turn on the output echo sensors.gpIn[2].value ;Check the input

Not sure where to check the output status in the object model ??

Hope this helps someone who comes across this who is trying to turn on off an output / check an input etc before they plant their fist into the screen.

Thanks Mark

@yoshimitsuspeed the IR probe does not work as a scanning probe but dc42 indicated it should be pissible to turn it into one with firmware modifications. Nobody has indicated that this work is planned though.

on my workplace i use FDM Printed parts quite frequently for Workholding Jigs.
either on a CMM or on a Mill to get oddly shaped SLM Printed parts to behave.

Printed stuff like a Door Dampener out of 60A TPU to prevent a door to slam shut during the summer months when i have a window open
also for a family member a guideblock for a Circular saw because of poor Manufacturing tolerances the included one had way to much play

@oliof said in Motor problems on RatRig V-Core 3:

The duet boards are best cooled by blowing a bit of air above and below the board along the drivers.

Hindsight IS def 20/20 here...If I only saw that in the documentation from RatRig when I built it. They did mention that passive cooling should be enough...but the standoffs they provided to mount the Duet 3 Mini 5+ were simply not up to par.

My brother has a real nice O-Scope, so will prob send to him to check it out.

Many thanks again, for your sage advice. You are a credit to the forum here more certainly!
I did post pictures of my wiring and even some FLIR thermal pictures, which did show the drivers getting hot, so I should have realized to check the thermal limits before trying to run some test prints. Doh!

Regarding the Octopus drivers, I agree that the duet PCB wicks better, but with the 120mm Noctua PWM fanmounted directly above the board, I think it will cool down fairly well.

Thanks again for the reply- duly noted.

@Chris-S
M574 defines whether you're homing to the low or high end.
It sounds like you're homing to the high end, so the value when the stop triggers should be max travel as set by M208
You'd need to post your config.g so that it can be examined properly.

@bugpwr said in resume redundant extrusion:

by the way, I am having some (unrelated) motion troubles with the beta3+1. On a couple of incidents homing commands got stuck (e.g. G1 H1 Y480 F5000) I did not investigate further.

That is the second line of a 2-line error message. The first line includes a single-digit error code, which I need to know to investigate this further.

@dc42 said in Reading values from digital Vacuum Pressure sensors:

@developeralgo222 I suggest you remove the leading ! from the analog pin names in your M308 commands, and add B and C parameters to those commands to define the reading range.

You only need to use voltage dividers if you want to take readings when the sensor output exceeds 3.3V. If you don't then you will likely get the same reading as an input of about 3.3V would. A voltage divider is just 2 resistors so you can make one yourself, e.g. 2K from the input pin to ground and 1K from the input pin to the sensor output.

Hi dc42

I am now trying to get my vacuum sensors to work, 5V sensors driven from 6XD and I get Vswing from ~5V to 0v on sensors but connecting Vdivider as suggestes I get nothing.

What can be wrong?
Bengt

@T3P3Tony I switched it to Out9 and it works fine. Go figure.

@T3P3Tony Email sent, thanks for your help.

@droftarts This fixes my problem thank you.

@droftarts Hi Ian, sorry for the delayed response, only just got back from my trip

Thank you very much for offering a replacement board, its incredibly generous of you!

I've attached a full copy of the M122 report and some photos of the SD slot just incase there is anything that would suggest another issue (would prefer not to cause a bother with a replacement if it can be avoided)

Thanks again,
Zac

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 35ZY3-SN6KL-K65J0-409N8-JFW1Z-ZF6NL
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 119484 of which 0 recycled
Never used RAM 18768, free system stack 156 words
Tasks: NETWORK(1,ready,6.5%,505) HEAT(3,nWait 6,0.0%,369) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.0%,121) MAIN(1,running,90.4%,876) IDLE(0,ready,2.2%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:22 ago, cause: power up
Last software reset at 2025-01-19 15:31, reason: User, Gcodes spinning, available RAM 6088, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 107312, completed 107312, timed out 0, errs 0
MCU temperature: min 23.8, current 25.8, max 26.2
Supply voltage: min 0.3, current 0.8, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 302689886
Slowest loop: 0.28ms; fastest: 0.15ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 0.2MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "M122" 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 715, received 0, lost 0, errs 689203, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 715/0/0
Tx timeouts 0,0,714,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 0.25ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: disabled
Module is disabled
Failed messages: pending 0, notrdy 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
20250123_205346.jpg 20250123_205406.jpg

@droftarts Okay , 🙏 thank you.