I received the Maslow two weeks ago, and I’ve already done some work with it, but since yesterday, the bugs just keep coming with the same message over and over: “you are disconnected, connection lost for more than 20s.”
So, I tried to reset the parameters, but when I went to start a new calibration, I got the same message again.
In addition, at certain times, a red light appears on the motherboard.
Maslow-serial (3).log (3.3 KB)
the problem has nothing to do with calibration, so restore your old maslow.yaml
file to keep the settings.
do you know if you are getting wigi disconnects or just browser disconnects?
do you connect to the maslow in ap mode? or is the maslow connected to your home
wifi?
what firmware version are you on?
David Lang
Hugues Simon wrote:
Yes, you’re right, but I did a full reset, so I had to run a new calibration.
It’s only browser disconnects.
The Maslow is connected to my home WiFi, and I’m using version 1.10.
Hugues Simon wrote:
Yes, you¢re right, but I did a full reset, so I had to run a new calibration.
once you have a working system again, save your maslow.yaml file. calibration is
just figuring out where the anchors are, once you have those numbers, you don’t
need to run calibration again (unless we get a better routine)
It¢s only browser disconnects.
The Maslow is connected to my home WiFi, and I¢m using version 1.10.
you can go into preferences and disable the 20 second connection check. see if
the connection is really having problems or not.
what changed about the time the problem started (network activity, firmware
update, etc)?
David Lang
There you go, after a recalibration everything seems to be back to normal. I saved the .yaml. Thanks for the advice @dlang
This morning the disconnection problem happened again. It’s not even possible anymore to perform “retract all - extend all,” I immediately get the disconnection message. As a reminder, I had this problem yesterday, which seemed to be resolved. After a full reset, I was able to work normally again. I saved the .yaml file, but updating it this morning doesn’t change anything.
I sould suggest turning off the check in the preferences and see if you can use
it with the check disabled.
David Lang
Regarding the discussion above, the problem now seems to be resolved. I noticed that the manipulation of one of the four arms was problematic, and when I ran “extend all” it started to fully unroll and then rewind in the opposite direction. I then concluded that the issue was coming from the magnet. I disassembled the arm, cleaned everything, and reassembled it, and now it works again. The inside of the arm (and the magnet area) was very dirty. Could this also explain the disconnection issues? Since then, I haven’t had any more problems.
Hi Simon, hope you don’t mind if I join your discussion.
I was having the same disconnection issue. It cleared for me when I went into my “settings tab” and found the “device manager tab” and found the wifi hardware device. Windows defaults this device to “disconnect when the computer detects inactive connection” (or something to that effect). I believe Windows doesn’t “see” wifi activity when the maslow4 is cutting (because you are not clicking your mouse and changing web pages, etc.) and decides to close the connection to save power. When I unchecked that box. The problem was solved. This was after I had changed a bunch of settings: including changing the power settings on the screensaver, harddrives, and computer to “never shut down.” I also would recommend connecting directly to the maslow wifi network. Do this by clicking your wifi tab. It should show several wifi networks including “maslow.” Click maslow and supply the maslow password (12345678) you can change it later. I am using Windows 10 and a dedicated old computer just to run the Maslow. I found that connecting to my home wifi network “distracts” the browser and opens my computer up to “insecurity issues.” Set your home page in your browser to the IP number of the maslow (192.168.0.1). I don’t know if changing these settings will solve your connection problem, but I saved me much time and frustration.
Also some belt issues for me, seemed related to vibration. It happened when my cutting tool was not concentric (wobbly) or when I exceeded the z-axis upper limit and z-steppers started bouncing. At that point, I noticed slack in a couple belts. I cut power immediately to Maslow to save the belts. I had to rewind the belts manually after that, but the maslow kept it’s configuration and it’s machine home position.
I also took Bar’s advice about Increasing belt tension to address the “retract all” and “apply tension” issue to get all the belts to cooperate. My setting now reads 1500. Hope this helps.
