Topics created by CCS86

@CCS86 the Maestro IAP (In App Programmer) file, named “Duet2_SDiap32_Maestro.bin”, is the third required file. The IAP files weren’t in the 3.5.1 release initially, but they are now. Not sure if they made it into the release zip though.

Ian

@gloomyandy said in 3.5.0-RC1: Major Issue with Skipped Steps:

@CCS86 Are you running input shaping? If so try disabling it and see if that makes any difference. Also capturing and posting the output from M122 after a failed print might provide some more information.

Yes, I am running IS.

I'm not sure when I will get a chance to test again, as I run pretty steady production on this machine.

@gloomyandy

This is a Maestro board.

I'm not sure when I will get a chance to test again, as I run pretty steady production on this machine.

@CCS86 I think the main focus right now is getting 3.5 out the door.

@dc42 said in Allow Interruption of Heater Command:

@CCS86 I believe this is working in firmware 3.5.0-beta.4. Please test and confirm or not. See https://github.com/Duet3D/RepRapFirmware/issues/763.

Perfect, it is working!

Pause button "completes", which allows it to transform into the cancel button. The heater continues heating after pausing. The heater turns off if you then cancel.

(Sorry for duplicating the report)

@CCS86 I was rather surprised about the "invalid base64 content", that appears to come from a G-code file (HTTP thumbnail response).

@chrishamm said in DWC: Allow File Overwrite During Move:

@CCS86 I've logged this at https://github.com/Duet3D/DuetWebControl/issues/472. It would just require a prompt if the first move attempt fails.

Awesome, thank you!

@dc42 today I learnt!

That makes sense guys.

I was asking more for the visualization aspect with the DWC plugin, as opposed to using it for mesh leveling.

Thanks guys.

I think this is probably the case, because shortly after I was able to upload the same file with no issue. In the process of backing up, I found an unexpected EOF error on a macro, so it seems like the SD was flaky.

Using (the awesome) RFM I was able to pull almost every file off the card (even though windows wouldn't properly mount it), and push them all to a new card. Boom, up and running without missing a beat.

Oddly, despite the DWC working on my local computer, when I try to load it from an external network, I get some errors in the console:

b5b457dd-760d-4f3b-b4d4-e5369b3eceba-image.png

It seems odd, since I don't know why it would be using different files. But, I'll reinstall DWC and see if that fixes it.

Fixed after reinstall

@CCS86 thanks. @chrishamm hope this helps.

@o_lampe I'll bring it up.

@achrn said in Configuring Filament-error.g to play nice with Pause.g:

If you enable the Object Model Browser, you can browse and watch the values in real time, e.g. in this case feed a bit of filament in and out of your sensor by hand while you watch the values on screen (assuming the screen is within sight of the printer).

Very cool! I hadn't tried that yet, thanks.

@OwenD said in Store Height Maps in a Folder:

@CCS86
If you use G29 S3 P"0:/myFolder/myMap.csv" you can save it wherever you want and call it what you want.
You just have to remember to use the same P parameter when you load it
G29 S1 P"0:/myFolder/myMap.csv"

Does the heightmap plugin find them in there?

30e5fea1-ae7b-4639-a512-f58f11be5ae4-image.png

@CCS86 It's been fixed since 3.5-b3, see the DWC changelog on GitHub:

- Fixed tool fan on the Job Status page

Thanks guys. Looking forward to the next version.

@T3P3Tony I am running in standalone mode. Browser is Chrome in Win10 x64.

Let me know if you need any more information or testing.

@dc42 said in 3.5.0-b2: Bed shut off during print:

@CCS86 regarding this:

if heat.heaters[0].current < 60-1 M190 R60 ; Wait for cold bed G4 S240 ; Cold Pause else M190 R60 ; Wait for hot bed <<<<<<< G4 S1 ; Hot Pause

The M190 command with the "Wait for hot bed" comment wil be ignored because it needs to be on a separate line, not on the same line as the 'else'. I will change the parser to generate an error message when there are unexpected characters after 'else'.

Great, thank you for that correction!

@CCS86 2-wire fans are not designed to work with PWM. It's a minor miracle that so many of them do.

@CCS86 one option is to undefine it as a filament sensor and define it as a trigger in your sprint start and end macros. Roughly (untested):
start gcode:

M950 J1 C"nil" ; free up the pin M591 D0 P1 C"nil" M581 T2 P-1

end gcode:

M591 D0 P0 M950 J1 C"e0stop" M581 P1 T2 S0 R0

The other option is keep it as a trigger the whole time (which is probably easier) and have the conditional gcode to check the state (https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation#statestatus)

e.g.

;trigger2.g if state.status = "processing" M98 filament-error.g ;example of some logic to handle the filament out situation else ;the existing logic to handle filament loading.