@Rat-Rig-CS thanks for your response and for how this had been handled.

From our side part of the issue was between how warranty issues are handled when a product is supplied from a reseller, vs a board supplied with a complete product (be it a kit or an assembled machine):

For a reseller supplied product, referral to the forum is the correct procedure. For a product incorporated in kit or complete machine we expect the manufacturer to handle the warranty process (and communicate with us directly, if there is a fault with the board).

The basic idea being a machine sold as a complete product, which the manufacturer has control over would not be expected to have configuration or wiring issues that we want to debug here on the forum before confirming a hardware fault.

We will update our T&Cs to make this clearer.

@gloomyandy This was my first time updating from the Duet; RC1 was a fresh flash from USB, but yep I'm on Duet3 MB6HC + SBC

@gloomyandy
@droftarts
@Notepad
@dc42

From my perspective, there is no need to switch to CAN0 from CAN1. Since it was not specified in the team gloomy documentaion that only CAN1 will work with the toolboard, I assumed both would do it.

In my case it would have simplified the wiring of the toolboard a bit because my 24V PSU is mounted close to the Duet 6HC. I have four 1HCL expansion boards mounted inside the build chamber. But they are all running on 48V. So I split the toolboard cable in CAN and power. CAN goes to to ne of the toolboards and power goes all the way down to the underside of my printer to the 24V PSU. Not as tidy, but works. 🙂

@KenW and just to add further, GPIO18 and GPIO19 won't be available to use on the latest revision as they will be used by z scanning probe.
I'm currently looking to see if anything else can be made available

@jay_s_uk That would be useful, I could use at least one more for the Orbiter load/unload feature. That was nice, stick the filament in and it loads it. Push the button and it pulls it out. And if both GPIO's were to appear I'd move the X endstop back onto the extruder. Less wires dangling all over the printer frame that way.

I tested the daemon and it works fine,. This way if a fan ever fails again the printer can shut down before damage happens.

@agz90 said in Fly-RRF-36 RP2040 not work second fan:

@gloomyandy
Thanks

Not sure if it will help but here's a RRF-36 Config for one of my tools,

;---------------------Tool 0 aka "AMY" With CAN Address 20.0 ------------------------------------------ ;Heater Thermistor M308 S1 P"20.TEMP0" Y"thermistor" T100000 B4725 C7.06e-8 A"Amy" ;"T1" Semtec Thermistor defined ;M308 S6 P"20.temp1" Y"thermistor" A"Amy Fly RRF" T100000 B4092 ; Onboard temperature sensor ; Cooling Fans M950 F0 C"20.out1" ; Fan 0, part cooler fan on Tool 0 M106 P0 C"Amy" ; Set Fan Name M950 F1 C"20.out2" ; Fan 1, hotend fan on Tool 0 M950 H1 C"20.out0" T1 ; Heater 1 "H1" uses the Out0 pin and Temp0 M570 H1 P15 T20 R5 ; An anomaly on "H1" must persist for 15 seconds, and must be greater or less than 20C from the setpoint, to raise a heater fault. M143 H1 S280 ; Maximum H1 (Extruder 1) heater temperature M106 P1 S1.0 T45 H1 ; Tool 0 Hotend Fan to start cooling at 45C Monitoring Heater 1 (H1) M563 P0 S"Amy" D0 H1 F0 ; Define tool 0 "AMY" using H1 heater, F0 cooling ;G10 P0 X0.188 Y32.637 Z-0.345 ; Set tool 0 offset from the bed FOR INITIAL SETUP ONLY SEE VALUES IN CONFIG OVERRIDE G10 P0 S0 R0 ; Set tool 1 operating (S) and standby temperatures (R) (-273 = "off") M572 D0 S0.04 ; Set pressure advance on Extruder Drive 1 ;Turn on tool Lights M950 E0 C"20.rgbled" T2 U2 ; Strip number, Pin ID, type, Max # of LED'S ;M150 E0 U0 R0 B0 W255 S1 F1 P255 ; for RGBW LED Only ;M150 E0 U0 R0 B0 W255 S1 F0 P255 ; for RGBW LED Only M955 P20.0 I52 ; Enable accelerometer on Amy ;---------------------End of Tool 0 aka "AMY" -----------------------------------------------------------

@Topenga https://teamgloomy.github.io/btt_octopus_pro_1.0_f429_screen.html

@o_lampe you do need the CAN transceivers. They should have low propagation delay because we can't do transmitter delay compensation on the RP2040. And yes, the MCP2542 CAN transceivers that we use on Duets and recommend for the RP2040 are hard to find at present, however the SOIC version is currently available from Microchip Direct.

@reflexlab it depends on your board:

If the board uses plug-in drivers then you can usually unplug the driver and connect an external driver to the step, direction and either 5V or ground pins of the driver socket. If it doesn't use plug-in drivers, and doesn't provide access to the step and direction outputs, then you would need a specialise driver that decodes the phase outputs of on-board driver to extract step and direction information from them. I have never come across such a driver, however in this thread https://forum.duet3d.com/topic/28887/weird-signal-from-duet-to-motor it became apparent that the person posting has such a driver.

The Duet3D MB6HC main board and the EXP3HC and EXP1HCL expansion boards can drive some types of Nema 34 motor directly at up to 6A peak current.

@gojdk said in wires to the stepper motors fell off,:

hi, I ran into a problem, one of the belts broke, so I had to remove the bottom, that's where my problem arose, all the wires to the stepper motors fell off, does anyone know which wires belong to which motor E2, E3 , E4 , E5?

Duet2 Board ?
https://docs.duet3d.com/en/How_to_guides/Wiring_your_Duet_2

@dc42 Hi i have adjusted things as needed when I build i get this it may be because I am just changing one file and not the whole project it could also be I have never done this before here is the error I am getting

17:48:12 **** Incremental Build of configuration Build (GNU) for project duet3v2 ****
make all
make: *** No rule to make target 'all'. Stop.
"make all" terminated with exit code 2. Build might be incomplete.

17:48:12 Build Finished. 0 errors, 0 warnings. (took 117ms)

@hardgeek95 said in Converting davinci JR 1.0 board to reprap:

Hello, I need help to make compatible reprap firmware with stock davinci JR 1.0 board, the board have Atmel ATSAM4E8E also have other microcontroller that control Nfc tag, some filament sensor and ntc and hot end too but I plain cut off that MCU and jumper ntc and hot end direct to main CPU, I already have all pins mapped but I don't have experience with making changes on reprap firmware to make Pinout compatible.

Almost all of the pin configuration data is in file Pins_DuetNG.h. So that's the main file you will need to change.

@flipasaurus please use the 3.4-dev branches of all projects (Duet3Expansion, CANlib, FreeRTOS, CoreN2G and RRFLibraries. The branches listed in the readme file are out of date.

I was able to return the Kinetica G2 board and I am going with a Duet 3 mini instead.

@o_lampe So for the RAM, I currently opted to use any free RAM for network buffers. However, ESP32-S3 supports external PSRAM up to 8MB.

The firmware is about 1.5MB. Phi has a module with 8MB flash.

@oliof Thank you sir......:)

@pcr NC, US.

Look in the alternative boards/ports section of the forums.

There is an STM port there I think.