@droftarts said in Accelerometer on toolboard 1.3 : positioning:

I have updated the documentation page using images from the pdf kindly supplied by @Nuramori. Unfortunately I can't upload pdfs to the wiki software, so I have left the original link in.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer#orientation

Ian

nice documentation update for orientation toolboard !
thanks a lot @droftarts !
little pics of my config on a RR-Vcore 500 on duet 5+mini with toolboard (Ir sensor on toolboard)

@Phaedrux
thanks it' solved with manualy update firware (copy past firmware on sd card )

I tested all the boards independently
I have toolboard 0 (adress20) which creates a conflict for me in the general can bus
I am reconfiguring a toolboard to replace it
thank you

OK you awsome
My M140 H0 was after M143 so now it would be good

M143 H0
Heater 0 monitor 0 uses sensor 0 to generate a heater fault if the reading exceeds 180.0°C
Heater 0 monitor 1 is disabled
Heater 0 monitor 2 is disabled

thanks a lot guys

I just received my LLL PLUS Buffer from Mellow 3D.
I'd like to connect it to my Duet to retrieve buffer information. The Duet also has information about filament progress and breakage.
Here's the device's date sheet:
https://mellow.klipper.cn/en/docs/ProductDoc/ExtensionBoard/fly-buffer-plus/?persistLocale=true
It must be connected to 12/24V and has a switch pin and a motion pin.

Thank you.

@droftarts said in Accelerometer on toolboard 1.3 : positioning:

I have updated the documentation page using images from the pdf kindly supplied by @Nuramori. Unfortunately I can't upload pdfs to the wiki software, so I have left the original link in.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer#orientation

Ian

nice documentation update for orientation toolboard !
thanks a lot @droftarts !
little pics of my config on a RR-Vcore 500 on duet 5+mini with toolboard (Ir sensor on toolboard)

@droftarts
thank a lot
now I just have to understand the graphics those who haven't won yet!

@droftarts this link no longer works on dropbox
Attached is a photo of my toolboard on my machine with the axes, which configuration on the accelerometer should I use for the position of the accelerometer
THANKS

it s correct for the orientation of accelerometer?
M955 P121.0 I54 ?good orientation?
thanks

hi
I would like to have a diagram for the positioning of the toolboard and its accelerometer to configure it on my Vcore
Nuramori's "graphical guide to help illustrate the orientation options" link no longer works on dropbox
Thanks

@Phaedrux
thanks it' solved with manualy update firware (copy past firmware on sd card )

M997 S0:1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found<LF>ok<LF>

DuetWiFIServer.bin is in my system file (263Ko)

board>>duet 2 wifi
after updating to 3.4.5, I can no longer connect to my board's wifi (i can control printer with duet panel)
To talk with the board I use YAT

m122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later<LF>Board ID: 08DJM-9178L-L4MSN-6JTD8-3SS6N-K82YQ<LF>Used output buffers: 3 of 26 (11 max)<LF>=== RTOS ===<LF>Static ram: 23836<LF>Dynamic ram: 75420 of which 0 recycled<LF>Never used RAM 12824, free system stack 192 words<LF>Tasks: NETWORK(ready,8.3%,517) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,91.7%,412) IDLE(ready,0.0%,30), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:05:08 ago, cause: power up<LF>Last software reset time unknown, reason: User, GCodes spinning, available RAM 12752, slot 0<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max interval 0<LF>MCU temperature: min 29.3, current 29.8, max 30.4<LF>Supply voltage: min 0.1, current 0.4, max 0.5, under voltage events: 0, over voltage events: 0, power good: no<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Events: 0 queued, 0 completed<LF>Driver 0: ok, SG min n/a<LF>Driver 1: ok, SG min n/a<LF>Driver 2: ok, SG min n/a<LF>Driver 3: ok, SG min n/a<LF>Driver 4: ok, SG min n/a<LF>Driver 5: <LF>Driver 6: <LF>Driver 7: <LF>Driver 8: <LF>Driver 9: <LF>Driver 10: <LF>Driver 11: <LF>Date/time: 1970-01-01 00:00:00<LF>Cache data hit count 4294967295<LF>Slowest loop: 101.16ms; fastest: 0.15ms<LF>I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest read time 1.1ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters 0 -1 -1 -1, chamber heaters 2 -1 -1 -1, ordering errs 0<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "m122" in state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty<LF>=== Network ===<LF>Slowest loop: 1.03ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)<LF>HTTP sessions: 0 of 8<LF>= WiFi =<LF>Network state is starting2<LF>WiFi module is disabled<LF>Failed messages: pending 0, notready 1, noresp 0<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>

m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2022-11-30 19:36:12<LF>ok<LF>

m552
WiFi module is being started<LF>ok<LF>

wifi module isn't IDLE with M552
I think the wifi of the board has a problem can you help me thank you

@droftarts
it s too small for a photo

@droftarts said in Duet 2wifi fan not working (mosfet dead):

If that is okay, most likely the fan mosfets have failed. See https://docs.duet3d.com/User_manual/Troubleshooting/Parts#replacement-parts
The fan mosfets should show if they have failed. Post a good image of yours so we can check.
The usual reason for fan mosfets to fail is shorting the, connecting fans the wrong way around, or using a fan that draws too much current. As such, they are generally not covered by warranty. See our warranty terms here: https://www.duet3d.com/page/warranty-policy
If it is the fan mosfets, you can replace them yourself; see the link earlier for details of replacement mosfets.
Ian

Hi Ian
the first thing iam doing is verify fuse (ok)
the problem occurred after cleaning the nozzle due to a print crash (full of plastic all over the nozzle)
the installation has been working for several months without problems
I checked the amperage of the fans (ok) still well plugged
so I don't understand why it burned, maybe a short circuit, I don't know
the fan 0 and fan 1 mosfets burned out, I did not check the fan 2
so i will have to change my mosfet...
thank you for the information