@dc42 Thanks! Which resistor should I remove as the "termination resistor?"

@genioluiz7 did you try using M997 S1 to reinstall the WiFi firmware?

@lazy_mosquito You don't have the bed temperature sensor (S1) associated with the bed heater (H0). There's no M950 for the extruder heater (ie H1). You have assigned sensor 0 (S0) to both the bed, with M140 P0 H0, and the tool (extruder), with M563 P0 ... H0. That's why they both have the same temperature. It is plotting sensor 1 named "bed" on the graph, but it is not associated with the bed or the tool heater.

What output is the extruder heater (H1) connected to? You need an M950 line for this, and associate it with sensor 0.

I would rename the sensors like this:

; Sensors M308 S0 P"temp2" Y"thermistor" A"bed" T100000 B4138 ; configure sensor #1 M308 S1 P"spi.cs1" Y"rtd-max31865"

Then correct the associations so that S0 is for H0 (bed) and S1 is for the extruder heater (H1).

Ian

@jay_s_uk thanks. i forwarded it to him.

@dc42 thats nice and simple and easy. I like it!

@dc42 thanks for replying!
I really wasn't thinking about fixing the board, there's no one in my area who can do that.
I've already ordered a new board to replace the one I burned. Since it's a very basic printer, I believe the RRF 3.5 will be perfect for me.
For the other printers, I have the Duet 2 WiFi and "Fysect Big Dipper" boards, and with these I'll be able to keep up with the new versions of the RRF.
I'm going to keep the Maestro that I burned as a souvenir so I don't do this kind of stupid thing again, lol.
Thanks!

@ChunkyPanda it might be possible to modify the version 1.01a boards to provide the new functionality. If you look at the version 1.01a schematic at https://github.com/Duet3D/Duet3-Expansion-1HCL/blob/main/v1.0a/Duet3_Exp_1HCL_Schematic_v1.0a.pdf you will see a diode D10 connected between V_FUSE and C32/L2. The relevant change we made at version 2 was to add a second diode between VB_FUSED and the same C32/L2/D10 junction. This allows V_BRAKE to power the 12V regulator but not the stepper driver. The diode we use is a Schottky diode rated at 60V or greater reverse voltage and 1A or greater forward current.

@Notepad

That worked, thanks for your help!

@woody
Without seeing a wiring diagram of what you plan its hard for me to say if it will work.

But powering an expansion board like a 3HC with a different PSU is A-OK. One test machine I have has 3 different PSUs (one at 25V one at 30V and one at 42V)
If the expansion board is CAN controlled, then its important to know that power isn't transferred via CAN so you can power each expansion board with its own unique power if you so wanted.

@droftarts said in Problem in endstop triggering:

Are you sure both 1XDs are running the same version of the firmware as the 6XD?

Checked the firmware version on main board and expansion board, both are running at 3.4.4

@jay_s_uk said in Problem in endstop triggering:

looks like you have them wired as normally open and they're picking up interference. Wire the normally closed instead

I have tried with the normally closed connection. But when triggered it goes to the floating state even triggered all the time.

All the motors are in ON state in the case 1;(Without connecting the expansion board). During which no floating state occur, so I think its not a interference problem.

Here is my Diagnostics report

edit: I have changed my CAN address of both board as 40 and 41

code_text

