Connectivity issues jackpot

I ran into some issues with fluidnc. I ordered a jackpot from elecrow and have an espressif wroom 32D. I flashed it to the latest 3.9.x release and installed webui v3. I can sometimes connect no problem but do get this screen:

If I press continue I get to the ui. I can jog my axis but after a little while the controller stops responding and seems to freeze. It also continuously spams a position message as can been seen. These issues happen on mobile and on my laptop

$SS gives no output. And the system often goes into hold state.

1 Like

Changed firmware to 3.8.17 and webui v2. This works.

1 Like

That is expected if it is in a Hold state. This screen will go away in the next release.

This is expected with status polling.

I’m not sure if that command would work while in a hold state.

This is the one that’s throwing me off. Were you running anything? Gcode, macros, manual commands? It should only go into hold if an M0 or feedhold command (!) is executed. If this is happening automatically, it almost sounds like there is a polling command setup running “!” instead of “?”.

I assume you mean 3.7.17. This version doesn’t have that hold screen.

1 Like

[quote=“Jason Yeager, post:3, topic:46365, username:jeyeager”]
This is the one that’s throwing me off. Were you running anything? Gcode, macros, manual commands?[/quote]

no not running anything, sometimes jogging but nothing else.

Yes sorry, ment 3.7.17. Wanted to see if downgrading it would work. It seemed to work.

However, I have a lot of trouble connecting and if it connects reliability is poor. While jogging it froze a number of times with error 6 and error 8. I have screenshots on my laptop which I can post if needed.

I also saw a warning of low memory come by, it says I have 4mb memory. I am starting to think something is wrong with my esp32. Ordered it from aliexpress, chip says it is espressif wroom 32d.

That’s FLASH, like hard drive.

RAM, you only have like ~500K, and typically run with ~100-ish free, maybe less in the 3.7.x series

I am assuming AP mode by the 192.168.0.0.1… How far from the machine are you? Do you have any wires or anything running over the top of the ESP32 that could be interfering with the signal?

Alarm 8 means the command requires an idle state, so that one is probably not concerning if you were doing something while in motion.

Alarm 6 is “Step pulse too short”, which, if you were getting this with 3.9.1, is more concerning since the stepping engine was rewritten in that release…

Any details you have about what caused it, or if you can find a way to reproduce it, would be a good thing to be able to report if we can.

1 Like

Ah thank you for explaining :slight_smile:

Yes, ap mode and have not changed the ip address. I am right besides the machine, maybe half a meter. Both with my phone and laptop

Some wires running above the esp.

The errors were in the old version so not in 3.9.1

This is known to cause connection problems.

You want to run those around the side as much as possible.

Nothing above the ESP antenna to interfere.

Nothing near the red X…

Follow the yellow. Down the side and underneath is better if possible

The wires over the heat sinks can also cause issue with overheating, or possible melting the insulation, please run the beside or under the board.

Oké thanks for the feedback! Will do a better job at cable managing tomorrow. I will update with the results

I redid the wiring, still having trouble getting a reliable connection. Also during homing this happens and gives alarm 6.

This happens on half of the homing attempts. No issues while running gcode.

$G
[MSG:WARN: Low memory: 13404 bytes]
[MSG:WARN: Low memory: 10888 bytes]
[MSG:WARN: Low memory: 7940 bytes]
[MSG:WARN: Low memory: 5496 bytes]
[MSG:WARN: Low memory: 5188 bytes]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
$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: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 (0.000,1220.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 (0.000,2440.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 (-300.000,0.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

I’m pretty surprised by this.

I haven’t seen low memory be an issue since the earlier 3.6.x series builds.

Is all of your config completely stock from Ryan’s github?

Yes completely stock, installed using the web installer and then the webui v2 version from Ryan’s GitHub. Did some cutting a few minutes ago. Two jobs without issue, one job froze for ten seconds and then continued. One completely froze and had to be power cycled.

Do you have any spare ESP32s to try?

I know wifi on the ESP32s can be power hungry and memory hungry.

I know there have also been previous reports of wifi connecting/disconnecting causing job pauses.

I’m wondering if there is an issue with your ESP32 causing shaky network issues and/or unstable power based on the behavior.

I’m also starting to think my current esp32 is faulty in some way. I don’t have a compatible esp32 laying around. I will order a new one from amazon, do you know a reputable brand/model I could order?

I use the V1 ESP32 from the shop with no issues.

I think @vicious1 used to have a link to one from Amazon in the docs…

Let me see if I can find it, or maybe if he sees this he can post a link

Edit:
Here it is: ESP32-DevKitC CP2102 - MicroUSB

Found here when you expand “Click here for full specifications”

1 Like

Before you buy another one try 3.9.1, it can help with multiple devices trying to log in at once. The only time I have seen that is when two devices are fighting to refresh.

I had 3.9.1 on it before. Had even more issues for me, it could not move the steppers at all. I will order the esp @Michael_Melancon mentioned.

Would this one also be fine? Amazon.nl

I ordered products from azdelivery before and worked well. Only this chip is wroom32 and not wroom32d. From what I read online 32d is newer?

Just noticed you said you got the Jackpot from Elecrow.

This means Ryan didn’t get it and pre-test it.

So it’s possible the motor issue could be something to do with the Jackpot itself or the drivers.

If you just want to try the ESP32 replacement as a first step, you can, but I’m not sure if that’s the best path forward.

It may take some more detailed troubleshooting to see if a hardware issue is potentially at play here.