Printer Model: Custom
MCU / Printerboard: Beaglebones Black & Cramps2.2
Hello!
I configure my Cramps2.2 with Beaglebone using this guide:
monoxide13/CRAMPS-and-Klipper: Device tree files for Beagle Bone Black CRAMPS (github.com)
…but no klippy.log is available and also /tmp/printer is not generate. how I can force the creation of /tmp/printer?
Thanks
At a guess the beaglebone black pru,s are not running, the beaglebone black images had/have a bad habit of change how the pru,s start or even breaking them without any documentation of what changes were made.
From memory when I had a BBB the last working image that worked was debian 9.3 but it was quite awhile ago and my memory is not as good as it use to be.
You are not following a official install so very difficult to give any info on a untested BBB image. according to the site you listed the author is using debian 10.3 , I can only presume it is working with the authors instructions so would suggest following them to the letter and if not working opening a issue on that git as instructed.
cheers
I would try the official install https://github.com/Klipper3d/klipper/blob/master/docs/Beaglebone.md
Config for cramps https://github.com/Klipper3d/klipper/blob/master/config/generic-cramps.cfg
Using Debian 10.3 the gcc-pru library conflict with gcc-avr library… I try using Debian official image, as you suggest.
Thank and have a nice day!
After a tons of problem with the libraries, now it is able to create the firmware for PRU unit, with /tmp/printer and klippy.log
Unfortunatly now I have this problem: klippy.log shows this error
mcu ‘mcu’: Unable to open port: [Errno 2] No such file or directory: ‘/dev/rpmsg_pru30’
In “install-beaglegone.sh” I found
sudo /bin/sh -c “cat > /etc/udev/rules.d/pru.rules” <<EOF
KERNEL==“rpmsg_pru30”, GROUP=“tty”, MODE=“0660”
EOF
and /dev/rpmsg_pru30 is present.
Thanks
The /dev/rpmsg_pru30 is the connection path between the BBB and the CRamps. It should be created by the above-mentioned UDEV Rule.
Have you rebooted the BBB?
I reinstalled all, and now it is present! Perhaps a passage was skipped. 
…But it doesn’t still works fine…klippy.log shows:
Extruder max_extrude_ratio=0.266081
mcu ‘mcu’: Starting connect
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.291283742, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.347082492, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.370023117, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.370077367, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.392622076, ‘#name’: ‘identify’, ‘#sent_time’: 7629.367879367, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7629.692320534, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7630.286250951, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7631.475133118, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 7633.847778409, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: Timeout on connect
mcu ‘mcu’: Wait for identify_response
Traceback (most recent call last):
File “/home/debian/klipper/klippy/serialhdl.py”, line 68, in _get_identify_data
params = self.send_with_response(msg, ‘identify_response’)
File “/home/debian/klipper/klippy/serialhdl.py”, line 261, in send_with_response
return src.get_response([cmd], self.default_cmd_queue)
File “/home/debian/klipper/klippy/serialhdl.py”, line 319, in get_response
cmd_queue)
File “/home/debian/klipper/klippy/serialhdl.py”, line 253, in raw_send_wait_ack
self._error(“Serial connection closed”)
File “/home/debian/klipper/klippy/serialhdl.py”, line 61, in _error
raise error(self.warn_prefix + (msg % params))
error: mcu ‘mcu’: Serial connection closed
Could you attach your klippy.log?
Good luck,hcet14
This is my klippy.log:
Starting Klippy…
Args: [‘/home/debian/klipper/klippy/klippy.py’, ‘/home/debian/printer.cfg’, ‘-l’, ‘/tmp/klippy.log’]
Git version: ‘v0.11.0-241-gffb5105b’
Branch: master
Remote: origin
Tracked URL: GitHub - Klipper3d/klipper: Klipper is a 3d-printer firmware
CPU: 1 core ARMv7 Processor rev 2 (v7l)
Python: ‘2.7.16 (default, May 23 2023, 14:13:27) \n[GCC 8.3.0]’
Start printer at Thu Jul 20 13:29:06 2023 (1689859746.1 1154.6)
===== Config file =====
[stepper_x]
step_pin = gpio0_23
dir_pin = gpio1_12
enable_pin = !gpio1_18
microsteps = 16
rotation_distance = 40
endstop_pin = ^gpio2_3
position_endstop = 0
position_max = 400
homing_speed = 50
[stepper_y]
step_pin = gpio1_15
dir_pin = gpio0_26
enable_pin = !gpio1_18
microsteps = 16
rotation_distance = 40
endstop_pin = ^gpio2_4
position_endstop = 0
position_max = 400
homing_speed = 50
[stepper_z]
step_pin = gpio0_22
dir_pin = gpio2_1
enable_pin = !gpio1_18
microsteps = 16
rotation_distance = 8
endstop_pin = ^gpio0_31
position_endstop = 0
position_max = 400
[extruder]
step_pin = gpio1_19
dir_pin = gpio1_28
enable_pin = !gpio1_18
microsteps = 16
rotation_distance = 33.500
nozzle_diameter = 0.400
filament_diameter = 1.750
heater_pin = gpio1_16
sensor_type = EPCOS 100K B57560G104F
pullup_resistor = 2000
sensor_pin = host:analog5
control = pid
pid_kp = 22.2
pid_ki = 1.08
pid_kd = 114
min_temp = 0
max_temp = 250
[heater_bed]
heater_pin = gpio1_13
sensor_type = EPCOS 100K B57560G104F
pullup_resistor = 2000
sensor_pin = host:analog4
control = watermark
min_temp = 0
max_temp = 130
[fan]
pin = gpio0_20
[mcu]
serial = /dev/rpmsg_pru30
[mcu host]
serial = /tmp/klipper_host_mcu
[printer]
kinematics = corexy
max_velocity = 300
max_accel = 3000
max_z_velocity = 5
max_z_accel = 100
Extruder max_extrude_ratio=0.266081
mcu ‘mcu’: Starting connect
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.203610804, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.259237012, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.290290596, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.292337054, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.394626554, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.595089179, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1155.994936346, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Got error -1 in tcflush: (25)Inappropriate ioctl for device
mcu ‘mcu’: got {‘count’: 40, ‘#receive_time’: 1156.796343887, ‘#name’: ‘identify’, ‘#sent_time’: 0.0, ‘offset’: 0}
Please put such long logs or code listings into preformatted text tags:
This makes it easier to read and does not consume sp much space.
That’s not “attaching” your klippy.log
Please “Reply” and drag the file in so it gets loaded into the post.
Excuse me…Now i hope it’s correct
klippy (1).log (3.1 KB)
Hi,
still want to try out BeagleBone and CRAMPS ?
i just finished upgrading it to latest image…
more details in this topic: