Error code wtih maslow.yaml

Troubleshooting
1

Hi all,

Going thru the set up process and I’m stalled on getting it calibrated. Keep getting fitness too low alerts. One thing that stands out as I go thru the log file is this:

“[MSG:ERR: Configuration file:maslow.yaml]”

I believe I have everything updated. Went thru that process twice. Any ideas?

Full startup serial log below. I can add log files fro my failed calibration attempts if that helps. Just trying to eliminate one issue at a time.

Thanks!
-Russell

Serial Messages
[MSG:INFO: Channel auto report interval set to 50 ms]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: FluidNC v0.75 (Maslow-Main-e2ef1bb2-dirty)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:ERR: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Config messages ran]
[MSG:INFO: Axis Y (-1219.200,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.110]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.110]
[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: Connecting to STA SSID:Hatchersons]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.0.122]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]

2

Russell Hatch wrote:

Going thru the set up process and I’m stalled on getting it calibrated. Keep getting fitness too low alerts. One thing that stands out as I go thru the log file is this:

“[MSG:ERR: Configuration file:maslow.yaml]”

when you updated, did you update all three files (firmware, index and yaml?)

I think that as long as it’s complaining about the yaml file, you need to
resolve that before worrying about anything else.

David Lang

3

Hey, I did upload all files. However I am unclear on whether I should have deleted the old index and yaml files first… I just uploaded the new versions expecting that it would overwrite the old.

4

I just went back to the previous week’s release (0.75). and the error code is now gone. I’ll update on the rest of the process when I have run some calibrations

5

It does overwrite automatically, but I’m also paranoid about that kind of thing, so I delete the files before uploading the new ones.

6

I’d assumed so but went through every way of uploading the current version I could come up with and got the same code.

If I get it fully calibrated on version .75 then I’ll make another go at .76

Thanks for the feedback all. Just glad to have resolved that err. message and on to the next step :slight_smile:

7

once you have a good calibration that you are happy with, you don’t need to do
another when you upgrade, just record the anchor positions (the Maslow_*
variables in the yaml file)

David Lang

8

I got an error message about corrupt Yaml file or something last night in the terminal, so I decided to re-upload the fresh .76 version with my calibration numbers. The deleted file was 5375 bytes, And the fresh one is 3418 bytes. I’m just wondering what causes the file size to change? Obviously there is some writing going on? Just curious so I can better understand how the file might corrupt?

9

there shouldn’t be anything else in there, that’s only supposed to be
configuration.

David Lang

10

Ok. So if the file size changes, Something is probably wrong…

11

Yes, I would suggest that if it does change, save a copy before you replace it
so we can see what happened.

We do know of a failure mode that will overwrite the file in a way that risks
actually damaging the machine (the Z steppers get very hot), I think a fix for
that is going in this week (if it didn’t get in last week)

anything else we need info to troubleshoot.

David Lang

12

This occurs because, as calibration is performed, a fresh ‘dump’ of the entire configuration is written back into the maslow.yaml file. This includes lots of FluidNC values which are not considered ‘important’ for the M4, but that are the ‘default’ for the corresponding setting in FluidNC.

It also occurs when you click ‘Save’ in the ‘Setup’/‘Config’ drop down.

13

I’ve just reread the code - and that specific error message is my bad. It should be a log_info not a log_config_error.

I’ll get a PR in for it shortly.

14

@bar - here’s the :pr: Fix log_config_error that should be log_info by md8n · Pull Request #137 · BarbourSmith/FluidNC (github.com)