Hi,
During testing / setup etc occasionally the connection to the Maslow would drop, or for some reason disconnect in that when I tell the Maslow to jog, it says it’s moved but the machine hasn’t. A refresh of the browser re-opens the connection and I just hit home and start again. Perhaps at the expense of more traffic have the browser send a heartbeat?
Like the XY position indicator shows it moving, but the machine stays in the same place?
Does it say Alarm in red on the right hand side when that happens?
This issue seems to be coming up a bit at the moment. I dealt with it too and it was infuriating to get anything done as eventually refreshing the browser didnt work and i had to power cycle and start again.
For me, connecting the Maslow to my home wifi and connecting through that rather than directly connecting to the maslow wifi definitely helped, i still get some issues now and then but its much less frustrating
Pondering…
I have not collected data to support this thinking; it’s just what comes to mind. I have (after a lot of challenges) had pretty good success more recently.
Yeah that’s right - so the position in the browser updates but the machine doesn’t move. I could be wrong, but I think even the fan on the Maslow starts up while it says it’s moving but the machine just stays. Then I refresh, and it moves again
The alarm isn’t armed.
Also, it’s connected to the home wifi close to the AP, signal isn’t an issue.
Using safari on Mac, sometimes the little purple dot doesn’t move well - Brave browser seems more stable for me.
David Negaard wrote:
- We know that sometimes the browser reacts poorly with the direct connection
to the Maslow hotspot, causing the browser to disconnect (I’ve had fewer
issues with Firefox, but it still complains about there not being an internet
connection). This suggests to me that if the connection is not to
the Maslow hotspot, the browser behaves better.
Yes, in recent years, it’s become the fad to assume that you don’t want to do
anything using a network unless you are connected to the Internet.
never mind that it’s perfectly legitimate to have a network completely
disconnected from the Internet with internal-only resources. (in fact, this is a
really good thing for security)
so Operating systems and browsers both try to get out to the Internet to reach
‘known’ URLs at google/apple/firefox/etc and if they can’t get them, they assume
that you are on a broken network. At best, they assume that you are behind a
captive portal (like a hotel/dorm) that you need to login to to reach the
Internet. So they do various things (give you a limited version of the browser,
disconnect after a while with the thought that you will then connect to a
different network, etc). All of these ‘helpful’ steps interfere with the simple,
direct connection we are trying to make with the maslow.
shortly after the maslow 4 shipped, there was some work to identify these
endpoints that different browsers/OSs try to connect to and make the maslow
answer to trick them into working properly. It seems that either something has
changed or we have missed some. The fact that some browsers work better than
others probably helps identify what is missing.
David Lang
Do we have a list of known good/known bad browsers and devices/OS’s for this? I’ve been trying to control my M4.1 from my iPhoneX and it’s been a nightmare. It drops after extend all. Refresh usually sorts it out, but not always, and when it fails the Maslow is in an unknown state and I have to start over.
I’m seeing this with the 1.0.5 firmware. I have turned off the connection monitoring. I am connected over non-Maslow Wi-Fi. I am seeing the x,y coordinates in the interface change. The fan runs when the jog command is issued. I’ve found that what causes the machine to finally move is going into Setup and commanding Apply Tension. This works somewhat inconsistently. It also then moves in a stair-step or herky jerky fashion.