The heightmap tab isn’t visible when I open moonraker from chrome. It is visible from my cell phone (android) or from firefox. (I don’t do windoze).
Also, the webcam view appears on the right side of the screen on firefox, but on the left side in chrome. (vertically separated on the phone, but I expected that!)
I don’t think this is the best place to ask about this.
And you don’t open moonraker with chrome or firefox. Moonraker is an API that allows a web interface (Mainsail, Fluidd, Octoprint, Kilp pad, Mobile Raker etc) to get data out of Klippy. Moonraker doesn’t “serve” web pages.
Which interface do you use?
Also note that your browser sends a “user agent”. Most web sites “serve” different layouts depending on that info. It is common for manufacturers of phones/tablets to play games with the default user agent settings.
I noticed some differences in the layout of the Zero web interface compared to my Elegoo Nepture 4 and Sovol SV08 but most of the functionality is there in the Brave browser running under Linux, including the HeightMap feature.
I love how the Zero’s Eddy probe is fast and accurate. I just made five consecutive 400 point bed mesh calibrations in 100 seconds and the results were very repeatable.
Range: 256, 259, 259, 256, 257 microns
Min: -181, -182, -182, -181, -182 microns
Max: 75, 77, 76. 75, 74 microns
I made screen shots of the bed mesh graphs and when I quickly scroll through them, the mesh surfaces are almost identical. This is WAY faster and WAY more accurate than the 8 mm inductive proximity sensor on the SV08. I can’t wait to replace it with the Eddy probe.
1 Like
I guess I meant “mainsail” not moonraker.
In a recent youtube review of this printer, the reviewer mentioned that his printer got bricked after an OTA update, and he got no help from Sovol in getting a replacement flash chip due to “the Tariff issue”. Needless to say, I’m not going to attempt another OTA!
I stumbled across OTA in the Zero menu while I was assembling the printer and clicked on it before the user manual assembly instructions recommended and it worked just fine. Maybe I got lucky?
1 Like
This was before they were being sold to the public.
The version 1.4.0 update (which identified itself incorrectly as 1.4.1) did also result in a state that someone might call “bricked” as the printer was only accessible with ssh while the screen stayed blank. That update was however available most likely only for less than 24 hours before getting rolled back to 1.3.8 so it’s not too likely that many got it installed. Thankfully there’s no auto-OTA existing or enabled.
After spending one afternoon figuring out what went wrong with 1.4.0 (it was a failed firmware flashing due to an issue in the flashing script), I’ve taken the practice of diffing the firmwares as I have a feeling those contain a little bit more than what the change notes (wow, we got those starting from 1.4.2) mention. It would, for example, be nice to know why the pressure sensor isn’t anymore used for z offset calibration. I’m also not a fan of the chamber fan having been tied to the chamber temperature sensor and configured to try to get the temperature to 32C or below by default, which mainly creates extra noise when printing with the door open.
No this reviewer bought his printer himself, and received it in the first batch sold in the early bird, same as I did.