Hi, I tried improving my accuracy by doing more calibrations,
I have this recuring issue, after the first set of point to check maslow get stuck, I can’t send command and if I refresh or try connecting in another tab I can’t anymore, like it is completly crashed. I am then forced to restart and the position is not saved so I also need to retract and extend again.
It happened to me once when I tied 3x3 on 400x400mm, after the little calc it does after the 5th point. I tried again and it worked this time.
Then I tried 7x7 800x800mm it happened again after he 5th point, tried again and it happened after the second set (like, 12th point)
I’m running 1.15, I wanted to attach my log but it was not downloaded because I forgot to confirm download from http, but I do remember it said the “confirm this values line” and then “calibrate” and just got stuck since
I also got a weird console messge, uploaded it but I dont think its the issue
It does seem like the issue might have something to do with HTTPS vs HTTP in a setting somewhere.
I’m seeing this error message in the log that I haven’t seen before which does seem like it could be related.
%200.0%0AA%20command%20to%20save%20these%20values%20has%20been%20successfully%20sent%20for%20you.%20Please%20check%20for%20any%20error%20messages.%0ACalibrate' was loaded over an insecure connection. This file should be served over HTTPS.
It seems like maybe the computation is finishing on the computer, but then when the computer tries to send the results to the machine it isn’t able to send them.
And I’m using the ap mode, not connecting to another wifi
I’m thinking this maybe because of dropping connection and my error is just there but people usually do not notice it because they don’t get the calibration stuck, maybe there’s a way to make the sending back more robust?
chrome has recently added warnings for downloading via http instead of https
To stop Chrome warnings for non-secure (HTTP) sites, you can either use the
risky chrome://flags setting to disable the “Not Secure” label globally (not
recommended) or, for specific sites, go to Chrome Settings → Privacy and
Security → Site Settings → Insecure content and add the site’s URL to the
“Allow” list, though Chrome often prioritizes HTTPS for security and warns you
about mixed content.
For Specific Sites (Recommended Approach)
Open Settings: Go to chrome://settings/content/insecureContent or click the
three dots > Settings > Privacy & Security > Site Settings > Insecure content.
Allow the Site: Under “Insecure content,” find the “Not allowed to show insecure
content” section, click Add, and type the URL (e.g., example.com) you trust to
allow it.
For All Sites (Not Recommended)
Open Flags: Type chrome://flags in the address bar and hit Enter.
Search: In the flags search bar, type “secure”.
Disable Flag: Find the “Mark non-secure origins as non-secure” setting and
change it to Disabled.
Relaunch: Relaunch Chrome for the change to take effect.
Thanks I will do that, though I don¢t think it is related to send file using
http error
I think this is exactly related, it’s complaining that you are sending the file
via http vs https. This should disable the browser fussing at you about doing
so.
If this doesn’t solve the problem, paste the exact error message into a browser
search bar and see if there is another way to eliminate it.
unfortunantly, trying to create a cert and load it is not going to work for an
offline device like the maslow in AP mode.