Topics created by SputnikOC3d

@SputnikOC3d I've updated the M997 Gcode entry with more examples, and made the notes a bit clearer: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

@SputnikOC3d said in 1LC Toolboard FW mismatch - M997 fails to update D3 Mini+SBC pi4:

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

It isn't a two stage process, because you rarely, if ever, need to update the bootloader. So all you needed was M997 B121 to update the firmware. And usually this is done automatically for you.

Ian

@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

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.

@sputnikoc3d that would then be @fcwilt's sample macro calling thoese four macros depending on what you chose. And then you could use the BtnCmd plugin for DWC to make a button to choose for each.

@wdenker from the datasheet, 143C:

https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2209_datasheet_rev1.09.pdf

However that's internal temperature generated from the MOSFETs inside the TMC2209, not chamber temperature. The hotter the chamber, the less motor current can be used before the driver overtemp kicks in.

I think you got your answer in your other thread.

@sputnikoc3d delete all debs and download only the 3.4.0 packages without beta in the filename, then upgrade using dpkg again.

@phaedrux - hard to say if its been 14 or 24 months - i'll have to check my filatruder and other online resellers online accounts order history .. i have a few. Slapped a 1.2v in and it does NOT have the issue.

Ref;ashing its fw right now - fingers crossed

@nightlonk42 - No Caribou / Zaribo bedslinger

@sputnikoc3d adding T0 to config.g should be safe if the G10 for T0 has S0, R0 (i.e. set it to 0 temperature). what did you have in config.g?

@phaedrux - @ctilley79 - got me thru the hiccups of getting all the right services started and in the proper order.

We got the updates and packages down and running and dcs / dwc is live. Toolboard was on 3.4.oBeta3 - so I went all in there again. We'll see how she goes from here .

I have the hostname and machine name matching [ duet3/duet3 ] in pi / and config.g

So far things are working ... I neglected to save my macros and all my local dwc settings were gone too - but Im getting much closer - network drop outs are better atm as well.

Running on the new SD card 64 GB SanDisk Extreme - fastest they sold at Best Buy.

My pi/nix game is ever so slightly improving ...

If the disconnects continue ... will address and be back.

@sputnikoc3d said in Filament Material Changes without Load - Unload ???:

@fcwilt

I'd have a manual button/macro I can hit that will toggle on/off my load / unload scripts when I change a filament via dwc tool drop down option ...

Exactly.

Frederick

@sputnikoc3d said in STUMPED : Slicer sending Garbage Start.g GCode to 1LC toolboard:

@fcwilt - heres a solution for Super Slicer ...

https://github.com/supermerill/SuperSlicer/issues/425#issuecomment-913036749

found the setting [ if it were a snake it have bit me ]

superslicersolution.png

I like that. Every slicer ought to have that option rather than having to figure which other settings will stop the generation of this or that bit of code.

Good work.

Frederick

@dc42 TY sir.

Looks like I had several syntax errors that needed sorting M915 at the end. As well needed to arrange the codes at the starts in better order. Still not sure of all the pauses needed but it is now working. I had some G1 H1 / H2 commands wrong as well that gave bizarre behavior on a corexy x/y axis 🙂 as one might imagine.

So posting up what worked for me w/ spec OMC 2A steppers - voron 2.4 300mm build Duet 3 Mini5+

;==================== ; homeX.g ;==================== ; called to home the X axis M400 ; Wait for current moves to finish M913 X60 Y60 ; drop motor current to 60% M569 P5 D3 V10 ; X -> B axis reduce V parameter so driver operates in stealthChop M569 P6 D3 V10 ; Y -> A axis reduce V parameter so driver operates in stealthChop ;G4 P200 ; Pause for 200ms to let StealthChop do some sh!t M17 X Y ; Energize Motors X Y G4 P200 ; Pause for 200ms to let StealthChop do some sh!t M915 X S-2 R0 F0 H200 ; Sensitivity -3 [-64 --> 64], R - take no action, F - No filter, 400steps/sec G4 P200 ; wait 200ms G91 ; set relative G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 X10 F6000 ; Move X away from possible end point - relative to current position G4 P200 ; wait 200ms G1 H1 X-350 F5000 ; [ First Pass ] move quickly to X axis endstop and stop there G90 ; absolute positioning M400 ; Wait for current moves to finish M913 X100 Y100 ; return current to 100% M569 P5 D2 ; Take driver out of StealthChop Mode M569 P6 D2 ; Take driver out of StealthChop Mode M915 X Y R0 ; Disable Logging and lower stall detection G1 H1 X150 F12000 ; Move X away from possible end point - relative to current position ;==================== ; homeY.g ;==================== ; called to home the Y axis M400 ; Wait for current moves to finish M913 X60 Y60 ; drop motor current to 60% M569 P5 D3 V10 ; X -> B axis reduce V parameter so driver operates in stealthChop M569 P6 D3 V10 ; Y -> A axis reduce V parameter so driver operates in stealthChop ;G4 P200 ; Pause for 200ms to let StealthChop do some sh!t M17 X Y ; Energize Motors X Y G4 P200 ; Pause for 200ms to let StealthChop do some sh!t M915 X Y S1 R0 F0 H200 ; Sensitivity -3 [-64 --> 64], R - take no action, F - No filter, 400steps/sec G4 P200 ; wait 200ms G91 ; set relative G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 Y10 F6000 ; Move Y away from possible end point - relative to current position G4 P200 ; wait 200ms G1 H1 Y-350 F4000 ; [ First Pass ] move quickly to Y axis endstop and stop there G1 H2 Z-10 F6000 ; lower Z again G90 ; absolute positioning M400 ; Wait for current moves to finish M913 X100 Y100 ; return current to 100% M569 P5 D2 V2000 ; Take driver out of StealthChop Mode M569 P6 D2 V2000 ; Take driver out of StealthChop Mode M915 X Y R0 ; Disable Logging and lower stall detection

Thanks to all for their help - especially ctilley ... gracias C3

@jay_s_uk said in RRF3.2beta4 / DWC 3.2.0-beta4 - heatbed now missing ...:

M140 H0

That did it ... Thank You ! Much appreciated

Now I shall go look to see why that was needed where it wasnt before ...

Thanks @dc42 and @chrishamm

We now have a functioning homing system

Appreciate you help

and...@SputnikOC3d - thank you too dude!!!

Cheers

Ray

@dc42 said in Pause / Resume from DWC buttons - nasty head crash - but WHY?:

@sputnikoc3d said in Pause / Resume from DWC buttons - nasty head crash - but WHY?:

2.02RC5

You should not use beta or RC firmware versions once the corresponding stable release is available (2.02 in this case). As @resam said, there was a known bug in this area in some 2.02RC versions.

Thanks David ...

Lesson learned then. I wondered if I had changed something somewhere that may have caused it ... I had not had the printer up and working for over a month - and needed to get a friends parts printed ... asap. Didnt think to see if there was a new version before rockin and rollin. Lesson #2 learned 🙂

Im up on all the latest stable full releases now.

thanks to all for the assist.

@sputnikoc3d said in Tutorial - running Duet Wifi 2 in Access Point Mode ?:

Pronterface ok here for this YAT is just not my cup of tea - at all.

Bear in mind that Pronterface forces all the characters you send to upper case, which is awkward for entering passwords in particular. That's why we suggest YAT for this purpose.