FluidNC -> "pulse_us" ? [MSG:WARN] + getting WebUI v3 back!

Software / Firmware Jackpot Board / FluidNC
1

So, I thought would at least try out the latest version of FluidNC on my Jackpot-based LowRider v3.

Even though I’m using the same config.yaml as before, I’ve now been shown a warning message:

[MSG:WARN: Increasing stepping/pulse_us to the IS2 minimum value 4]

Screenshot 2024-06-21 at 9.01.53 PM
Screenshot 2024-06-21 at 9.01.53 PM1920×1394 201 KB

Here are the first few lines of config.yaml — notice the “pulse_us: 1” near the top.

board: Jackpot TMC2209
name: LowRider
meta: 10-30-2023 RyanZ; 11-20-2023 DougJoseph for swapped X and Y

planner_blocks: 32

stepping:
  engine: I2S_STATIC
  idle_ms: 255
  pulse_us: 1
  dir_delay_us: 1
  disable_delay_us: 0
  
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: 1000000
  mode: 8N1

uart_channel2:
  uart_num: 2
  report_interval_ms: 75

axes:
  shared_stepper_disable_pin: NO_PIN
          
  x:

What does “pulse_us:” do?

Can I safely just change it to 4?

Thanks for all help. :slight_smile:

2

It’s already set to 4 in my config.yaml:

board: Jackpot TMC2209
name: LowRider
meta: 03-15-2024 RyanZ
stepping: 
  engine: I2S_static
  idle_ms: 255
  pulse_us: 4
  dir_delay_us: 1
  disable_delay_us: 0
  segments: 12

It’s also set that way in all of Ryan’s default configs.
V1EngineeringInc/FluidNC_Configs: Configuration and support files for the FluidNC boards typically used and V1 Engineering (github.com)

2 Likes
3

OK, then I have no idea how I wound up with mine set to something else.

1 Like
4

Hey, while I am on this… After updating the FluidNC firmware, it is showing me the old version of WebUI. I uploaded the index.html.gz that came with v3.7.18, but no WebUI v3. I then overwrote it with the index.html.gz that I was using before, with WebUI v3 combined with your V1 theme, and it still shows me the old version of WebUI. I must be overlooking something, but I don’t know what. Any ideas?

5

Delete everything you have and use my V3 config to start. Then add a theme and you own config. V3 changes a lot

1 Like
6

I was using v3 successfully for a long time before this. Will most likely simply go back to what I was using before.

7

If you’re seeing V2, I’m assuming that either the index.html.gz didn’t actually upload, you need to refresh/restart after upload and/or you need a preferences.json. I think if things go really poorly, it defaults back to some basic UI that probably looks similar to V2.

I upgraded to v3.7.18 and it stayed on V3. However, I upgraded through PlatformIO since I built it for the extra memory on the V1 ESP32s.

1 Like
8

Clear your browser cache.

1 Like
9

This would make a lot of sense, except what would have been stuck in my browser cache would have been the WebUI v3 I was already using for the longest time.

10

I made sure to upload the preferences.json, and made sure to reboot. Several times.

11

This gave me success. I think the file I was forgetting was theme-FluidNC.gz

Thanks guys!!!

12

From the UI or actually power off and back on?

I would still try Ryan’s suggestion even though you used V3 before. Starting with a clean slate in the flash memory sounds like a good approach.

2 Likes
13

I see my post was a bit late. This is the theme Mike created so everything wasn’t purple. I doubt that was the issue unless your preferences.json referenced that file.

1 Like
14

Both, but mostly hard power off via physical switch.

15

I’m probably mistaken on the cause, but getting another fresh start seems to have gotten around it! :slight_smile:

16

Re. index.html.gz

Are copies from “/data” folder the WebUI v2, while copies from “/data3” folder are WebUI v3?

Filename Date File size Note?
index.html.gz 2024-01-02 111 KB from ?
index.html.gz 2024-03-20 83 KB part of Ryan’s config set for WebUI v3
index.html.gz 2024-06-21 117 KB recent from FluidNC github, but from /data folder
index.html.gz 2024-06-21 83 KB recent from FluidNC github, but from /data3 folder
17

Just a couple additional notes about my temporary foray into 3.7.18:

  1. It would let me save file changes via GUI to “preferences.json” for 2 or 3 times, then lose ability to save.

  2. The save button was totally missing from the V1 theme, but when I switched back to 3.7.17, it’s right there.

I’m back to 3.7.17 - and advising avoid 3.7.18.

18

Yes, that is correct. However, the currently recommended repo for WebUI v3 is Mike’s fork. Note that the v3 from the FluidNC repo hasn’t actually been updated in 5 months.

What do you mean by “lose ability to save”?

Which Save button are you talking about?

I’m not convinced this is actually a 3.7.18 issue at all. If you can upload the files you’ve been using, I’m curious to see if I can reproduce.

2 Likes
19

I would make a change, such as adding a macro, and press “Save” and it would not save, and instead give me warning message that “file could not be created” or some such. Over and over, even after reboot, etc.

20

For instance, in Settings, when editing macros etc, there is a save button at the bottom. It may be because I was not on Mike’s latest version of WebUI3. ?