FluidNC v3.9.3 (2024-12-17)

It was the friggin ESP32 chip!!! :grinning: I’m flashed with 3.9.3 and working just fine. Even ran a job just now. I have to admit I’m very surprised. Seems like a very strange way to fail.

On another note, how many different physical sizes of ESP32s are there exactly?? The way the pins were set up on this one, it wasn’t as wide. I had to spread pins on the chip outward and the connectors on the jackpot gently inward. It did work though. At this point, things work, so I really don’t care, but found it curious.


2 Likes

Great to hear!

I don’t know, I just know there’s more than one!

Hey all, did my first print and ended up with the following pretty quickly into the print.

Using 3.9.3 with UI3 and the newest v1 configs (FluidNC_Configs/MPCNC/UI V3 MPCNC at main Ā· V1EngineeringInc/FluidNC_Configs Ā· GitHub)

The machine is now frozen so sadly need to kill the job and restart everything…

[MSG:WARN: Low memory: 6336 bytes]

[MSG:WARN: Low memory: 4200 bytes]
[MSG:WARN: Low memory: 3448 bytes]
[MSG:WARN: Low memory: 3136 bytes]
[MSG:WARN: Low memory: 2936 bytes]
[MSG:WARN: Low memory: 2856 bytes]
[MSG:WARN: Low memory: 2364 bytes]

Many. There must be at least a dozen form factors I’ve encountered of ESP-32 dev boards.

That’s one of the known issues. It’s more common on the USB-C variants, but ESP-32 dev boards are made in the slightly wider form factor.

They also come with different USB/UART bridge chips sometimes, and there are multiple pin counts on the dev boards.

Yeah, ESP-32s go bad. ESD can kill them, so be aware of good practices when handling your system and in particular never plug or unplug ANYTHING in the system while it is on.

1 Like

It took a second to realize what you meant- ā€œjobā€ is the generic term for running code on a CNC machine.

What was happening when you get the errors quited below? Were you refreshing the WebUI or ??

This is unusual when using the newer builds.

Thanks, sorry print is my coming from the 3d print world. I was doing a job and had Chrome connected with the screen set to not shut off or machine sleep, so was just watching the print do it’s thing…

Also when I press abort this command is sent:

http://mpcnc.local/command?cmd=[ESP701]action%3DABORT&t=1734713515451

Then this is the result in the debugger:

Error: Invalid $ statement

So restarting will see if it happens again…

@ahbrown41 Which mode are you using for Wifi, AP or STA?

I’m running 3.9.3, and used ONLY the config.yaml from the UI V2 on GitHub. That works for me. I did not change the other files. Yet.

Tried again and the print worked. The abort button still has an error though…. Odd

1 Like

Wifi STA

1 Like

I’m not aware of an ESP701 abort command existing. Where are you seeing this? I usually do a feed hold followed by a soft reset.

http://wiki.fluidnc.com/en/features/commands_and_settings

1 Like

It doesn’t exist.

Likely is pressing the button under Streaming Commands, which is not supported by FluidNC

I will remove those soon

2 Likes