Tore Westre wrote:
I will try that to see if the index file changes anything. Is it possible to upload the 0.88 again after the memory re-allocation if all else fails?
The process to install v1.0 can be used with the older versions.
but I believe I also saw that you could use the 0.88 with the new allocation as
well.
David Lang
I have seen this error before too. There is a black button on the control board (you will probably need to take of the cover with the fan to see it). Holding down that button will put the board in “boot mode” which will make it easier to program. To get it to work the order has to be hold down the button and THEN plug in the power (while keeping the button held down)
That worked for my part also when I connected the board to my PC at home. Thank you David!
What kind of glitches do you experience? Just in the WebGUI? Or anything that supports going back to 0.88 for calibrating and use?
And thanks to @bar and @md8n for the great work! Knowing about the button for download mode makes me feel safer testing neew releases.
Hoping to get in a few cuts tomorrow!
I haven’t dug any deeper, yet; I’m in the middle of a design project that has a deadline, and until I can access my frame I can’t run calibration or any cuts.
I will test a little tomorrow and see if I get the same behavior. I did notice the No Connection message as I opened the webpage.
If you’re seeing this then try a different USB port on your computer. It’s more a matter of resetting the USB than anything, but the easiest way to do that is to swap ports.
OK, I’ve found the bug causing the ‘no connection’ alert and fixed it. This will also fix other ‘potential’ (but likely) problems.
Plus another issue…
You can get this for yourself and build it at: deepCopy params to prms by md8n · Pull Request #121 · BarbourSmith/ESP3D-WEBUI
But otherwise wait for @bar to rebuild it
For those playing along at home
http.js as undergone some massive changes to clean it up, and to alleviate some very naive assumptions that were made in the code. What I did is still somewhat naive, but at least it’s a bit better, it’s definitely more robust.
So now, when the front end wants to send something to the backend (M4) it adds what it wants to a queue. And then that queue is managed separately, with a better lifecycle for each message being sent.
The queue processing is throttled with a 10ms delay, but really this is about ensuring that the queue of messages (going to the M4) is treated asynchronously.
I have managed to calibrate with version 1.0 and the updated index.html.gz, but I have not installed the version that includes the fix for the ‘no connection’ alert.
I can’t find any other forum posts for version 1.0. Should we keep posting our findings in this thread, or make another thread for each issue we find?
Yeah, you’ll probably want that version
@bar - heads up
I’m on it!
Just in case it was not fixed in combination with the previous fix. Downloading files via the “Manage Local Files” does not work as intended in Chrome and Edge browsers(only ones tested) on 1.0 firmware and 1.0 index.html.gz. Files are being downloaded as “undefined.htm”.
Uploading 0.88 fixes the issue, but I was not awake enough to check if it was the 0.88 firmware or indexfile that made the difference.
Just got the message that 1.01 is available!
Thanks @bar !
I will test it tomorrow and se if we can get a cut going!
Thanks for being the guinea pig on this one! I just tested it and it seems to work for me, but I’ll believe it when it works for someone else!
I also made a youtube video to guide folks through the process which is uploading now:
Aloha @bar,
I’ve followed the process and I think it worked, but…
I’m still having issues with setting preferences in the “hamburger” menu on the Maslow tab.
Here’s the default for Connection monitoring
Here’s what it’s like after I change and save the setting:
And here’s what it looks like after I refresh the browser window:
So, same as 1.0, my preference settings don’t persist.
Yeah, I didn’t touch any of that code at all. I wanted to make sure that the HTTP shenanigans were sorted out first
" I just tested it and it seems to work for me, but I’ll believe it when it works for someone else!"
I just tried uploading from the menus from V1.0 to V1.01. Index.html.gz loads, but the firmware.bin is ignored.
Following extract from Test:
Test
Index.html Version: 1.01
[MSG:INFO: Firmware Version: 1.0]
[MSG:INFO: I2C Timeout: ]
[MSG:INFO: 10]
As I still found myself cursed with the “Fatal Error. No serial data received” message, I figured I’d do a fresh install.
I put my board in “boot mode” with the button held in while powering on.
I then successfully ran the installation with the files from release 1.01.
Connected with no problems, and did not get any error messages.
Ran a successful calibration with fitness around 0.56. Can’t remember exactly since I forgot to bring my notes back with me…
Regardless, I will list what I remember.
Findings so far:
After refresh and restart of FluidNC:
I then uploaded the 0.88 version of index.html.gz, but kept the firmware.
The above issues marked with * was resolved after this.
When I loaded the changes from V1.0, I did it from windows without pressing the button, which seemed to work OK, but I could not see the lownloaded .nc files until I loaded another file and they did not persist after a restart. I have just repeated the Install firmware (to V1.01) following your new video and I can now see the files after the restart. It still displays firmware V1.0 however (on the Test output)..
I just tested and mine does that too
Index.html Version: 1.01
[MSG:INFO: Firmware Version: 1.0]
I think I forgot to update the variable name somewhere, but it is actually the correct version.