Topics created by oozeBot

@Phaedrux I actually spent a bit of time early today trying to visualize just that! But I can't figure out the best way to do that when it's over a full 360 degrees. I mean, this works, but it still requires a bit of math in your head.

82a675d2-ea77-4965-9d4d-0d3f0f5c5ccc-image.png

@oozeBot Thank you, oozeBot. Yes, my explicit Z values are different to the typical slicer output, but they make it easier for me to see what is going on in the gcode. I treat the whole 'layer' idea a bit more loosely than a slicer would...

@oozeBot Thanks for pointing it out, I just removed the section about gpiochip4. The automatic change in config.json to gpiochip4 was removed last year and that change is already in the latest DuetPi version, so no further changes should be needed at this point if the stock image is used.

Thank you both! I'll have an engineer do some testing on it. We've never seen one have this kind of issue before and would like to understand if we (really, myself since it's been on my desk) caused it damage or if it was just a faulty board. I'll go ahead and remove the "Unsolved" tag.

@chrishamm Thanks! That’s the nudge we needed- It’s definitely a permission issue. We’ll get it sorted.

@infiniteloop we’ll discuss- not against it at all but would want to spend a bit more time on the design and then have a few made for verification before posting based on the initial batch we received. We have a lot going on at the moment but will revisit soon!

@chrishamm That all makes sense. I like being able to build it all together as DWC builds pretty quickly on our build server but yeah, bypassing DWC if it hasn't changed is a good idea. I just wanted to make certain I wasn't overlooking a flag or something but didn't know how I could be after reviewing the code. Thanks

@oozeBot Looks good, feel free to send me a PR for this!

@droftarts Appreciate it. What we have built is also time-series but with the addition of joining tables where applicable to dive in deeper.

Good to know its safe to poll the objectModel that rapidly! We were a bit concerned with doing it every 5 seconds!

@oozeBot Yes I agree there is some lack of documentation ... and for now it mainly requires reading the code.
But on other hand, an IDE would suggest you the class attributes/properties and I believe the names are still pretty explicit.

@mikeabuilder Thanks! That's option B which we listed above. It would less of an issue if Macros showed up on the main screen of our IDEX machines, but they don't - meaning the end user has to navigate to them to access.

For posterity - this must have been an issue with Python as upgrading to 3.12 resolved the issue I just reported.

https://github.com/Duet3D/PanelDueFirmware/issues/289

mfs12 created this issue in Duet3D/PanelDueFirmware closed Wrong simulated time is displayed #289

https://github.com/Duet3D/PanelDueFirmware/issues/284

mfs12 created this issue in Duet3D/PanelDueFirmware closed Test "print again" with long filenames #284

@oozeBot is it running cancel.g?

@gloomyandy schematics are here https://github.com/dc42/PanelDue

Confirmed this works:

G29 S0 if result !=0 abort "Probing Error - canceling job"

@chrishamm Sorry for the delay in our response on this- we let it slip. This primarily occurs when the machine is homing and the e-stop is pressed. It is easily repeatable on our machines running 3.4.4 with a SBC and the stock PanelDue firmware 3.4.1.

We have some time to further research, but so far nothing in our homing scripts has been identified as the issue. To reproduce, all we have to do is press the e-stop button while the gantry is homing in X or Y direction (haven't tested Z yet). Thanks

Before moving on to other work, I went ahead and added a custom mCode that will run any script located in the list by calling it through a parameter. This opens the door to easily include custom functionality into job files, macros, etc.