@jay_s_uk Sure. I have messaged you in Discord. Pls check

; Configuration file for Fly Super8 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.4.0-LPC-STM32+2 on Sat May 28 2022 18:17:40 GMT+0200 (hora de verano de Europa central) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"EXODO" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet M302 P1 ; Drives M569 P0 S0 ; physical drive 0 goes forwards using default driver timings M569 P1 S0 ; physical drive 1 goes forwards using default driver timings M569 P2 S0 ; physical drive 2 goes forwards using default driver timings M569 P3 S0 ; physical drive 3 goes backwards using default driver timings M569 P4 S0 ; physical drive 4 goes backwards using default driver timings M584 X0 Y1 Z2 E3:4 ; set drive mapping M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation M92 X400.00 Y400.00 Z533.33 E40.00:40.00 ; set steps per mm M566 X400 Y400 Z120 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X3000 Y3000 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min) M201 X300 Y300 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X180 Y200 Z200 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!io0" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0 M574 Y1 S1 P"!io1" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1 M574 Z1 S1 P"io2" M574 U2 S0 P"!io3" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io2 ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M140 H-1 ; disable heated bed (overrides default heater mapping) M308 S0 P"ADC_0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin ADC_0 M950 H0 C"heat0" T0 ; create nozzle heater output on heat0 and map it to sensor 0 M307 H0 B0 S1.00 I1 ; disable bang-bang mode for heater and set PWM limit M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"ADC_1" Y"thermistor" T10000 B3988 ; configure sensor 1 as thermistor on pin ADC_1 M950 H1 C"heat1" T1 ; create nozzle heater output on heat1 and map it to sensor 1 M307 H1 B0 S1.00 I1 ; disable bang-bang mode for heater and set PWM limit M143 H1 S120 ; set temperature limit for heater 1 to 120C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 S"A" D0 H0 F-1 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"B" D1 H1 F-1 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R18 S18 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined

I don't see anything noteworthy in there other than the tool1 definition sets the active and standby temps to 18 for some reason.

@o_lampe See the stepper.num5160Drivers board.txt entry, you basically tell the firmware how many of the smart drivers are 5160 based. You will also need to configure the stepper.spiChannel entry to tell the firmware which spi channel to use to talk to them. You will also need to set the jumpers on the board appropriately. The 5160 drivers must be the lowest numbered drivers, so if you have 3 5160s they must be in slots 0, 1, 2. Sorry I don't have access to my super8 configuration at the moment so I can't supply the specifics.

Well, I've solved this, by noticing that the fault occurs only after the 'idle hold' timeout. I can print any number of files as long as I follow the previous quickly enough, but if the M84 timeout occurs then the next time I attempt to move axis X I get a short to Vin. (This was pernicious, because when I was testing I'd print one after another and all would go ok, then I'd come back later to do something and it would fail!)

I did have a very very low idle current factor - M906 X1000 Y1000 I5 i.e. 5% of full. That's because my mechanism can't droop (it's X and Y only) so I didn't think I needed much hold current. If I increase the idle factor to a more normal value (I've actually set to 35%) then it can timeout fine and I can still print the next file.

I have no idea why this behaviour started (I've had 5% for months and months), but setting idle current factor to a higher value seems to have stopped shorts being reported, and fortunately the only components I'd got round to replacing so far were cables ie not very costly).

@jay_s_uk OK, thanks. I'll try redoing the cables if it happens again.

thanks for your efforts

@alankilian said in Don't mount F407 vertically...:

At 24 Volts, 300 Watts is 12 Amps which is on the edge according to @jay_s_uk

My cheap multimeter read 2.6Ohm, which would lead to less than 10Amps @220W. (probably not very accurate reading)

@jay_s_uk
IMHO a bed-Mosfet should be oversized to run 24/7 reliably.
The replacement you kindly offered will have the same problem, unless I can upgrade the FET. (will try it on my board first, you don't have to send anything yet).
If it fails, an external MOSFet would work from an extruder heater, too.

@jay_s_uk Thanks Jay, I missed that info on the github pages...

@jay_s_uk I've upgraded the board to 3.3.0_5 and the SBC to the latest 3.3.0 stable release but unfortunately with no effect. It still stops randomly sometimes.

I've tried to cancel the print after it stopped and got this:

M0 H1 Error: M0: Pause the print before attempting to cancel it

which seems odd as the print should be paused, or is it maybe because it is getting stuck in the script somewhere?

Driver 1 and and 4 are not in use btw. I have a weird arrangement due to one driver slot being fried.

This is the output of M122 P200:
M122 P200.txt

@jay_s_uk my board duet 2 wifi

@jay_s_uk said in Can I use an SKR Pro with external drivers:

@markz I use an SKR Pro with external drivers on my CNC machine.
So the answers are

Yes. I made my own little adapter boards to break out the pins but you can also buy these Yes. you just need to set the appropriate timings Duet 2 supports external drivers using an external breakout board or you can get a duet 3 with a 1XD board to connect an external driver, although one would be required per driver

Sorry for reviving a several month old thread but this is exactly what I'm looking for.

@jay_s_uk is there any chance you have any details available on the adapters you made? I'm not able to find any of the premade ones anywhere that won't take ages to ship and I'm trying to get this project up and running as quickly as I can. My SKR 1.4 turbo arrives today and I have the high voltage stepper controller already, just need to be able to connect them.

Thank you for any help you can offer!

Thanks @rodsmith I have flashed my screen with the firmware by ThRo42 & it's waaay better than the one I had, I just wish that there was a more recent version (26.2)
Have you came across any?

@sankafola I'm interested too because I have a 12VDC power supply and to be able to use the resume after power outage I thought to buy this:

https://www.aliexpress.com/item/32967985788.html?spm=a2g0o.productlist.0.0.2d9255cbWfDPoe&algo_pvid=cdd5d04b-1af9-4065-9037-be32ec8befcc&algo_expid=cdd5d04b-1af9-4065-9037-be32ec8befcc-8&btsid=0b0a555b16040680685654891ea7fc&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

So it would be possible to connect the otuput port of this "UPS" to a free pin of the DUET 2 Wifi and trigger a pause?

@bot
Yeah, that was my conclusion as well since i don't bring the Tx to temp before switching.
So far the result is promising, but i will change my setting in the slicer to bring up the temp before tool switch.

Has any wiring for the PanelDue or reset button been moved near motor wiring during your rebuild?

Is the power supply malfunctioning?

debug logs would go out over USB
https://duet3d.dozuki.com/Wiki/Gcode#Section_M111_Set_Debug_Level

Oh and if you have further LPC specific questions you may get an answer more quickly using the discord server (see the LPC wiki for details).

thank you guys ... I'm going to update ... and i run 4 tmc2209 drivers ..can be the cable from motors?