Not at all, you can absolutely use it that way.
Still no blue light. Only red. I think I am connected but now I get a no heartbeat error. Searching the forums again.
Got some other weirdness happening I think. Updated firmware to .73 and it still shows as .71 when test is pressed on the Maslow side. On the fluid nc side it shows as .73
That is 100% my fault, I forgot to update the text there. Todayâs update will fix that.
Letâs start there. When you press âtestâ what do you see? That should tell us why the red light is on.
Whatâs the best way to capture that info. The ways I know and have tried are very limited and have not worked. Iâm not quick enough to copy it.
Itâs been a long time since Iâve even played with a windows laptop so Iâm having to relearn a lot of things as I go. Sorry.
I have an iPhone and a windows laptop. Thatâs about it.
That âMotor not found on top leftâ seems like the issue to me.
Can you try unplugging that motor and plugging it back in to see if that fixes the issue?
Did not help. Still have blinking red light and motor not found error.
What happens if you plug a different motor into that same port and press test?
That will tell us if the issue is with the motor or with the board.
Well. I think I may have found the issue. Heat sink too close to motor connector. Guess it was shorting it out because it made no difference if motor was plugged in or not- same error.
Now when test is pressed it looks like everything passes.
Still no blue lightđ¤
But blinking red is goneđ
Just a solid green light on the control board
That sounds like progress to me! Good catch!
So now the issue is that the âmaslowâ wifi network isnât appearing still?
No. Iâm using the Maslow network to get machine status. Original âissueâ was not being able to connect to home WiFi network. I assume that it will work now since that error is cleared out?
If you agree then I will attempt to get it on my home WiFi network and then follow the calibration video?
Ah rightâŚhow would you have taken screenshots of the UI if you couldnât connect
That sounds like a great plan to me
can you post a photo of the heatsink and area where it may have been shortingâthx!
My trouble was with the upper left motor driver chip heatsink. I tried to put it on the chip square and it must have made contact with the leads coming out of the back of the white connector. Totally my fault. Looks like the upper right might could have the same issue. Maybe needs to go into assembly instructions?
So after all of that. I didnât play to much with getting it on the home WiFi network since I had a reliable local connection thru the Maslow network connection. I gave up on that and went straight to calibration.
Success!!!
It calibrated.
So. Whatâs next???
Thank you and congrats! whatâs next is you is go build something big and amazing!
Whatâs next for the community is we explore the question of whether this might have happened on other M4s and figure out how to prevent it.
Well after calibration I didnât really know what to do so I just jogged the machine around and played with changing the distances and sending it to home and just getting the feel for moving it around and then it became unresponsive. No matter what I did it would not move again. No errors that I could see just no more jogging. Whatâs strange is that it looked like the software thought it was moving- the position numbers were changing but no physical movement.
Also @bar still no connection to home WiFi network and still no blue light.
I just did a test and this is actually normal. I thought that the blue light was always on, but it looks like itâs only on when connected to your home wifi. Why it wonât connect to your home wifi is still a mystery.
Do all of your wifi settings look like this:
But with your network name? Is it a 2.4ghz network?
This sounds to me like either the emergency stop was triggered somehow or the firmware crashed and reset. Did you need to refresh the page at any point, or did it just stop moving?