Z0 doesn't respond


Hello everyone.

I have built my Lowrider 4 with a Jackpot CNC Controller, and everything seems to work perfectly except for the Z0 axis, which doesn’t respond. If I swap the motor to the B axis, it works without any issues. When I run the $SS command, all the drivers are detected correctly.

Does anyone know what could be happening? Thank you

Can you post the response to $SS please? Have you also tried a different, working stepper driver board in Z0?

1 Like

Deleted by author

Agreed that $ss lets us know a lot of things, most importantly here, is the right firmware.

$SS
[MSG:INFO: FluidNC v3.7.17 GitHub - bdring/FluidNC: The next generation of motion control firmware]]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]]
[MSG:INFO: Local filesystem type is littlefs]]
[MSG:INFO: Configuration file:config.yaml]]
[MSG:WARN: Increasing stepping/pulse_us to the IS2 minimum value 4]]
[MSG:INFO: Machine LowRider]]
[MSG:INFO: Board Jackpot TMC2209]]
[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]]
[MSG:INFO: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21]]
[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]]
[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN freq:20000000]]
[MSG:INFO: Stepping:I2S_static Pulse:4us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]]
[MSG:INFO: User Digital Output:0 on Pin:gpio.26]]
[MSG:INFO: User Digital Output:1 on Pin:gpio.27]]
[MSG:INFO: Axis count 3]]
[MSG:INFO: Axis X (3.000,1263.000)]]
[MSG:INFO: Motor0]]
[MSG:INFO: tmc_2209 UART1 Addr:0 CS:NO_PIN Step:I2SO.2 Dir:I2SO.1 Disable:I2SO.0 R:0.110]]
[MSG:INFO: X Neg Limit gpio.25]]
[MSG:INFO: Axis Y (3.000,2483.000)]]
[MSG:INFO: Motor0]]
[MSG:INFO: tmc_2209 UART1 Addr:1 CS:NO_PIN Step:I2SO.5 Dir:I2SO.4 Disable:I2SO.7 R:0.110]]
[MSG:INFO: Y Neg Limit gpio.33]]
[MSG:INFO: Motor1]]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]]
[MSG:INFO: Y2 Neg Limit gpio.35]]
[MSG:INFO: Axis Z (-297.000,3.000)]]
[MSG:INFO: Motor0]]
[MSG:INFO: tmc_2209 UART1 Addr:2 CS:NO_PIN Step:I2SO.10 Dir:I2SO.9 Disable:I2SO.8 R:0.110]]
[MSG:INFO: Z Pos Limit gpio.32]]
[MSG:INFO: Motor1]]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.19 Step:I2SO.18 Dir:I2SO.17 Disable:I2SO.16 R:0.110]]
[MSG:INFO: Z2 Pos Limit gpio.34]]
[MSG:INFO: X Axis driver test passed]]
[MSG:INFO: Y Axis driver test passed]]
[MSG:INFO: Y2 Axis driver test passed]]
[MSG:INFO: Z Axis driver test passed]]
[MSG:INFO: Z2 Axis driver test passed]]
[MSG:INFO: Kinematic system: Cartesian]]
[MSG:INFO: Using spindle NoSpindle]]
[MSG:INFO: Flood coolant gpio.2]]
[MSG:INFO: Mist coolant gpio.16]]
[MSG:INFO: Probe gpio.36:low]]
[MSG:INFO: STA SSID is not set]]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]]
[MSG:INFO: AP started]]
[MSG:INFO: WiFi on]]
[MSG:INFO: Captive Portal Started]]
[MSG:INFO: HTTP started on port 80]]
[MSG:INFO: Telnet started on port 23]]
ok

No idea why that would not work, it all looks good.

Seems like you have had that board a while, might be worth updating it. Jackpot CNC Controller - V1 Engineering Documentation

The board is new, I received it three weeks ago. I got it from Elecrow (I’m in Europe).

I tried installing FluidNC version 3.9.1 and loading the V2 configuration with the macros, but none of the axes respond. Which version do you recommend?

Full erase, use 3.9.1 and if it is still funky. Power down and swap the drivers to see where the issues moves.

Hello again! I’m still not making any progress… When I try to update FluidNC to version 3.9.1, I get the following message: ‘Error: 500: WebSocket dead.’ Can anyone tell me what I might be doing wrong? How can I completely reset my Jackpot before reinstalling FluidNC?

Ok, that’s different from above where you’d loaded 3.9.1And macros. So can you confirm step by step what you’re doing when trying to update?

  • Are you using a known good USB cable that supports data - some are power only
  • Are you removing the esp32 board from the jackpot board or updating it in place
  • When you plug the esp32 into your computer does it appear as new hardware
  • Have you ever updated any esp32 or esp8266 devices, it not you might need the drivers installed
  • Are you using the web installer or another method

With the ESP32 on the Jackpot and disconnected from power, I connect the USB cable to my computer (Mac). Using the FluidNC web installer, I connect, select ‘Install’, and choose version 3.9.1 — the one that completely erases the existing version. Then I copy all the macros and files from the V2 folder and paste them. I restart and disconnect it from the computer."

