@gloomyandy posted

[[ Both the 5160 and 2209 were a pain to tune with the 0.9 steppers. I started out with 2209s and managed to get them working pretty well. ]]

But this is in Stealthchop mode ONLY 100% of the time ... utilizing print speeds < 100 mm/s and non print travel moves < 200 mm/s right ? Probably fine for MOST cartesians but not the OPS - travel moves over 200 mm/s are doable as are much faster print moves.

Operating in stealthchop for several of us is just not a solution - especially on a Voron 2.4 - purpose built to far exceed Stealthchop limitations.

The issue we're fighting isnt Homing sensitivity and the PITA that that is- we've gotten past that - we're now missing steps during print moves < 100 mm/s in Spreadcycle. Thats a very serious issue for a 3d print and the FW - somewhere. This post is far beyond mere inconvenience, its now to the point of the Duet 3 Mini 5+ viability as a useable board.

@chrishamm - bro ... HUGE info. Appreciated.

On a mission

p.s. - as if you couldnt tell by my post - my linux skills are trash, but learning

@t3p3tony - any potential ideas to help get this resolved. If not - pretty sure I'll just send my Mini 5+ back in for a refund to Filastruder.

Someone needs to put some type of effort also into getting Trinamic engaged to help sort these issues its across the spectrum with several other boards - at least with those one can swap out drivers.

Never thought Id be sending back a Duet in order to get a china board ... for different drivers.

@gloomyandy ... Yes - we do have some test cases setup.

I have 2 Duet2 wifi's running various LDO .9* and 1.8* steppers
I have a voron 2.4 build in the works that will possibly be fitted with a Mini 5_ Duet 3 w/ Pi4

