Jump to content

I'm going round in circles!

TitusADuxass

By TitusADuxass
in General Discussion

 Share

Recommended Posts

TitusADuxass Mentor

TitusADuxass

Posted
Posted

My vz330 is driving me around the bend.

It keeps losing communication with either the MCU, the O2S or the Beacon.

I've had it switched on all day and have been regularly doing ls /dev/serial/by-id/ and getting this:
usb-Beacon_Beacon_RevH_FB12DEC35154354D38202020FF0A2308-if00  usb-Klipper_stm32f072xb_Orbitool_O2S-if00  usb-Klipper_stm32h723xx_080015000C51323532393433-if00

Everything is there and then I going to mainsail via a web browser (google chrome) and it gives me a communcation failure. This time it was the Beacon thatt lost comms.

But ls /dev/serial/by-id/ gave me this.

usb-Beacon_Beacon_RevH_FB12DEC35154354D38202020FF0A2308-if00

I've changed:

The Pi twice (from a BTT Pi2 to a Pi4 and then a Pi5.

I put a new SD card in and Kiauhed everything.

I've reflashed the Kraken and the O2S a number of times.

I've swapped out all the USB cables.

I am stuck!

The only thing that has changed with regard to my laptop and Wifi is that I now have a persistent VPN connection running on my laptop. But, I cannot see how that would have any connection to the issues that I'm having.

  • Like 1
Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
12 minutes ago, Penatr8tor said:

It could be the Orbitool USB connection to the Beacon. Maybe try running a cable from the Beacon to the Pi just to see if maybe that's the issue. 

That was my first thought. The Beacon has been running via a USB cable since I started chasing my arse round the room.

And, swapping the O2S for an O2 didn't solve it.

My v2.4 is running fine.

Link to comment
Share on other sites
Penatr8tor Grand Master

Penatr8tor

Posted
Posted

Hmmm... the only thing I can think of is maybe flash another SD card with 32 bit Pi OS. I know the RatOS has issues with 64 bit and since it's a fork of klipper they might have discovered something or not... just thinking out loud at this point.

  • Like 1
Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
1 minute ago, Penatr8tor said:

Hmmm... the only thing I can think of is maybe flash another SD card with 32 bit Pi OS. I know the RatOS has issues with 64 bit and since it's a fork of klipper they might have discovered something or not... just thinking out loud at this point.

I like your way of thinking. I'll give that a try.

  • Like 1
Link to comment
Share on other sites
NikosSprocket Proficient

NikosSprocket

Posted
Posted

I am not familiar with RatOS setups, but it's still debian linux. Buggy applications will create instabilities, but you were running the 64 bit before without any issues?

What changed in the system, since you started having problems?

Can you connect a keyboard and monitor to the Pi and watch live output/stream from the console and logs files ?

Using the Pi connected keyboard (USB) and looking at the HDMI connected monitor to the Pi, login, and then you can use the following command to "watch" live logs:

For Mainsail Pi distributions:

For system (debian) errors:

# journalctl -f

For klipper logs:

 $ tail -f ~/printer_data/logs/klippy.log

For nginx logs:

$ tail -f ~/printer_data/logs/mainsail-access.log

I do not know if RatOS it's using also nginx, but if does vpn installation is tricky as both protocols control network access, routing etc.

 

To break-out of the tail command, hit Ctrl-C.

  • Like 4
Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
11 hours ago, polyneutron said:

64 bit can be a real issue that has been documented. It is important to start with a lite version of raspberry pi image. Then shh in and install kiauh and then open kiauh to load kliper... it is also important to update v the system even before kiauh. This solved the dropping issues for me.

The only that I do differently is that I choose image that's built for 3D Printing.

Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
10 hours ago, NikosSprocket said:

I am not familiar with RatOS setups, but it's still debian linux. Buggy applications will create instabilities, but you were running the 64 bit before without any issues?

What changed in the system, since you started having problems?

Can you connect a keyboard and monitor to the Pi and watch live output/stream from the console and logs files ?

Using the Pi connected keyboard (USB) and looking at the HDMI connected monitor to the Pi, login, and then you can use the following command to "watch" live logs:

For Mainsail Pi distributions:

For system (debian) errors:

# journalctl -f

For klipper logs:

 $ tail -f ~/printer_data/logs/klippy.log

For nginx logs:

$ tail -f ~/printer_data/logs/mainsail-access.log

I do not know if RatOS it's using also nginx, but if does vpn installation is tricky as both protocols control network access, routing etc.

To break-out of the tail command, hit Ctrl-C.

Nikos, I'm not using RatOS.

Link to comment
Share on other sites
Huminio Newbie

Huminio

Posted
Posted (edited)

Anyway I think problem is in power supply to raspi. If it is too weak than usb devices can be randomly removed by falsely detected overdraw of current. 
There should be evidences in system logs for PSU under power and removal of usb devices. 
From my play with practically every generation of raspi I trust only genuine chargers. 

Edited by Huminio
  • Like 1
Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted

I am trying the 32 bit route. But it's a lot more of a nerdy install.

I am now stuck with a No module named 'numpy'

Klipper log gives this:  File "/home/p4/klipper/klippy/extras/beacon.py", line 21, in <module>
    import numpy as np ModuleNotFoundError: No module named 'numpy'

I've installed numpy via apt and followed a couple of threads that I found.

I had none of these issues with the 64 bit version.

 

...back to 64 bit for me with the 3D printer option and a new PSU for the Pi.

Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
14 minutes ago, polyneutron said:

I am using a voron 2.4 r2. I had drop outs at different times. I used esoteric can write up and on one of there start pages outlined issues wit raspberry 64. They provided a link with pi lite 64 image and after following this, I use it for every printer setup. 

Is it this - https://github.com/EricZimmerman/VoronTools/blob/main/OSUpgrade.md

Link to comment
Share on other sites
NikosSprocket Proficient

NikosSprocket

Posted
Posted

I checked your klippy.log and I show a couple of things that I am not sure if are significant:

1. I thought you are using Pi 5.

The log indicates Pi4:

 

 

Args: ['/home/p4/klipper/klippy/klippy.py', '/home/p4/printer_data/config/printer.cfg', '-l', '/home/p4/printer_data/logs/klippy.log', '-I', '/home/p4/printer_data/comms/klippy.serial', '-a', '/home/p4/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-433-gdc622f4ac-dirty'
Untracked files: klippy/extras/beacon.py
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git
CPU: 4 core ?
Device: Raspberry Pi 4 Model B Rev 1.5
Linux: Linux version 6.12.47+rpt-rpi-v8 ([email protected]) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
Python: '3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]'

This is from my 350 with the Pi5:

 

Starting Klippy...
Args: ['/home/b/klipper/klippy/klippy.py', '/home/b/printer_data/config/printer.cfg', '-l', '/home/b/printer_data/logs/klippy.log', '-I', '/home/b/printer_data/comms/klippy.serial', '-a', '/home/b/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-428-ga8cbc9355-dirty'
Untracked files: klippy/extras/led_effect.py
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git
CPU: 4 core ?
Device: Raspberry Pi 5 Model B Rev 1.0
Linux: Linux version 6.12.47+rpt-rpi-2712  (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
Python: '3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]'
Start printer at Sun Dec 21 13:51:06 2025 (1766353866.5 8.1)

 

 

 

I do not know how similar are the kernel's and libraries between Pi4 and Pi5; just my observations.

 

2. Beacon errors?

Near the bottom of the log there where 2 similar failures:

 

Receive: 97 174.977190 174.063137 18: seq: 1b, beacon_data samples=1 start_clock=1530051996 delta_clock=0 data=b'\x82\x8f\x96\x86'
Receive: 98 174.978793 174.977930 12: seq: 1c, shutdown clock=1530134236 static_string_id=Emergency stop
Receive: 99 174.978825 174.977951 8: seq: 1d, beacon_accel_state en=0 err=0

 

 

Link to comment
Share on other sites
mvdveer Grand Master

mvdveer

Posted
Posted
1 hour ago, NikosSprocket said:

I just put a reply, and it got flagged that needs approval!

What's that?

Got no idea. Your account profile has not changed and you are not flagged for moderation. ? Glitch in the system. Xmas gremlins, the grinch? Sorry about that. Let's see if it happens again. What you mind posting a reply so I can check

Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted
3 hours ago, NikosSprocket said:

I checked your klippy.log and I show a couple of things that I am not sure if are significant:

1. I thought you are using Pi 5.

The log indicates Pi4:

Args: ['/home/p4/klipper/klippy/klippy.py', '/home/p4/printer_data/config/printer.cfg', '-l', '/home/p4/printer_data/logs/klippy.log', '-I', '/home/p4/printer_data/comms/klippy.serial', '-a', '/home/p4/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-433-gdc622f4ac-dirty'
Untracked files: klippy/extras/beacon.py
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git
CPU: 4 core ?
Device: Raspberry Pi 4 Model B Rev 1.5
Linux: Linux version 6.12.47+rpt-rpi-v8 ([email protected]) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
Python: '3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]'

This is from my 350 with the Pi5:

Starting Klippy...
Args: ['/home/b/klipper/klippy/klippy.py', '/home/b/printer_data/config/printer.cfg', '-l', '/home/b/printer_data/logs/klippy.log', '-I', '/home/b/printer_data/comms/klippy.serial', '-a', '/home/b/printer_data/comms/klippy.sock']
Git version: 'v0.13.0-428-ga8cbc9355-dirty'
Untracked files: klippy/extras/led_effect.py
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper.git
CPU: 4 core ?
Device: Raspberry Pi 5 Model B Rev 1.0
Linux: Linux version 6.12.47+rpt-rpi-2712  (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
Python: '3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]'
Start printer at Sun Dec 21 13:51:06 2025 (1766353866.5 8.1)

I do not know how similar are the kernel's and libraries between Pi4 and Pi5; just my observations.

2. Beacon errors?

Near the bottom of the log there where 2 similar failures:

Receive: 97 174.977190 174.063137 18: seq: 1b, beacon_data samples=1 start_clock=1530051996 delta_clock=0 data=b'\x82\x8f\x96\x86'
Receive: 98 174.978793 174.977930 12: seq: 1c, shutdown clock=1530134236 static_string_id=Emergency stop
Receive: 99 174.978825 174.977951 8: seq: 1d, beacon_accel_state en=0 err=0

I'm now using a Pi4. But, I have also tried a Pi5.

Link to comment
Share on other sites
TitusADuxass Mentor

TitusADuxass

Posted
  • Author
Posted

So this moring's trials.

I'm running a Pi4 with 32 bit Debian Bookworm. The is running on it's own Pi approved Netzteil.

I've installed Klipper, Mainsail, Moonrake, etc. via KIAUH and ....

I still get the effing errors!!

  

Can not update MCU 'orbitoolO2S' config as it is shutdown

 

All three devices are displayed with lsusb & ls /dev/serial/by-id

p4@p4:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 006: ID 1d50:614e OpenMoko, Inc. stm32f072xb
Bus 001 Device 004: ID 1a86:8091 QinHeng Electronics USB HUB
Bus 001 Device 003: ID 1d50:614e OpenMoko, Inc. stm32h723xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
p4@p4:~ $ ls /dev/serial/by-id/
usb-Beacon_Beacon_RevH_FB12DEC35154354D38202020FF0A2308-if00  usb-Klipper_stm32f072xb_Orbitool_O2S-if00  usb-Klipper_stm32h723xx_080015000C51323532393433-if00
 

I went into both the priner.cfg and Orbitool_O2S.cfg and checked that the MCU identities were correct. All three match with what's displayed with ls /dev/serial/by-id

I overwrote the entries in printer.cfg and Orbitool_O2S.cfg and did a restart, it came on line!

I did a home and got error - No Beacon Model Loaded. I've encountered this error before. But, I can't remember the solution.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

×
×
  • Create New...