Topics created by jltx

@T3P3Tony Yes, I used the V parameter as you show. And I assume the prior F parameter worked or it would not have found the 3.6 beta files that I specified.

@jltx Thanks, fixed!

For example, G31 Z1.2 T0.02 S20 H2 when sensor 2 measures 26C would calculate trigger height as 1.2 + 0.02x6 = 1.32mm

Ian

@T3P3Tony That is correct, the T value applied to the M558 command does change the travel speed, but it does not honor machine limits. Additionally (I didn't test this part again for fear of damage) if you leave off the T parameter altogether it uses an extreme travel speed. I'm not sure where it would have calculated that based on other settings.

@jay_s_uk Thanks for clearing that up. Too bad because the Pi antenna is poop. But at least I can simplify things.

Well that was quick. I found if I right click there is a reload menu which caused it to come alive. All works great now! Hope this helps someone else.

Ok, it was as simple as using raspi-config to boot to terminal (CLI) instead of desktop (GUI). I'm new to RPi so this was probably obvious to all.

BTW, fun fact, the desktop uses about 600 KB RAM at 1280x900. That leaves me with about 960 KB free which I hope is sufficient.

Bonus side effect was switching to CLI and back seems to have resolved my system instability. So I am happy.

OK, I may have inadvertently resolved it.

I found how to remove the desktop and boot to terminal using raspi-config. I wanted to understand the RAM cost. I have an RPi4b with 2GB RAM.

FYI:
in terminal mode after boot I have 1.5 GB free.
In desktop gui with DWC running at 1280x900 I have 960 KB free.

Anyway, after switching back to GUI mode everything boots as expected and DWC starts. So I suspect my config was whacked somehow (I touched nothing!) and running the rasp-config corrected the situation.

Sorry for all the bother.

@sebkritikel Awesome news! Thank you.

@dc42 I did check the console and it had no errors reported. But I’m not clear that it captures anything when my laptop is asleep. I feel like it skips over anything incoming while asleep.

Is there a mode I can set the treats M0 like M1? I can’t ever think when I’d use M0. I never have before. More likely I think is your theory on SD read error (though I don’t know what that would happen either, just more likely). But wouldn’t that get captured in M122? Also the failure mode there should be a pause by firmware to allow for restart, e.g don’t turn off bed heater or motors and send warning. I was lucky that I happened to catch it. I was about to go to bed and it would have been ruined the next morning.

@fcwilt
That's clever. I'll have a think about that.

@jltx said in 12864 stopped working in 3.4b6:

I cut and paste each step from the wiki into ssh on pi. when I pulled the SD and looked at the contents I see all empty directories with just a template config.g in sys.

If you're using a raspberry pi, the SD card is not a readable format in a windows computer. The config files are located in the linux file system on the pi.

@phaedrux I got it from the US distributer, I think in May this year. Anyway, I already bought another and set it up. Just thought you should know.

So after a few failed attempts ("Error: Failed to connect to DCS (A task was canceled.") upgrading/downgrading between 3.3 and 3.4b6 I finally got it to stick and now I see the menu directory! Hooray!

Hopefully this beta is stable enough to use.

@jltx as per thois post https://forum.duet3d.com/post/229692 on the Duet 3 Mini5+ you need to connect the DHT22 signal pin to both the IN and OUT pins of an I/O connector, not to a spi.cs pin.

@jltx Glad you got it sorted. Electronics often behave when I start looking at them! They respect my authority...

Ian

@jltx

third try was the charm. working now. sorry for the noise