We also have a test Caribou 320 with Mini 5+ - w/ LDO .9* steppers on X / Y / E [ OP's machine ]

Another Bear with linear rails w/ Mini 5+ - w/ LIN .9* steppers on X Y E - working ins spreadcycle but skipping steps and klunking on higher than 180 mm/s moves

Then a Voron 2.4 w/ full sized main board duet and .9* OMC Stepper online on all axis

Then another Voron 2.4 with SKR and 2209's and 1.8* LDO Motors

So lots of things being compared ... This with this exhibits that or none of this etc ..

Thru the process of elimination its seems to be either LDO .9* motors or RRF3 FW.

@droftarts said in Missing Steps - Cant Print SpreadCycle StealthChop tuning help:

@SputnikOC3d please don’t quote a whole long post that you’re not actually referring to, it makes the thread very long and harder to navigate.

Ian

You got it champ ... I'll work on better forum reply posting etiquette ...

Patience of a saint on display here ... I think its high time to seriously consider a new board with a different driver type. Since Duet 2 would be going backwards - revision' ly ... the 6HC seems a proper choice for the customer - having dealt with So Much effort to make this work. Personally, thats where Id be at this point.

@fcwilt - awesome.

Ok so it is manageable. This further info posted from your start print macro is helpful. The conditional code - solves several concerns - wasnt thinking of that flexibility being availed in rrf3.x but its there now.

Yes T0 and M703 are the 1st two lines in my start macro, but Im sure it was my lack of passing temps for nozz and bed thru variables to the slicer somehow that cause it to emit junk gcode.

I did find a hack for the superslicer G10/M116 issue - and that is - it and prusa slicer will not emit "safeguard" gcode into the mix if you stuff a M104 / M190 at the front of your custom start.g in the slicer.

I switched over to M568 ... and neither slicer jived with that; hence it stuffed a G10 P0 S215 and a M116 - to safeguard me from myself.

2 am now ... lots to ponder and fix. off to bed for a short bit then back at it fresh in the a.m.

thanks again for all your help.

Voron 2.4
Duet 3 Mini 5+
1LC toolboard v.1.1
RRF 3.4.0-Beta4

;===================================
; Nozzle Heater
;===================================
M308 S1 P"121.temp0" Y"thermistor" T100000 B4138        ; configure sensor 1 as Nozz Heater Therm on pin 121.temp0
M950 H1 C"121.out0" T1                                   ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 B0 S1.00                                         ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S285                                             ; set temperature limit for heater 1 to 285C

Previously well functioning machine. Had the magnet on the BL Touch drop the pin mid print in hot enclosure and caused havoc. I thought I smelled blue smoke but thought it might have been the hotend nozz dragging across the top of the prints infill. Was printing PC-CF at 270c when it all went south a few months ago. Just now getting things back to working.

Havent been to get to print or PID since the above failure ... now on all starts the HotEnd runs away to thermal max and beyond ... 400c the first time before i realized it was happening. Max temp is set at 285C

Ive ohm'd the installed heater at 14.3 [ 24v system and 40 heater cartridge AFAIK ]

Ive swapped out another heater cart too and it also goes straight to max temps and no control allowed at reboots.

Ive been running the machine for setup and fw/config.g tweaking without the Heater wires connected to the 1LC 121.out0.

Suspecting maybe blown mosfet on the 1LC now. Perhaps thats what caused all the issues with the BL Touch as well ??? [ noted some fw update notes that the 1LC's io0 pins are not acceptable for servo pins ? ]

How can I troubleshoot from here ?

@bearer said in PanelDueFirmware 3.2.4 released:

@SputnikOC3d said in PanelDueFirmware 3.2.4 released:

but it cant seem to connect to the duet on rrf 3.2-beta4

if you upgraded from before 3.1 check out the release notes https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310

Found another thread / post where you identified the issue :

Ive got no M575 P1 S1 B57600

Think thats the issue ?

TY ...

@jackatom74

Im using Matterhackers [ they are just down the street from me ] 1.75 Aqua PetG Pro

@droftarts - PS - can mark this SOLVED too

Answer was to use syntax M997 B121 [ where 121 represents your expansion boards CAN ID ]

@droftarts - thank you.

For whatever reason the needed file was missing ... [ Duet3Bootloader-SAMC21.bin ]

After I found the missing file and uploaded it via DWC, and tried to update the firmware using various variants of the M997 command.

Its confusing [ to me anyways ] because .. you update the main board by the "S" parameter and several other things with it [ per the docs ] - seemed logical that M997 S3 was going to try and update the FW ... not JUST the bootloader and that unlike the main board the CAN bus attached toolheads etc do not require the "S" parameter to be used to update the firmware.

Hopefully Im making sense at describing what doesnt make sense in the docs. Also curious why that particular file was absent on a new fresh SD card flash.

@droftarts - wow !!! That did it ... Thank you.

I must be super daft ... cuz I really never saw this as a 2 step process in the docs.

1. Update the bootloader with M997 S3 B121
2. Update the firmware with just M997 B121

Seems this stage is fixed

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.3 (2024-09-17 14:35:31)
Bootloader ID: SAMC21 bootloader version 2.11 (2024-08-09)
All averaging filters OK

The above clarifications and facts should be entered into the docs for future for others ?

Link to the docs

Ive recently flashed a new SD card image for the SBC t oDuet FW 3.5.3

Main board - duet mini 5+ - updated to 3.5.3 via M997
DWC - showed up as 3.5.3 after 1st boot after new flashed SD
DSF - showed up as 3.5.3 after 1st boot after new flashed SD

Duet 3 expansion toolboard 1LC- was stuck at 3.4.0 beta - for the obvious reasons

tried M997 S3 B121 - first error was the SAM2C.bin file not present. Went to bootloader latest releases and DL'd to pc then uploaded to the FW Director via DWC [ Duet3Bootloader-SAMC21.bin ] dwc shows date of 9/19/2024. it is 11/10/24 today

Not sure what to do from here - where to find the right file[s] to get the toolhead 1LC up to date ...

@droftarts - this issue is resolved - and now im into a new issue.

Ive abandoned the filezilla bu and just used the filed from the DWC backups.

Closing ... moved on

@droftarts thank you ...

New twist

Now ive got mismatched FW on the main board [ just fixed ] and the iLC toolhead. tried a M997 S3 B121 [ as the DWC tells my my toolhead is 121 ] - error Error: M997: Firmware file Duet3Bootloader-SAMC21.bin not found

Ive used the dwc prior to flashing new sd card - to zip up and save all my config / sys / macros files and stored local ... need to try and get this toolhead updated properly.

Wil say - it'd be nice to have real world use examples in the docs / GCode Dictionary ...

[[ 3 - update the bootloader on the CAN-connected Duet 3 expansion board specified by the B parameter. In older Duet 2 firmware versions, was used to put the WiFi module into bootloader mode, so that firmware can be uploaded directly via its serial port. ]]

[[ On Duet 3 only this command take an optional B (board number) parameter which is the CAN address of the board to be updated, default 0 (i.e. main board). ]]

then .. get the BT wireless kb mouse on the voron to reconnect - VNC enabled ... fortunately DWC is rocking

Trying to backup my existing 3.4.0 + SBC debian pi install - config and macro's - using the SBC Bookworm guide in the linked docs.

However; I cannot get Filezilla to authenticate / login to my pi.

Status: Connecting to 192.168.1.xx...
Status: Using username "pi".
Status: Access denied
Error: Authentication failed.
Error: Critical error: Could not connect to server

SSH is enabled. changed passwd - several times to : raspberry

Have access to the pi via vnc and i have a kb / mouse and monitor connected to the pi

Closing this thread as Ive determined with guidance from those in the know, my path forward needs to be not merely just an update and upgrade to RRF, but to the debian install as well. Bookworm on SD Card fresh.

Context:

Voron 2.4 - Duet 3 mini - Raspi 3 - SBC Mode
Current Firmware 3.4.0
bluetooth KB / Mouse and HDMI monitor connected to the SBC/Pi

Workshop environment has internet / wifi via cox.net free open wifi which operates fine in our neighborhood, as I cannot reach my house wifi from the garage shop. I can access the cox.net free wifi from my PC on the shop LAN, but the pi cannot connect to it because it has a browser based first use login requirement to get on. Kind of like using starbucks wifi. This cannot be performed from the command line.

I have a 5G iphone and can use it as a hotspot - but cannot get the pi / sbc to connect to it, regardless of the many attempts ive made with entries for it in the wpa_supplicant.conf file [ wlan0 - not associated ]

Pi / SBC will connect just fine to the wifi lan [ Linksys router ] in the shop via wpa_supplicant.conf configurations, but I cannot get the lan as a whole out onto the internet [ Starbucks style free wifi 1st use browser login required ] not sure how to overcome that with a router interface.

My main goal is to try and update / upgrade my firmware, thus requiring the machine to be connected to the internet. I think my shortest path to glory is to get the Pi/SBC onto the interwbz via the iPhone hotspot.

Or .. is there a non internet based method / option to upgrade all with file downloads. I can get to the SBC via VNC from the web connected PC on the lan.

I know just enough about linux / raspi to cause issue, and my networking skills peaked ages ago - so im super rusty on basic ip / lan stuff too - sorry.

@chrishamm said in cant connect to https://pkg.duet3d.com for update:

@SputnikOC3d It's just a stub at this point. First of all, you need to enable root plugin support in /opt/dsf/conf/config.json by changing RootPluginSupport from false to true. Then restart the SBC or just DCS by running sudo systemctl restart duetcontrolserver from a Linux terminal. Once done, you need to download the latest .deb packages from the stable/unstable package feeds (see the command line here for a list of the packages you need), compress them as dsf-update.zip, and upload it on the Files -> System page. After 2mins or so, DWC should report that the installation was successful. I don't think this way of updating is supported before v3.4, though.

Awesome - thank you ... running 3.4+ iirc - Need to fire up the beast and see where shes at ... Thanks again.