No serial logs after initialization?

Troubleshooting
1

Not sure if I’ve seen this bug reported yet… I can connect to my Maslow, move it around, calibrate it, etc. However some actions produce no serial logs whatsoever. Non-log producing actions include:

  • Running “Test” from the setup pane
  • Running a file, even to completion
  • Running a file and crashing due to an error

I do see logs when I initially connect to the Maslow:

Serial Messages
Index.html Version: 0.8
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v0.79 (Maslow-Main-7b9f3a44-dirty)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: 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: 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:speed_of_light]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting...]
[MSG:INFO: Connected - IP is 192.168.0.118]
[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]

Additionally, I see logs when calibrating (with fitness and such).

I just ran my first cut with the router on, and it failed after 20 minutes or so, I think it’s consistent with the ethernet/dust error, but I don’t have any logs to diagnose!

Thanks!
-Sam

1 Like
2

After turning it on today, I have logs again. Not sure what changed, I had previously power cycled with no effect.

I’ll report back if I experience this again.

1 Like
3

That’s very interesting. Is it possible that maybe multiple computers connected to the machine or something like that? I haven’t run across that before

4

only one computer connected. One thing peculiar about my setup is that I’m connecting via the local IP address and my network looks like:

maslow → 2.4ghz_ssid : 5ghz_ssid → laptop

however, now that I’m seeing logs I tried connecting on my laptop to both the 2.4ghz and 5ghz networks and it made no difference, saw them on both.

1 Like