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.

@micaheli I got bed leveling to work using the latest unreleased firmware. See this thread. Note that I am NOT using touch mode. There are still some mysteries but it appears to be working.

https://forum.duet3d.com/topic/37755/szp-for-bed-level-in-3-6-rc1/19?_=1742942881479

@sebkritikel Awesome news! Thank you.

@jltx

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

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

spoke too soon. I ran it again and it made odd adjustments to the Z motors and then the head crashed into the bed pretty bad. I also noticed that it only does the first dive, not the second, e.g. 15 but not 5.

; Clear any bed transform
M561

; Turn off noisy Extruder motor
M84 E0


; Lower currents, speed & accel
M98 P"/macros/print_scripts/setup_probing.g"

;if !move.axes[2].homed
  ; Home all axes
  G28

  G1 Y240 Z6      ; move coil over bed and higher than trigger point
  M558.1 K1 S1.5  ; calibrate height coeff

  ; Probe the bed at 3 points, x3 for more precision
  M558 K1 H15:5 F800 T15000; increase the depth range, gets the gantry mostly level immediately
  M98 P"/sys/bed_probe_points.g"
  M558 K1 H4:2 F400 T15000  ; reduce depth range, probe slower for better repeatability
  M98 P"/sys/bed_probe_points.g"
  ; last attempt will be auto-repeated


M558 K1 H1 F60 T15000   ; reduce depth range, probe slower for better repeatability
while move.calibration.initial.deviation > 0.01 ; 0.003
  if iterations > 3
    abort "Too many leveling attempts! Canceling print."
  M98 P"/sys/bed_probe_points.g"
  echo "Current deviation: " ^ move.calibration.initial.deviation ^ "mm"
echo "Leveling complete"

;use mechanical instead? G30 S-2 ; Z=0

; Restore high currents, speed & accel
M98 P"/macros/print_scripts/setup_printing.g"

@droftarts said in getting blank page for DWC on iPad:

@jltx said in getting blank page for DWC on iPad:

it says iOS 10 and up in the documentation

Can you post a link to where it says that, please?

Ian

https://docs.duet3d.com/User_manual/Reference/Duet_Web_Control_Manual#:~:text=Browser Compatibility&text=Duet Web Control file editor,work in any earlier versions).

@chrishamm it says iOS 10 and up in the documentation. I'm on 12. I can't find any modern websites that don't work. Youtube via browser works. It seems there is a path for html5 to work fine. What changed in DWC? Is there a new feature that requires advanced capability?

Holy smokes! these js are huge! like 200k lines. I was going to ask ChatGPT to fix it but not enough tokens

found two errors.

first:

second:

I hooked it up in debug mode. No clue what I'm looking at...

I have an old iPad with iOS 12.5.7 which was working previously for DWC. Now I just get a blank page in all the browsers I have tried. I am on 3.6.0-rc1. I tried to update to rc2 but I cannot sftp the files into www because I don't have permission. I really want to use DWC instead of 12864 display. @chrishamm any ideas to get this working?

@chrishamm said in SBC may be overloaded:

@jltx M929 isn't really needed in SBC mode because journald already keeps track of most important messages. When did you flash your microSD card? Is it rated A1 or A2? Can you confirm that vcgencmd get_throttled via SSH/terminal outputs 0x0 (not throttled)?

If you are still using the Debian Buster-based image, it's time to upgrade: https://docs.duet3d.com/en/How_to_guides/SBC_Buster_to_Bookworm

I am using A2 card with Bookworm. I did get 0x0 output. I have not seen this after the first occurrence. Where does the journald log go? /var/log?

I had a print abort right in the middle. Never seen this before. I am on 3.6.0-rc.1+2. I have printed several hours successfully on this version. How to go about debugging this?

@gloomyandy said in SZP for bed level in 3.6-RC1:

You are not setting the probe threshold/trigger value in config.g (the P parameter to G31), so it will be using whatever the default is (which is almost certainly not correct) until you have performed a M558.1.

Correct. You can't guess this value so it would just be a random number. Before any use of the SZP I run a M558.1, such as in bed.g and mesh.g.

As to the mesh not reading zero at the centre of the bed. I would expect the scan to return 0 for wherever you have homed/set Z=0, ideally you will be homing and calibrating the probe at the same location

correct. I answered myself above when I remembered I am setting Z=0 with a separate probe at the back of the bed. So the bed scan does not necessarily cross zero, especially if the G31 offset for that probe isn't close enough.

Everything seems to be running well. I don't know why I had so much trouble setting it up. I understood the documentation but thought that I didn't because the results were so flaky. Knock on wood but it is stable right now. It is a very slick setup and much better than what I had before. Thanks for the help.

@jltx answering my own question: no. The Z reference is the rear probe (K0) and so bed center can be offset.