I bought this unit from the kickstarter. Was super excited. Successfully built it. Built an awesome table for it. Calibrated, updated firmware. Thats as for as I could get. I tried to do a simple logo cut into wood but I couldnt figure out the software side. Sadly I put it on the shelf, Happily I didn’t smash it.
This week I tried to use it again. I was able to upgrade firmware from 0.71 to 1.20
The user guide says to use the calibrate button but there is no calibrate button. I think it says calculate anchor points now. Is this the same thing? The user guide seems outdated.
After calculating anchor points for a while it now says that bottom right motor is not found.
This machine is the hardest thing I’ve ever tried to use and I’ve written my own Marlin code for a sand table I built using CoreXY. I know gcode and 3d printers. Why is this so hard?
This week I tried to use it again. I was able to upgrade firmware from 0.71 to 1.20
good, that’s a step a lot of people run into problems with.
The user guide says to use the calibrate button but there is no calibrate
button. I think it says calculate anchor points now. Is this the same thing?
The user guide seems outdated.
we changed the button label from ‘calibrate’ to ‘find anchor locations’ because
people were attaching too much meaning to ‘calibrate’ when what it is doing is
trying to calculate where the anchors are. the documentation has not been
updated yet.
After calculating anchor points for a while it now says that bottom right motor is not found.
normally when this happens, it means that the connector to the motor is not
seated well. We have had one person who found that the chip on the board burned
out.
you said this was a kickstarter unit, did you put the heatsinks on the chips?
they shouldn’t have been working so hard that they would burn out, but we did
have one other person who had a similar problem (that you link to below) where
the chip did burn out.
is this a 4.0 or 4.1 kit? (are the connectors to the encoders rj45 jacks like a
network cable?)
This machine is the hardest thing I’ve ever tried to use and I’ve written my
own Marlin code for a sand table I built using CoreXY. I know gcode and 3d
printers. Why is this so hard?
it’s different (being classed as a cable-driven robot), we don’t have nice,
orthoginal axis to work with, and the scale of the machine is such that most
people don’t have the ability to accurately position the anchors (or even to
accurately measure the distances between the anchors). So we have to do some
things indirectly. It means that some of the assumptions from machines with
simpler kinematic designs (cartesian or corexy are MUCH simpler to calculate
for) mislead your thinking.
The motor connecters have been seated and reseated. I swapped connecters so that different motors were used in that plug and it always says bottom, right
The motor connecters have been seated and reseated. I swapped connecters so
that different motors were used in that plug and it always says bottom, right
did you have heatsinks on the chips? and does the large chip next to the plug
that doesn’t work look burned/broken?
Can you post a copy of the full log file? That helps a lot to spot exactly what is going on. You can download it by pressing the “Save Serial” button in the bottom right of the screen:
Serial Messages
Index.html Version: v1.20
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v1.20]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 5]
[MSG:INFO: Axis A (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.11]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:NO_PIN Disable:NO_PIN R:0.11]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID maslow IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: WebSocket send protection active (canSend() checks enabled)]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|‘$X’ to unlock]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:ERR: Motor not found on Bottom Right]
[MSG:INFO: Current z-axis position loaded as: 2.000]
[MSG:INFO: Saved belt positions in NVS are marked as stale/invalid (value=0) - machine will remain in UNKNOWN state until belts are calibrated/extended]
[MSG:ERR: Maslow failed to initialize - fix errors and restart]
[MSG:INFO: Maslow update loop registered with hardware watchdog]
[MSG:ERR: Motor not found on Bottom Right]
[MSG:INFO: Channel auto report interval set to 50 ms]
Yup, that is exactly what you described. Nothing else weird going on there.
If you plug that motor into a different port on the controller does the message change? Like basically let’s try swapping around which ports the motors plug into and see if the message is different or the same.
Yup, that is exactly what you described. Nothing else weird going on there.
If you plug that motor into a different port on the controller does the message change? Like basically let’s try swapping around which ports the motors plug into and see if the message is different or the same.
he said earlier that he swapped motors and the error stayed with the port.
That sounds like a bad driver chip. We don’t have the 4.0 boards for sale in the store anymore, but if you DM me your address I can get one in the mail to you tomorrow!
