@o_lampe thanks

Yeah, the whole idea came from wanting a big STOP button, then thought about having a physical panel with all of the different typical jog maneuvers, homing, tramming, and I started to worry I may not have enough pins for every function I wanted a button for. So I figured this was a really common use case of mine it would be a good one to start with to reduce the number of pins used.

@mikeabuilder it's probably better to check if it is > 0 (or eventually not = "null")
then, a single reading should be enough

Thanks @chrishamm. Reading your response made me realize that I not only mistyped "SBC" but also that I was backwards about it. My system is NOT running in SBC mode, it's stand-alone. So thanks for answering that version of the question.

I'm restating your "never supported NPT" comment to see if I understand the implications for a machine running in stand-alone mode:

The stand-along RRF will not "know" the time until a client connects. This means all log entries will have a timestamp based on the machine's uptime (time since boot).

If/When a client connects, if that client is DWC, then DWC will set RRF's date-time.

If a client other than DWC connects, and it connects using rr_connect with the time option, then RRF will update with the time from the client.

This explains a lot of unexplained macro errors I've observed over the past three years. And I can see now that I'll need to rewrite all the macros to not use state.time for measuring duration. I'll convert them all over to using state.upTime rather than state.time.

I think I'll also look into making an Rpi pico that powers up with my system and that does the rr_conenct function.

@p8blr said in Duet not consistently running code:

@dc42 Interesting. Any idea on an estimated completion date on the feature request? Or maybe a workaround I could do instead?

See https://github.com/Duet3D/RepRapFirmware/issues/959

Scheduled for “after 3.6.0”.

Ian

benagricola created this issue in Duet3D/RepRapFirmware closed [FeatureRequest]: Allow `M291` to set `result` to `-1` when blocking modal "Cancel" clicked. #959

@Notepad @droftarts ,

My goal is to test a shitload of probes, and see how much it starts to deviate after thousands. Your script might actually work, let me test

@droftarts said in Possible object model error:

I'm sorry, but you'll have to ask @chrishamm why it works! I think it changes the data type to a string.

ok 😂

@Proschi3D yeah I understand. Best way would be to break up the parts and call them as separate macros guarded by conditionals, but if you do that, you can use the built-in tool prep macros.

@Valveman said in G-code file rotation:

@Valveman M556 any significance?

No, that compensates for when you can't build your machine square! G68 is what you need to use, but it will depend how the file is set up as to whether it's easy to predict where it will actually do the engraving. It's best to start with the work square, and add the rotation after.

By the way, how can I post the code for you all to examine?

Add .txt to the end of the gcode file's name, then upload it here, so long as it's under a couple of MB.

Ian

@chrishamm I have a syslog that has the same gcode run twice in a row, once with no errors and then once with the errors. Hopefully the syslog is the "journal" that you were referring to. Either way, it's good to know that the error still occurs with the debug logging enabled.

@dc42 I suspect it was just running out of memory, but I haven't tried this particular construct again with more free memory. I'll try it tomorrow.

@RockB Probably something like

; values are machine position from camera calibration var t1X = 0 var t1Y = 0 G1 X{var.t1X} Y{var.t1Y} F1000; Move to camera calib position G1 X{var.t1X-7.95} Y{var.t1Y-47.9} F1000; move to secondary position

@chrishamm Ah ok thanks, Yeah I did not understand the lingo before. thanks anyway. I will see if I can work around this limitation then somehow.

@cichaczech

The list of object model values is at

https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation

The list of meta commands is at

https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

@dc42 Standalone

@oliof acceleration is always specified in mm/sec^2. The problem arises because RRF allocated and published the M203 command (in the RepRap wiki), then Marlin added support for M203 and chose mm/sec as the unit. In fact there is no reason for slicers to generate M203 commands, but unfortunately they do.

@dc42 @jay_s_uk

Dear All,

I have prepared a G-code reversing tool Console App just to use to reverse motion of the print to be able to test best position to rewind Using C#. Please feel free to use the source if you find it useful. for sometimes it will help us to work manually. But I still required the tool DWC plugin or SBC function.

https://github.com/tunerji/G-Rewind

While reversing code, the code blocks sharing Feed rates and Z height had to be critically analyzed. That's why it was a bit important to review the code a few times.

However, it is temporary solution to me and we still need to make interface buttons and functions to run drive back and forward. The method might need to different way of capturing feed-rate and Z values in real time, once reversed, it use that one.

I assume if we tag all line having G0 and G1 commands as F and Z height of each X and Y coordinates, it might be easy to produce reversing go code in real time at the client side.

However like my case, if paused, machine might lift head and we might need to disable macros like pause and resume too.

as you may notice, in the g-code, Feed rate and Z coordinate has to be shifted and placed on right place, by respecting their groups like G0 and G1 and F Values. My reversing app does that if you like to inspired from there.

Example G-Code Snippet

G1 F1500 X0.00 Y-550 Z1.25 ; Move to coordinates with feed rate of 1500 G0 F4000 X0.00 Y0.00 ; Rapid move to new coordinates G1 F1200 X476.314 Y275 ; Controlled move to new coordinates G1 X0.00 Y0.00 ; Move back to start point

Reversed G-Code Example
After processing with G-Rewind, the G-code might look like this:

G1 X0.00 Y0.00 Z1.25 ; Move back to start point G0 F4000 X0.00 Y0.00 ; Rapid move to previous coordinates G1 F1500 X476.314 Y275 ; Controlled move to previous position G1 X0.00 Y-550 ; Reverse move to the starting coordinates

By the way, we have one more financial support candidate a friend of mine, who is wiling to donate 500 too. Therefore, we have total 1000 budget for now. We might rise more who is required to use it like my case. If you may accept, besides my method or code generation support, I can handover you my portion donation. Please feel free to reach me in private talk about it.

@Phaedrux Also, thanks for responding!

@OwenD Yes! I didnt noticed the typo either. Ok, will add this and try it further but question remains regarding why is this happening, it started after falshing the new raspi image and version 3.5.2. Can you confirm there should not be a problem using the 64 bit version on my raspi? because there are other problem like for example DWC not starting on my touch screen, there is just a linux desktop instead (DWC working through web interface conncection)

@p8blr The FW will run other tasks during the G4 command. But i'm not sure how long the G4 delay should be for proper function.

@infiniteloop @droftarts
Thanks, with your help I managed to achieve my goal.
I come accross with metacommands every other month or so, I think I need to engage more systematically in that matter.