M122 === Diagnostics === RepRapFirmware for Duet 3 MB6XD version 3.4.4 (2022-10-20 16:19:15) running on Duet 3 MB6XD v1.0 or later (standalone mode) Board ID: 0JD2M-999AL-D25S4-7JKD8-3SJ6Q-K41H3 Used output buffers: 1 of 40 (14 max) === RTOS === Static ram: 151264 Dynamic ram: 95092 of which 0 recycled Never used RAM 104244, free system stack 190 words Tasks: NETWORK(ready,38.1%,251) ETHERNET(notifyWait,0.1%,451) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,266) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,340) MAIN(running,60.9%,951) IDLE(ready,0.9%,29), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:14:46 ago, cause: power up Last software reset at 2024-11-17 10:37, reason: User, GCodes spinning, available RAM 104244, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 669 MCU temperature: min 36.3, current 44.8, max 45.0 Supply voltage: min 0.1, current 23.4, max 23.6, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.0, current 12.2, max 12.2, 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: ok Driver 1: ok Driver 2: ok Driver 3: ok Driver 4: ok Driver 5: ok Date/time: 2024-11-17 11:40:46 Slowest loop: 999.85ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.3ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 3, maxWait 123085ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 8, completed 8, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 8], 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 -1 -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 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 Code queue is empty === CAN === Messages queued 4449, received 12831, lost 0, boc 0 Longest wait 1ms for reply type 6024, peak Tx sync delay 2662, free buffers 50 (min 49), ts 4435/4008/0 Tx timeouts 0,0,426,6,0,0 last cancelled message type 30 dest 127 === Network === Slowest loop: 4.01ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 = Ethernet = State: active Error counts: 0 0 0 0 0 0 Socket states: 2 2 2 2 2 0 0 0 === Multicast handler === Responder is inactive, messages received 0, responses 0 ok M122 B41 Diagnostics for board 41: Duet EXP1XD firmware version 3.4.4 (2022-10-14 11:45:39) Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 5556, free system stack 88 words Tasks: Move(notifyWait<null>,0.0%,153) HEAT(notifyWait<null>,0.1%,115) CanAsync(notifyWait<null>,0.0%,64) CanRecv(notifyWait<null>,0.0%,77) CanClock(notifyWait<null>,0.0%,64) MAIN(running<null>,96.5%,441) IDLE(ready<null>,0.0%,40) AIN(delaying<null>,3.4%,142), total 100.0% Last reset 00:01:38 ago, cause: power up Last software reset data not available Driver 0: pos 0, 9.0 steps/mm, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 2/6, peak Rx sync delay 192, resyncs 0/0, no step interrupt scheduled VIN voltage: min 23.5, current 23.9, max 24.1 MCU temperature: min 32.0C, current 33.6C, max 33.6C Last sensors broadcast 0x00000000 found 0 199 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 810, send timeouts 0, received 505, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 ok M122 B40 Diagnostics for board 40: Duet EXP1XD firmware version 3.4.4 (2022-10-14 11:45:39) Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 5556, free system stack 88 words Tasks: Move(notifyWait<null>,0.0%,153) HEAT(notifyWait<null>,0.1%,115) CanAsync(notifyWait<null>,0.0%,64) CanRecv(notifyWait<null>,0.0%,77) CanClock(notifyWait<null>,0.0%,64) MAIN(running<null>,96.5%,443) IDLE(ready<null>,0.0%,40) AIN(delaying<null>,3.4%,142), total 100.0% Last reset 00:01:44 ago, cause: power up Last software reset data not available Driver 0: pos 0, 90.0 steps/mm, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 1/5, peak Rx sync delay 201, resyncs 0/0, no step interrupt scheduled VIN voltage: min 23.8, current 23.8, max 23.8 MCU temperature: min 32.9C, current 34.3C, max 34.4C Last sensors broadcast 0x00000000 found 0 217 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 206, send timeouts 0, received 122, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 ok

@droftarts said in Motor current idle factor not working over canbus?:

Sorry, senior moment,

LOL, no worries, I know the feeling!

Could you test without stallguard and with the drivers in spreadCycle?

Just tried it, unfortunately no luck, problem still persists.

Otherwise I'll try and test early next week

Thank you! And please do let me know if there is anything I can do on my end to help with the debugging.

@Redheadrambo You could add a temperature daughterboard, which would give two additional temperature inputs (or four if you added two temperature daughterboards), see https://docs.duet3d.com/Duet3D_hardware/Accessories/PT100_Temperature_Daughterboard or https://docs.duet3d.com/Duet3D_hardware/Accessories/Thermocouple_Daughterboard
However, these are only available with connections for thermocouples or PT100 sensors, not thermistors or PT1000.

Ian

Hi guys, did you ever resolve this? I'm going through a similar issue. Thinking of running 24V to my 6HC and 48V to the expansion board (3HC). Will this work? New topic posted here:

https://forum.duet3d.com/topic/36953/duet6hc-24v-and-48v-psu-s-for-different-components/8?_=1731730867239

Thanks 🙂

@droftarts Thank you very much.

I will not attempt to write to the register and risk damaging the board. I try to see if I can find other solutions.

@daninet You are unlikely to have anything connected to CONN_LCD (unless you're running a 12864 display), so it won't be a problem using that, it's outputs for drivers are the same as the expansion header. The BTT board will just save you a bit of wiring.

Ian

@Adamfilip just realized i can add the jumper so the fan gets 24v

@droftarts and @jay_s_uk
Thanks for the answers!
The sum of the 2 suggestions solved my problem.
I think the translation of the documentation into Portuguese by Google made me misspell the D parameter of the M563 command.
I had really forgotten to activate T0.
I used RRF for a few years, since v2.03 and migrated in 2022 to klipper on all machines. Now I'm going back to RRF and I'm trying to remember everything.
Thanks to both of you!