When are you getting the websocket error?

When I connect the Jackpot to power and try to connect to the Wi-Fi through my computer using the FluidNC interface.

Did you unplug the USB cable before? I think it can’t be plugged in for that.

When you flash it can you ckick the ‘More Details’ drop down and post theinstall log? Should look something like this:

esptool.js
Serial port WebSerial VendorID 0x10c4 ProductID 0xea60
ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: Wi-Fi, BT, Dual Core, Coding Scheme None
Crystal is 40MHz
MAC: 30:ae:a4:1c:27:d8
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 10.531s
Compressed 3072 bytes to 129...
Writing at 0x8000... (100%)
Wrote 3072 bytes (129 compressed) at 0x8000 in 0.042 seconds.
Hash of data verified.
Warning: Image file at 0x1000 doesn't look like an image file, so not changing any flash settings.
Compressed 17568 bytes to 12205...
Writing at 0x1000... (100%)
Wrote 17568 bytes (12205 compressed) at 0x1000 in 1.241 seconds.
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0xe000... (100%)
Wrote 8192 bytes (47 compressed) at 0xe000 in 0.063 seconds.
Hash of data verified.
Compressed 1839728 bytes to 1097335...
Writing at 0x10000... (1%)
Writing at 0x19925... (2%)
Writing at 0x20f67... (4%)
Writing at 0x2b2d4... (5%)
Writing at 0x37424... (7%)
Writing at 0x41719... (8%)
Writing at 0x49ca6... (10%)
Writing at 0x548e8... (11%)
Writing at 0x68d94... (13%)
Writing at 0x7b74b... (14%)
Writing at 0x81076... (16%)
Writing at 0x870f1... (17%)
Writing at 0x8d156... (19%)
Writing at 0x92a49... (20%)
Writing at 0x98754... (22%)
Writing at 0x9ebd8... (23%)
Writing at 0xa55f9... (25%)
Writing at 0xab6f0... (26%)
Writing at 0xb16b1... (28%)
Writing at 0xb806d... (29%)
Writing at 0xbe3f5... (31%)
Writing at 0xc4922... (32%)
Writing at 0xcaafa... (34%)
Writing at 0xd01b0... (35%)
Writing at 0xd6010... (37%)
Writing at 0xdbebe... (38%)
Writing at 0xe17f4... (40%)
Writing at 0xe6f57... (41%)
Writing at 0xecc6b... (43%)
Writing at 0xf2084... (44%)
Writing at 0xf7356... (46%)
Writing at 0xfc7b5... (47%)
Writing at 0x101948... (49%)
Writing at 0x107296... (50%)
Writing at 0x10c468... (52%)
Writing at 0x11176a... (53%)
Writing at 0x116c48... (55%)
Writing at 0x11c1d2... (56%)
Writing at 0x1215b2... (58%)
Writing at 0x1266c9... (59%)
Writing at 0x12b941... (61%)
Writing at 0x13098c... (62%)
Writing at 0x135e39... (64%)
Writing at 0x13c0c7... (65%)
Writing at 0x1418c8... (67%)
Writing at 0x14696a... (68%)
Writing at 0x14be7f... (70%)
Writing at 0x1511b6... (71%)
Writing at 0x156594... (73%)
Writing at 0x15b9fe... (74%)
Writing at 0x161078... (76%)
Writing at 0x16690b... (77%)
Writing at 0x16c572... (79%)
Writing at 0x17204d... (80%)
Writing at 0x178cad... (82%)
Writing at 0x180298... (83%)
Writing at 0x189a56... (85%)
Writing at 0x190c80... (86%)
Writing at 0x19636d... (88%)
Writing at 0x19f342... (89%)
Writing at 0x1a55d4... (91%)
Writing at 0x1aeb92... (92%)
Writing at 0x1b5e5b... (94%)
Writing at 0x1bafc9... (95%)
Writing at 0x1c0e07... (97%)
Writing at 0x1c6259... (98%)
Writing at 0x1cb748... (100%)
Wrote 1839728 bytes (1097335 compressed) at 0x10000 in 98.164 seconds.
Hash of data verified.
Compressed 196608 bytes to 121018...
Writing at 0x3d0000... (12%)
Writing at 0x3d5e83... (25%)
Writing at 0x3d9e84... (37%)
Writing at 0x3dde7f... (50%)
Writing at 0x3f275f... (62%)
Writing at 0x3f6759... (75%)
Writing at 0x3fa754... (87%)
Writing at 0x3fe74f... (100%)
Wrote 196608 bytes (121018 compressed) at 0x3d0000 in 10.924 seconds.
Hash of data verified.
Leaving...
esptool.js
Serial port WebSerial VendorID 0x10c4 ProductID 0xea60
ESP32
Chip is ESP32-D0WD-V3 (revision 3)
Features: Wi-Fi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 20:43:a8:da:6b:88
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 2.889s
Compressed 3072 bytes to 129...
Writing at 0x8000... (100%)
Wrote 3072 bytes (129 compressed) at 0x8000 in 0.038 seconds.
Hash of data verified.
Warning: Image file at 0x1000 doesn't look like an image file, so not changing any flash settings.
Compressed 17568 bytes to 12205...
Writing at 0x1000... (100%)
Wrote 17568 bytes (12205 compressed) at 0x1000 in 1.318 seconds.
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0xe000... (100%)
Wrote 8192 bytes (47 compressed) at 0xe000 in 0.04 seconds.
Hash of data verified.
Compressed 1839728 bytes to 1097335...
Writing at 0x10000... (1%)
Writing at 0x19925... (2%)
Writing at 0x20f67... (4%)
Writing at 0x2b2d4... (5%)
Writing at 0x37424... (7%)
Writing at 0x41719... (8%)
Writing at 0x49ca6... (10%)
Writing at 0x548e8... (11%)
Writing at 0x68d94... (13%)
Writing at 0x7b74b... (14%)
Writing at 0x81076... (16%)
Writing at 0x870f1... (17%)
Writing at 0x8d156... (19%)
Writing at 0x92a49... (20%)
Writing at 0x98754... (22%)
Writing at 0x9ebd8... (23%)
Writing at 0xa55f9... (25%)
Writing at 0xab6f0... (26%)
Writing at 0xb16b1... (28%)
Writing at 0xb806d... (29%)
Writing at 0xbe3f5... (31%)
Writing at 0xc4922... (32%)
Writing at 0xcaafa... (34%)
Writing at 0xd01b0... (35%)
Writing at 0xd6010... (37%)
Writing at 0xdbebe... (38%)
Writing at 0xe17f4... (40%)
Writing at 0xe6f57... (41%)
Writing at 0xecc6b... (43%)
Writing at 0xf2084... (44%)
Writing at 0xf7356... (46%)
Writing at 0xfc7b5... (47%)
Writing at 0x101948... (49%)
Writing at 0x107296... (50%)
Writing at 0x10c468... (52%)
Writing at 0x11176a... (53%)
Writing at 0x116c48... (55%)
Writing at 0x11c1d2... (56%)
Writing at 0x1215b2... (58%)
Writing at 0x1266c9... (59%)
Writing at 0x12b941... (61%)
Writing at 0x13098c... (62%)
Writing at 0x135e39... (64%)
Writing at 0x13c0c7... (65%)
Writing at 0x1418c8... (67%)
Writing at 0x14696a... (68%)
Writing at 0x14be7f... (70%)
Writing at 0x1511b6... (71%)
Writing at 0x156594... (73%)
Writing at 0x15b9fe... (74%)
Writing at 0x161078... (76%)
Writing at 0x16690b... (77%)
Writing at 0x16c572... (79%)
Writing at 0x17204d... (80%)
Writing at 0x178cad... (82%)
Writing at 0x180298... (83%)
Writing at 0x189a56... (85%)
Writing at 0x190c80... (86%)
Writing at 0x19636d... (88%)
Writing at 0x19f342... (89%)
Writing at 0x1a55d4... (91%)
Writing at 0x1aeb92... (92%)
Writing at 0x1b5e5b... (94%)
Writing at 0x1bafc9... (95%)
Writing at 0x1c0e07... (97%)
Writing at 0x1c6259... (98%)
Writing at 0x1cb748... (100%)
Wrote 1839728 bytes (1097335 compressed) at 0x10000 in 99.278 seconds.
Hash of data verified.
Compressed 196608 bytes to 121018...
Writing at 0x3d0000... (12%)
Writing at 0x3d5e83... (25%)
Writing at 0x3d9e84... (37%)
Writing at 0x3dde7f... (50%)
Writing at 0x3f275f... (62%)
Writing at 0x3f6759... (75%)
Writing at 0x3fa754... (87%)
Writing at 0x3fe74f... (100%)
Wrote 196608 bytes (121018 compressed) at 0x3d0000 in 10.97 seconds.
Hash of data verified.
Leaving...

hi in webui V2 can you post a screenshot of the screen first?


on webui2 you need to: have any methotd of reporting selected first ( you wont get any movement if not)
then
clear any alarms and home the machine

Thank you for your suggestion. I tried selecting Auto and pressing the alarm button, but it still doesn’t respond. When I enter the $SS command, I get the same error message again: ‘Error: 500: WebSocket dead.’

The 500 error after you reverted to WebUI2 could be an instance of this problem that is mentioned in the release notes for the test release: "If you use WebUI3 and then go back to WebUI2, WebUI2 might not start correctly. If you have this problem, you can fix it by deleting the preferences.json file with $localfs/delete=preferences.json . The problem is caused by WebUI3 creating a new preferences.json that is in a format that WebUI2 does not understand."

This is from the fluidnc discord help forum
$localfs/delete=preferences.json

Try that and restart your controller

Also, are you using ap mode?

Suerte

Is your wifi re-connecting constantly?