Posts made by SputnikOC3d

@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.

@chrishamm - where can I learn more about what this is about and how it works ? Im in SBC mode, but my printer is on a private lan in my shop and cannot easily get out to the internet to apt.get ...

@zapta said in Opinions on "FYSETC" ... politely, please.:

@notepad the examples above are of a 6HC. You dispute it using an older WI FI 2.

trying to have a honest discussion of the morality of these clone whores and the users hellbent on saving $35 at the cost of the originating ecosystem is futile. They will justify their savings with 500 differing variants of logic... all while knowing they are screwing the people who brought this whole thing to the forefront. Its sad.

Whats funny tho is listening to how theyve justified the cost savings in their minds with "How theyre actually improving the whole thing" with "competition" and "options" - utterly laughable.

@zbeeble

Why should we be polite when discussing them ? They are very "impolite" putting it mildly.

Their poor behavior as listed above and other nefarious B.S. merits them to earn the honors of the maker community banning and disparaging them - at least as much as the ABS Mafia in the voron community has ex-communicated Slice Engineering for enforcing their legitimately files patents.

FYSETC - low quality junk. Do not recommend.

@oc_geek

Just chiming in to add a +1 for me on this as well. Would be helpful.

@adamfilip

Howdy sir. My apologies - I didnt mean to come off like that, and perhaps my good willed intentions didnt come through in my post. for that I apologize. I know the last thing you need when struggling to get your printer working after hours of config and testing and struggles - is some clown on the interwebz giving you flack.

Didnt mean to be rude ... sorry if it came off that way. Was hoping to prevent you from spending $$$ unnecessarily. Thats all. Thought I saw some print tuning issues from your pics - perhaps I was mistaken.

Good luck with getting this sorted. Hope it gets worked out soon.

@adamfilip from the looks of the lower layers of this print - its slicer setting and print tuning - not the steppers fault. The poorly formed overhangs, the over extrusion in general. Not sure of the material being used or your slicer settings et al ... but the part of the print that didnt fail doesnt look like its coming off a well tuned printer - ready for a 53 hr challenging print task.

Not sure closed loop servos is the right solution ...

@oliof said in Tool Swaps Multiple Hotend PID tunes Trigger Height drama:

Since you manually swap out the tools, maybe using M505 to switch between configurations is an option

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m505-set-configuration-file-folder

TY sir ... however - thats a bit much work methinks for a mere 5 lines of code per hotend. Trying to sort some form of a singular - conditional macro like above sample posted .. but I cant sort what in the dwc interface would give me a suitable trigger event to tell such a macro what tool[0-3] was actually attached.

I have 4 macros now for each toolhead as a workaround Ive created that set

• trigger height for G31
• thermistor type
• M307 PID tune settings
• Max temps
• Tool A"name"

@mac pretty sure you could still use it - just use a browser vs. the Find My Duet "APP" - browser DWC is likely a better interface now too.

@fcwilt Thanks again Frederick ...

Was looking over your code and injecting snippets of it into my cfg.g file as applicable. However; I noticed then that perhaps your setup differs from mine in that you have a multi tool expansion board where all of your toolheads can be live - and communicating via canbus at the same time - and perhaps they even have separate part cooling and hotend fans on the toolheads ?

My setup is a bit different than that, in that I have to manually unwire the Heater and unplug the therm connector on my 1LC toolboard mounted on my 1 singular toolhead. So, having all these tools defined as live [ if you will ] in the cf.g.g seems like it will just throw endless gcode errors - as the fw will be looking for defined "stuff" that isnt connected ?

Also - my hotend heater is H1 .. in your tools section you have a heater defined as H0 - isnt that assignment used by your bed ? or when youre using toolheads like this - bed heater is no longer H0 ? Same issue for the fans assignment in M563 ...

OR ... does rrf not get bothered by that because its being done in M563 vs. M308 M950 gcode lines

... obvi Im kinda confused

@fcwilt - as always sir .. you come thru with the goods! TY very much

This is exactly what I was seeking - clarifies many of the missing pieces I was not understanding - on the "How To".

Im going to start with 2 tools and get that working then add in the other two. I dont have a Jubilee type setup - so mine will be manually swapped in and out when the printer is off.

Safe to assume that this general config you've posted doesnt require all tools / toolheads / boards to be powered up and connected to CAN