Topics created by Danal

@Phaedrux Holy crap I didn't know. Thanks for passing this on

@sebkritikel excellent! Thanks. Nice to know that you can do a bit of tuning contrary to what I thought - Cheers

Aha! Thank you Chris. Yes, there are tool offsets. And sure enough, it stops at machine 330.

I can adapt my particular use case, now that I know how this works. And FANTASTIC that clicking on Tool Position toggles to Machine Position. Very VERY useful.

DOH!!! Of course. I will give that a try.

Edit: That was it!! Of course, S1 is the default, so I actually had to set it to S0 when I got the "address" right. Final Result:

M584 X0 Y1 U2 Z3:4:5 ; X and Y for CoreXY. U for toolchanger lock. Z has three drivers for kinematic bed suspension. M584 E1.0:1.1:22.0 ; Extruders for three tools. First two on 3HC 1, third one on Tool Board 22 M569 P0 S0 ; Drive 0 direction | X stepper M569 P1 S0 ; Drive 1 direction | Y Stepper M569 P2 S0 ; Drive 2 direction | U Tool Changer Lock M569 P3 S0 ; Drive 3 direction | Front Left Z M569 P4 S0 ; Drive 4 direction | Front Right Z M569 P5 S0 ; Drive 5 direction | Back Z ; End of main board drivers. Expansion boards have three each. ; Expansion CAN 1 M569 P1.0 S1 ; Extruder T0 M569 P1.1 S1 ; Extruder T1 ; At this moment, nothing on expansion CAN 2 ; Tool board CAN 22 M569 P22.0 S0 ; Extruder T2

P.S. THANK YOU! I knew it was something I was staring right at and not seeing.

Put the stable file back in /etc/apt/sources.list.d

Forgot to run sudo apt update and just ran the long duet install command. No warnings.

Ran sudo apt update

Ran the long install again. Warnings are back. That proves it DOES 'recalc' (or how ever you want to phrase it), based on presence/absence of the '.list' files, even if there are no actual updates.

Cool.

P.S. It asked the [Y/n] on every run. Nothing to do with the warnings, apparently.

Also found out that my "look backward" index is off. See lower block. Argument of 2 gets latest and 0 or 1 blows up.

Will fix later today.

./DuetVersion.sh Highest Available DuetSoftwareFramework = 2.1.2 Currently Installed DuetSoftwareFramework = 2.1.1 Dependencies for DSF version 2.1.1 are: duetcontrolserver (= 2.1.1) duetsd (= 1.0.6) duettools (= 2.1.1) duetwebserver (= 2.1.0) duetwebcontrol (= 2.1.5) reprapfirmware (>= 2.1.1-1) reprapfirmware (<= 2.1.1-999) ) reprapfirmware apt version 2.1.1-1 is internal version 3.01-RC10 ./DuetVersion.sh 2 Highest Available DuetSoftwareFramework = 2.1.2 Currently Installed DuetSoftwareFramework = 2.1.1 Command line arg specified to request Release -2 from highest available. Highest-2 is DuetSoftwareFramework = 2.1.2 Dependencies for DSF version 2.1.2 are: duetcontrolserver (= 2.1.2) duetsd (= 1.0.6) duettools (= 2.1.2) duetwebserver (= 2.1.0) duetwebcontrol (= 2.1.5) reprapfirmware (>= 2.1.2-1) reprapfirmware (<= 2.1.2-999) ) reprapfirmware apt version 2.1.2-1 is internal version 3.01-RC10

Good idea. I'll look at that.

THANKS

You could also rig something up with a super-cap and a relay. The relay is controlled by 5v and drops a GPIO pin to ground when 5v goes away. super-cap keeps Pi running until the GPIO event is detected and a shutdown script is executed.

@ChrisP said in Undervolts on Pi:

Looking at the schematic and @dc42's comment, I don't think it is the diodes since the regulator feedback is taken after these.

I've just tried starting my system up from cold with nothing attached to the Pi (other than the D3, clearly) and I didn't get power warnings at all (can be observed by either the Pi's red power LED staying lit or looking at the journal logs).

It may be right on the edge... I do get warnings in the above config. Pi 4B+ 4Gig.

As soon as I plugged the LCD in, I begin getting occasional under-voltage warnings that tend to last for ~6 seconds before the voltage shows as normalised again.

I probably should look at the logs more carefully. Eyeball doesn't see any change when I plug in my 7" LCD... but the Mark 1 eye has its limits. I'll do some math, and see if there is more influence than I think.

If I then open a chrome tab on the Pi with DWC then the it's under-voltage warning is on pretty much permanently with only the occasional flick off - not long enough to register as normalised in the journal logs.

Interesting. I'm letting the Chrome/DWC autostart. So my "nothing attached" baseline has this running. Hmmm....

Thanks for considering these topics. Timing "is what it is" with changes this big, that's understood. Thanks for taking a look at some of the fundamental directions.

@bothamichael this version isn't maintained anymore. you need to use duetlapse3 instead
https://forum.duet3d.com/topic/20932/duetlapse3?_=1620132755569

https://github.com/DanalEstes/DuetLapse

Is ready for "alpha" testing for those brave fools er, uh, kind souls who want to take a look. Run it with no arguments and it will begin to help you figure out how to run it. I have done some very basic testing, but have not yet even run it through a print.

It needs https://github.com/DanalEstes/DuetWebAPI in the same directory (or, technically, in your python include path). It shouldn't need anything else.

@Danal 👍 Thanks!

Quite a few commits in the last few days. Alpha testers are reporting success.

@Danal I put quite a bit of time and effort into getting the quad to print as a quad and just could never get it to work right. It was at that point that i decided that instead of writing the entire thing off as a waste that i would convert it to a Bowden Single Extruder and re-program the duet. After doing that, i'm pretty happy with it. It's quiet and efficient, and working which is a plus lol.

Got an answer from Adrian - for the curious ones 😉

1e3fc30b-1e35-4978-bca8-6afc5ced2f7b-image.png