Making some good progress.
With the v1e LowRider config.yaml loaded on the Jackpot, I’m now able to jog X and Y axis around.
Some details and observations as I have started working with it.
Endstops still aren’t working. I discovered the @limits function, and the X/Y/Z endstop states are inverted (always triggered except when I hit the switch)
Homing Y seems to move away from 0 instead of towards.
Trying to home X, it also ran away to the 0 direction (Left as seen in my pictures above, away from the limit switch which is on the right side). It eventually hit and then drove for a long time and stopped.
Note: there’s no obvious way to kill a move from the UI. I’ll add a stop switch at some point.
I also noticed that the X motor is running moderately warm, while the parallel Y motors are very cool.
I reduced the drive current and holding current for the X motor to half the default values.
I realized that I have not yet installed an SD card. Duh! Found that from looking at fluidterm outputs as shown below. I also see that it’s not happy about the missing 6th driver (axis C)
jim@BR1100CKA:~$ python3 fluidterm.py
--- Fluidterm on /dev/ttyUSB0 115200,8,N,1 ---
--- Quit: Ctrl+] or Ctrl+Q | Menu: Ctrl+T | Help: Ctrl+T followed by 'H' ---
E (2098785) sdmmc_io: sdmmc_io_reset: unexpected return: 0x102
[MSG:ERR: sdmmc_card_init failed code 0x0x102]
[MSG:ERR: C Axis TMC driver not detected - expected 0x0x21 got 0x0x0]
I ran into an interesting error sequence uploading the config.yaml changes.
I used the file upload function, uploaded config.yaml, and then reloaded fluidnc with the power button on the GUI. Did that two or three times with no issues. Then, the next time I tried an upload I got this in the fluidterm:
E (50727) sdmmc_sd: sdmmc_init_sd_if_cond: send_if_cond (1) returned 0x108
[MSG:ERR: sdmmc_card_init failed code 0x0x108]
[MSG:WARN: Low memory: 14836 bytes]
[MSG:WARN: Low memory: 13816 bytes]
[MSG:WARN: Low memory: 13696 bytes]
[MSG:WARN: Low memory: 13428 bytes]
[MSG:WARN: Low memory: 12684 bytes]
[MSG:WARN: Low memory: 12532 bytes]
[MSG:WARN: Low memory: 12404 bytes]
[MSG:WARN: Low memory: 12276 bytes]
[MSG:WARN: Low memory: 12148 bytes]
[MSG:WARN: Low memory: 12096 bytes]
[MSG:WARN: Low memory: 11968 bytes]
[MSG:WARN: Low memory: 11848 bytes]
[MSG:WARN: Low memory: 11720 bytes]
[MSG:WARN: Low memory: 11600 bytes]
[MSG:WARN: Low memory: 11440 bytes]
[MSG:WARN: Low memory: 10020 bytes]
[MSG:WARN: Low memory: 8428 bytes]
[MSG:WARN: Low memory: 6852 bytes]
[MSG:WARN: Low memory: 5268 bytes]
[MSG:WARN: Low memory: 3684 bytes]
[MSG:WARN: Low memory: 3676 bytes]
[MSG:WARN: Low memory: 3548 bytes]
[MSG:WARN: Low memory: 3516 bytes]
[MSG:WARN: Low memory: 2724 bytes]
[MSG:WARN: Low memory: 2600 bytes]
[MSG:WARN: Low memory: 2576 bytes]
[MSG:WARN: Low memory: 2452 bytes]
[MSG:WARN: Low memory: 2396 bytes]
[MSG:WARN: Low memory: 2272 bytes]
Following that, I lost connection to the Jackpot ESP32. I ended up pulling the USB and killing power to the Jackpot board. After that, when trying to connect to it, I was getting an error that the ESP32 was not accepting the default 12345678 password.
After a couple more power cycles, I went off to do some work on my enclosure, and when I came back I was able to connect. Weird.
What’s the correct workflow for uploading a config.yaml and then restarting or applying it?
Questions:
How do I tell FluidNC the correct state of the enstop? I"ve toggled the config directive back and forth between these, with no joy:
motor0:
limit_neg_pin: gpio.25:high
also:
motor0:
limit_neg_pin: gpio.25:low
To try and get the direction correct, I fiddled with these:
homing:
cycle: 3
positive_direction: false
mpos_mm: 0
Changing positive_direction to true didn’t flip the axis movement as I’d expected… so a head scratcher for me.
