Fluid Dial (Fluid NC dial pendant by Bart Dring, using M5 Stack's M5 Dial)

Joebus · February 4, 2025, 8:54pm

Hi Doug! Coming back in after almost half a year. Trying to get everything fully updated (fluid.nc, jackpot, m5 dial). Out of 580 pages (wow) I’m not sure where to go to see the most updated info on installing M5 Dial firmware etc. Could you be so kind as to point me in the right direction!? Thank you,

Joe

DougJoseph · February 4, 2025, 9:07pm

The wiki for the FluidDial is best place to find concise details:

Joebus · February 6, 2025, 3:50pm

Thanks a bunch Doug.

I was able to update the firmware on the dial no issues but I get the dreaded “NC” now. The dial was working previously (until I updated fluid.nc).
-No wiring has changed.
-Changed baudrate in platformio.ini to 115200 prior to flashing firmware.
-Double checked config.yaml

uart1:
txd_pin: gpio.0
rxd_pin: gpio.4
rts_pin: NO_PIN
baud: 115200
mode: 8N1

uart2:
txd_pin: gpio.14
rxd_pin: gpio.13
rts_pin: NO_PIN
cts_pin: NO_PIN
baud: 115200
mode: 8N1

uart_channel2:
uart_num: 2
report_interval_ms: 75

Any ideas on what to look for next?

MakerJim · February 6, 2025, 3:52pm

That baud rate can’t be correct. It’s 1/10th of what it should be. Below is a section of one of my working machines’ config.yaml.

uart2:
  txd_pin: gpio.14
  rxd_pin: gpio.13
  rts_pin: NO_PIN
  cts_pin: NO_PIN
  baud: 1000000
  mode: 8N1
  
uart_channel2:
  uart_num: 2
  report_interval_ms: 75

Joebus · February 6, 2025, 3:57pm

Ok, good to know. Thank you.

I used that baud rate previously when it was working. This value was also based off of Dougs earlier post showing examples Fluid Dial (Fluid NC dial pendant by Bart Dring, using M5 Stack's M5 Dial) - #512 by DougJoseph.

I assumed as long as they match (M5Dial → Fluidnc) it would work.

I will try reverting firmware and config.yaml back to 1000000 baud

DougJoseph · February 6, 2025, 4:10pm

@MakerJim already pointed out the baud rate, but just to confirm, it is covered on the Wiki:

FluidNC Config Example

You can use any 2 pins on the ESP32 that are UART capable (most are)

The default baud rate is 1000000. It can be changed in platformio.ini in this statement

-DFNC_BAUD=1000000

It’s hard to catch everything — and you’re doing great.

DougJoseph · February 6, 2025, 4:12pm

Yes, but I think they changed the baud rate after I posted earlier work. They up’d it.

Joebus · February 6, 2025, 4:32pm

Thank you.

I reverted the firmware and updated the config.yaml to have baud: 1000000

Still NC So frustrating. I must have messed up something else like ESD damage or something. I’ll get another stamp in case I damaged mine.

DougJoseph · February 6, 2025, 4:39pm

How do you have your wiring done?

I think I read where you had it connecting previously?

Joebus · February 6, 2025, 4:44pm

I’ll have to pull the back off and take a photo. But it was working the day before yesterday before these updates. Nothing has changed with the wiring.

DougJoseph · February 6, 2025, 4:49pm

I hope you find that it was something simple. I’d hate if you found your dial had been bricked by discharge.

MakerJim · February 6, 2025, 4:56pm

Looking forward to the pictures.
Did you use Bart’s adapter set? Those incorporate some ESD protection, and they do report seeing ESD related issues for pendants connected without ESD protection.

Edit: Also, especially if you aren’t using Bart’s kit- avoid hot (powered) plugging and hot unplugging the pendant.

Joebus · February 6, 2025, 5:08pm

I’m not using any kit. Yellow is the gpio 13 and blue is gpio 14. Yellow is bottom left (pin 4) of “B” and blue is top right (pin1) of “A”. Hope this helps.

Britt · February 6, 2025, 5:16pm

I’m not sure where you got your wiring description from. This is what I used:

Joebus · February 6, 2025, 5:35pm

Doh, I didn’t double check my post before submitting. What I wrote above is incorrect. My wiring does infact look like yours. My A1 goes to gpio 13 and my A2 goes to gpio 14. I was really hoping that it was wrong because that would be a quick fix

Joebus · February 7, 2025, 3:13pm

@DougJoseph @MakerJim @Britt

It is working now. At some point the gpio RX and TX defenitions had swapped around on the jackpot from the last time I had used it.

Now I just see an issue on the probe menu. Any ideas? See pic:

Thanks again for your patience and help

DougJoseph · February 7, 2025, 4:41pm

I went through that also, if I remember right, it had something to do with changes from before an updated to after, and I posted on Discord to get advice on it, and I’m trying to remember what I eventually did. Not sure I can remember, but maybe it was wiping my dial back to factory condition, and redoing the firmware load from scratch?

DougJoseph · February 7, 2025, 4:44pm

Or maybe it was an “EraseAll.bat” or some such part of the file options provided in platformIO VSCode. ?

Britt · February 7, 2025, 5:04pm

What version of Fluidnc are you running?
I remember it happening to me also. I think, like Doug, that I had to erase the dial and reinstall the firmware and images.

Joebus · February 7, 2025, 5:12pm

V3.9.4
Agreed. I’m thinking this bit in the wiki will help me.