Hightmap comes and goes...
-
Hi *,
I miss the hightmap and any other plugin very frequently. It looks like that than:
It is on a mini 5+ in standalone mode. I tried new browsers, cleard caches, reboots of the duet. I have to restart the plugins when they are back in the "plugins" settings.
Cheers, Chriss
-
@Chriss Do you store the settings on the Duet or in local storage? Is that screenshot from Settings -> General -> Plugins and not from Settings -> Machine-Specific -> Plugins? You can open the dev tools via F12, go to Network, and check if the plugin assets can be loaded when you refresh the page. All the requests should be green (i.e. HTTP 200).
Duet software engineer
-
@chrishamm said in Hightmap comes and goes...:
@Chriss Do you store the settings on the Duet or in local storage?
On the Duet
Is that screenshot from Settings -> General -> Plugins and not from Settings -> Machine-Specific -> Plugins?
Ohhh, that can be the case. I'm not 100% sure at this point in time.
You can open the dev tools via F12, go to Network, and check if the plugin assets can be loaded when you refresh the page. All the requests should be green (i.e. HTTP 200).
Yes, I can do that when it comes back. What I can tell you is an experience from this morning. I had left some tabs open over night, printer off. I turned the printer back on. Went in one tab from here to there, saw that the hightmap was gone, opened the other tab with the hightmap still open. And I got a HTTP/404 there.
Let me wait till the error comes back, I will let you know how the responses from the duet are than.
Cheers, Chriss
-
Update: I reloaded the tab while the "heatmap" was open. I saw a HTTP/404 and a reload. I was able to reproduce it.
Does this point you into the right direction? (Yes the "Connection Reset" confuses me too.)
Cheers, Chriss
-
You don't need to worry about dwc-plugins.json because that's the JSON store for third-party plugins which you do not seem to be using yet.
The connection resets are rather bad though; I suspect the same happens for either dwc-settings.json and/or the heightmap plugin asset when the heightmap fails to load.
Do you have a Mini5+ Ethernet or WiFi?
-
@chrishamm
It is the wifi, connection reset indicates a "TCP RST" not a timeout. That is actually the part which confuses me. The problem is that I'm to busy with some other things, so I can not sniff the traffic right now. Maybe tomorrow... let's see. -
Keep in mind that we have two observations here:
1: I see the HTTP/404 shortly and the heatmap appears (latest screenshots)
2: The observation that the heatmap do not appear. The menu item is gone completely from the menu at the left. -
@Chriss You can ignore the 404 reports - they do not mean anything. The plugins to load are saved in dwc-settings.json and that file is loaded properly. But when plugins fail to load, they are automatically removed from the list of plugins to load next time, so I believe the actual plugin loading fails due to the connection resets. You can start the heightmap plugin again via Settings => General => Plugins (I'll rename the tabs in v3.3 to make the difference clearer).
Can you confirm that you are using DuetWiFiServer 1.25 and that the WiFi signal is good (< 60dB)? Does the same problem occur with a different browser/device?
-
Got it..
WiFi firmware version 1.25beta0 WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modemAnyway, the TCP_RST can not be caused by a bad WiFi signal, a bad connection may end up in a "timeout". (Btw. I checked that there is no IP collision).
I have seen that in all browsers in my workstation (Firefox, Firefox-Beta, Chromium, Chromium-Beta, Brave, Vivaldi, Opera, Opera-Beta).
I have not yet tested it with a other box (my laptop is lost somewhere in the flat.)
But I can tell you that I have seen it in at least one VM on the same workstation. Sure, that will not put the workstation out of the game here.Let me reboot my workstation tomorrow morning.. maybe....
Cheers, Chriss
-
@Chriss -66dBM is not great, not terrible. Any chance you can move the printer closer to your AP and check if that improves things?
-
I have not seen this issue since this morning any more. Maybe something wrong with my workstation? I'm not sure... I will keep an eye on it.
