okay, ill do 1-3 air cuts depending on performance of the machine and report back
1 Like
I agree with this, that does make sense. Do you want to make an issue for it?
1 Like
Bar wrote:
I agree with this, that does make sense. Do you want to make an issue for it?
will do.
David Lang
2 Likes
i did one air cut it did fine then i tried to get it ready for another told it to trace the boundary since it was a little high on the board i moved it down a bit and it went towards the edge then just kept going and wasnât going to stop because it crashed
i did one air cut it did fine then i tried to get it ready for another told it to trace the boundary since it was a little high on the board i moved it down a bit and it went towards the edge then just kept going and wasnât going to stop because it crashed so i had to unplug it
That can happen if Maslow loses connection. Until we can figure why itâs losing the connection, you will have to be ready on the power when testing.
When it fails, put a copy of your serial log up. It may be helpful to identify what is happening.
Maslow-serial (25).log (2.4 KB)
That doesnât help. In the maslow.yaml file there are settings for Maslow_Work_Area_X and Y. I have mine set to 2000 and 1000 to stop Maslow getting too close to the edges. Do you want to try something like that while testing to ensure it wonât run off the edge?
Would that even work when its crashing and not receiving new info?
Donât know but itâs worth testing. just be ready on the power button if it looks like going out of bounds.
1 Like
could it somehow be crashing because it is loosing connection to my laptop and not able to computer? ik it is supposed to work when disconnected and sometimes mine does but usually it just fully crashes from the machine computer and disconnects me, it also fails to connect to my laptop a few times compared to my tower pc which seemingly works almost every time, but i donât try and connect it as much so it might just be because i havenât tried to connect to it as much that i feel that way, its just strange that even after the full 4.1 upgrade everything is still not functioning even know itâs almost a completely new set of hardware its running, could it be one of the motors shorting or something internal? i really want to get this machine working so it can be the heart of my new business support my existing business and allow me to make content about it bringing more people into the community, but i just donât know what to do to track down this issue, Iâm gonna go and try and shake some wires and stuff but if that doesnât work i really need to take it back down and cut all the pins but Iâm scared of the screws stripping and me having to destroy the plastics and boards on those halves, how likely is it that the new 4.1 screws with the Loctite strip out?
From the last serial log it looks like you are connecting directly to the Maslow via its internal network. Have you tried with a local network?
Can you put the serial log of the latest attempt up.
what do you mean by internal and local networks? currently i am connected to my internet and the maslow is connected to the internet so i can connect to it through the maslow.local, do you mean to have it disconnect and only show up as maslow as a internet? or connect it via wire to the board? Iâve tried all 3, it seems to do better possibly when its hardwired to the machine but my laptop if its not hardwired and trying to connect to the maslow internet struggles with it still
Sorry, I got confused. It is connecting via your local network (Lollypop on 192.168.1.17)
1 Like
It seems like wifi connection issues are the current issue that folks are running into (issues seem to come in waves where a few people will have the same issue at the same time) so it is next on my list to work on. I am going to try to add more diagnostic tools to the next firmware version so that we can more clearly see what is happening with the wifi connection and hopefully troubleshoot things like this more quickly.
2 Likes
so, should i try hardwiring it until i find the source of the issue to take out that factor from the equation?
You canât run the Maslow via the USB, but it can give us more information. You can connect via USB using the software in the firmware updates
fluidnc-maslow4-1.17-posix.zip for Apple or
fluidnc-maslow4-1.17-win64.zip for Windows
i donât understand what that means? so does it normally just give more info but i can with that setting or file or?
Caleb Yager wrote:
i don¢t understand what that means? so does it normally just give more info
but i can with that setting or file or?
when your machine crashes, not all the data can get sent over wifi (same if you
are having the wifi disconnecting)
being plugged in to the USB port shows more data from the firmware (but not the
data the UI generates), so if it actually crashes, we can see the crash message.
If the wifi is disconnecting, we may see info about that (hopefully @bar will
add some debugging messages to help with this)
David Lang
1 Like
oh alright, cool, ill try that, thank you for the explanation