rat-os / ratos Goto Github PK

Is your feature request related to a problem? Please describe

Is not a problem just a request.

Describe the solution you'd like

Add a variable to change the preheat temperature for the extruder.

Describe alternatives you've considered

No response

Additional information

I'd like to be able to set different temperatures to speed up the start process.

Hi

I tried using the https://github.com/Rat-OS/RatOS/blob/master/site/docs/guides/4028.md documentation to add a 4028 parts fan to my VC3 printer featuring an Octopus 1.1 board. But I got hung up on the text "... PWM wire is fed a 5V PWM signal from the board ..." combined with the image (showing a suggested wiring for an Octopus board) having the voltage selection jump for the Fan port set for 24V.

On discord the community member Indymusician helped me get my bearings in this discussion - https://discord.com/channels/582187371529764864/816478223361245204/1015282861227655309

I hope the text and image can be adjusted to better describe how to implement the 4028 fan, but regardless thank you very much for the guide which was really helpful!

For ratos2 alpha there is no config file made on clean installation. Maybe a semi-preconfigure crowsnest file should be made and parts that need to be configure commented out and let user know.

Or a message when adding a camera, so users know that they must add a crowsnest config file.

What happened

In the file /etc/network/interfaces should be a statement that sources the files that are in /etc/network/interfaces.d. This is missing which caused me issues when trying to setup the can0 interface. In the file /etc/network/interfaces there should be something like this:

# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*

What did you expect to happen

The include is typically in the interface file, perhaps not in the base image that is used.

How to reproduce

Add a can0 interface and it will never show up until the file is sourced.

Additional information

No response

Change /etc/init.d/ratos (or wherever else seems sensible) to create a symlink from /tmp/klippy.log to /home/pi/klipper_logs/klippy.log so people can find the log file.

start)
echo "$(date +"%Y-%m-%d %T"): Updating RatOS" >> "$logfile"
if [ -e /tmp/printer ]; then
curl http://localhost:7125/printer/restart -X POST
fi
ln -fs /home/pi/klipper_logs/klippy.log /tmp/klippy.log
;;

• Explain flashing
• Explain configuration in the bottom of printer.cfg
• Explain ADXL345 chip names

Good morning, what is the difference between these 2 versions:

RatOS-v2.0.0-beta1.5-bullseye-arm64-lite.img.xz

RatOS-v2.0.0-beta1.5-bullseye-armhf-lite.img.xz

Which one should I use?

Using the PSK is great, enables you to store the password in a secure way
But the the clear txt password is saved as a comment in the file

It can be deleted

Hello Fellows,
this Issue is only to show up an error in your README.md.

If you follow the manual way you couldnt produce a usable Image, because "latest" is bullseye.
but since it is a fork of another project, similar to yours, the whole build chain is optimized to use "buster" Images as source.

See

Regards and Merry Christmas ( soon ) ;)

What happened

WiFi IP address and network are fixed to 192.168.50.1 and can't be changed.

What did you expect to happen

It should log into my WiFi and obtain an IP address from my DHCP server.

How to reproduce

Go through the normal setup

Additional information

No response

Hello,

After installing completely latest version and following installation documentation from:
https://os.ratrig.com/docs/installation

the software became unusable, return errors on ("permission errors") almost on each request.

sudo journalctl -xe -u moonraker

Jun 26 07:31:23 RatRig python[667]: [file_manager.py:get_file_list()] - Updating
Jun 26 07:31:23 RatRig python[667]: [app.py:log_request()] - 404 GET /machine/de
Jun 26 07:31:23 RatRig python[667]: [web.py:log_exception()] - 401 GET /websocke
Jun 26 07:31:23 RatRig python[667]: [app.py:log_request()] - 401 GET /websocket
Jun 26 07:31:23 RatRig python[667]: [file_manager.py:get_file_list()] - Updating
Jun 26 07:31:24 RatRig python[667]: [web.py:log_exception()] - 401 GET /websocke
Jun 26 07:31:24 RatRig python[667]: [app.py:log_request()] - 401 GET /websocket
.
.
.
Jun 26 07:49:32 RatRig python[667]: [web.py:log_exception()] - 401 GET /websocket (2a10:800e:19bd:0:7167:d4c9:a326:9cd5): Unauthorized
Jun 26 07:49:32 RatRig python[667]: [app.py:log_request()] - 401 GET /websocket (2a10:800e:19bd:0:7167:d4c9:a326:9cd5) [No User] 23.17ms
Jun 26 07:49:33 RatRig python[667]: [web.py:log_exception()] - 401 GET /websocket (2a10:800e:19bd:0:7167:d4c9:a326:9cd5): Unauthorized
Jun 26 07:49:33 RatRig python[667]: [app.py:log_request()] - 401 GET /websocket (2a10:800e:19bd:0:7167:d4c9:a326:9cd5) [No User] 21.05ms

To reproduce:
just take new sdcard and write Ver1.2.2

Hey guys,

I would request a change to the start_print macro to only do a home or z_tilt_adjust if it wasn't done before.
Those features were added to klipper months ago and they are realy nice to have if you do one print after an other.

In my case I got a macro called "ABL" for AutoBedLeveling that is doning the following stuff:

[gcode_macro ABL]
gcode:
    {% set axismin = printer.toolhead.axis_minimum %}
    {% set axismax = printer.toolhead.axis_maximum %}

    M118 Autobedleveling is started

    {% if not printer.z_tilt.applied %}
        Z_TILT_ADJUST         #Level Gantry
    {% endif %}

    BED_MESH_CALIBRATE

[gcode_macro BED_MESH_CALIBRATE]
rename_existing: BASE_BED_MESH_CALIBRATE
gcode:
    {% if printer.toolhead.homed_axes != 'xyz' %}
        M118 Homing the printer
		G28                   #Home All Axes
    {% else %}
        M118 Already homed
    {% endif %}

    G90
    G1 X5 Y-10 Z5 F6000
    M118 Calibrating the bed
    BASE_BED_MESH_CALIBRATE

[gcode_macro Z_TILT_ADJUST]
rename_existing: BASE_Z_TILT_ADJUST
gcode:
    {% if printer.toolhead.homed_axes != 'xyz' %}
        M118 Homing the printer
		G28                   #Home All Axes
    {% else %}
        M118 Already homed
    {% endif %}
   
    G90
    G1 X5 Y150 Z5 F6000
    M118 Adjusting the Z-Tilt
    BASE_Z_TILT_ADJUST

to be able to use M118 I had added this to printer.cfg (that messages are printed at the top on klipperscreeen as well during anything):

[respond]
default_type: echo

What happened

If I make the setting for motor performance in the printer.cfg for a v-core 3, I get an error.
File contains no section headers.
file: '/home/pi/printer_data/config/printer.cfg', line: 1
'[in'
have three of the same printer on all three the same.

What did you expect to happen

that the config works

How to reproduce

just set it up and restart

Additional information

No response

Some users have detachable accelerometers that mount directly to the printer's hotend. Depending on the setup, this can end up closer to the bed than the ABL probe on the carriage, causing a crash if the printer homes after installing the accelerometer.

Currently, even if you have homed the printer beforehand and the printhead's location is known, the printer will still home all axes when the GENERATE_SHAPER_GRAPHS command is run, potentially causing a crash or cable snag.

This is not urgent, but would be a nice change when time allows.

Hi, so we are having a discussion on Discord that the mesh generated by the ABL and incorrectly translated points while printing the very first layer.
Our finding is that while the mesh creation looks ok, when printing first layer it does not compensate the way it should.

I have marked two corned with number 1 and 2

Now when you look at the actual print of the first layer you can tell that the point 1 is printed way too low, while it should be compensated by the mesh and printed a little higher.

Then when you look at the point 2, it is printed way too high, while it should be compensated and printed a little lower to stick to the bed.

The mesh is not correctly applied when printing the first player. Specifically saying it looks like the mesh compensation is flipped or rotated.

In the end i have made a final test to prove it's the MESH issue:
I have completely disabled the mesh (removed it) and printed the first layer only relaying in bed 3 point tilt calibration. The result was outstanding, the first layer looked very good and smooth.
This test confirmed me in my opinion that there is a bug in the mesh translation and this needs investigation.
As from now, i am not using ABL MESH as it makes more harm then helps.
I am not only one person who experience this and we started discussion on RatRig Discord: https://discord.com/channels/582187371529764864/943964352216715315

Please understand: I am not a programmer so please forgive my bad explanation but hopefully this will be picked up by the DEVS and resolved ASAP.

Thanks!
Tom

MEASURE_COREXY_BELT_TENSION command does not generate the graphs in the input shaper directory,

07:09:45 Command {generate_belt_tension_graph} finished
07:09:11 Running Command {generate_belt_tension_graph}...:
07:09:11 Writing raw accelerometer data to /tmp/raw_data_axis=1.000,-1.000_belt-tension-lower.csv file
07:09:09 Re-enabled [input_shaper]

klipper v0.10.0-610-g0d9b2cc1
KlipperScreen v0.2.7-11-g1332045
RatOS v1.2.4-0-gfdfda1d
RatOSTheme v1.2.0-1-g692057f
moonraker v0.7.1-741-g379bcb1
ratos-configurator deployment: v0.1.0-4-ge2bbb14
mainsail v2.3.1

If you download version 1.2.4 and generate a new installation, you get a lot of messages, that your system is outdated.

If you try "update all components" it won't be usable.
If you try to "update system components" the update also stops with an error.

Hi,
I noticed that the Octopus Pro docs show the wrong board (Octopus 1.1) for both models.

This becomes clear when you look at the BLTouch/Inductive Probe connection, which is shown as being on the top right, while BTTs original documentation for the Octopus Pro shows it like this:

This could lead to confusion and should be fixed in a future release.

This will allow more displays to be used as there are more supported in the latest version. In-place upgrades break the installation.

I believe RatOS could use a minor correction with z_tilt. In the 500.cfg the z_tilt z_positions were:
0,0
250,500
500,0
I believe these should be the center positions of the pivoting balls on the bed, so if my measurements and math is correct (pls verify) I believe they should be:
-0.5,-0.75
250,500.75
500.5,0.75
I didn't run any math to know how much of an effect this actually has, but I can say after modifying this I don't think I've seen z_tilt run more than 2 times.

VMinion with SKR2 429.

I've tried 3 times to install but after the configuration, Klipper reports an error "mcu unable to connect".

klippy.log has mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-skrat-10: [Errno 2] No such file or directory: '/dev/btt-skrat-10'
moonraker.log has "utils.ServerError: Access to .git folders is forbidden"

Firmware is current.

Updating beyond this point results in a newer firmware but the errors persist.

Hi!

I noticed, that the current values for the z steppers in config/printers/v-core-3/tmc2209.cfg are different. Z and z2 are set to 1.0 while Z1 is set to 1.1.
I guess they should all be the same. Not sure if it makes much of a difference, but thought I mention it all the same.

devlink rule works to map octoprint pro 446 to /dev/btt-octopus-pro-446, but the mcu serial device was still listed as /dev/btt-octopus-11 in config/boards/btt-octopus-pro-446/config.cfg.

thanks for putting this together!

As the title says Balena etcher expects an image not a .zip file. I think you should fix the website instructions or fix the zip file. (zip file is about 33mb)

RASPBERRY PI INSTALLATION
Download the newest release (download the RatOS-*.zip file under the assets dropdown) of [RatOS on github](https://github.com/Rat-Os/RatOS/releases). Then use [Balena Etcher](https://www.balena.io/etcher/) to write that image to the SD card that goes into your raspberry pi (8GB or larger).

Note: this will destroy all data on the card!

Reference on Balena Etcher (balena-io/etcher#1249)

Small suggestion to remove the single mains wire after the SSR to not confuse Users why its there in the MCU wiring diagram.
Additional suggestion to add DC side +/- marking as not everybody knows about the hole being DC side.

We have now reached beta! Go to https://github.com/Rat-OS/RatOS/releases/tag/v2.0.0-beta1 to download the beta release and flash it to your Pi's SD card. You cannot upgrade from alpha to beta without reflashing.

If you're already on RatOS v2.0.0 beta, you can ignore this message.

Thank you for testing!

Updating KlipperScreen currently causes a bunch of critical packages to be removed and thus break klipper and moonraker as a result. I'm investigating, and will update you as soon as i know more.

This release will not be backwards compatible with v1.x. https://github.com/Rat-OS/RatOS-configuration and https://github.com/Rat-OS/RatOS-configurator will get a v2.x branch which they'll be deployed from.

v1.x will continue to get moonraker/klipper compatibility fixes for 3 months from the release of v2.0, that should be enough time for users to migrate. From that point, v1.x will have reached end of life. Users can still stay on v1.x but will either have to mantain it themselves or stop updating.

TODO:

• MCU wizard
• SKR 3 EZ support
• Resolve toolboard ADXL345 conflict with main control board.
• Manta M4P support (Rat-OS/RatOS-configuration#83 needs minor modifications)
• Voron 2.4 support (Rat-OS/RatOS-configuration#87)
• printer.cfg install macro for Voron V2.4
• Clean up stepper and driver configuration (get rid of backwards compat).
• DFU instructions in board-definition.json for all toolboards
• Ability to use sensorless and physical endstops simultaneously (PR needs minor work).
• Move flashing of connected boards to configurator
• Add configurator endpoints for registering klippy extras that should be symlinked
• Handle klippy extension symlinking via configurator in install and update scripts
• Disable IPv6 in avahi and nginx
• MainsailOS merge
• Docs on all the new macro variables.
• Wiring diagrams for BTT EBB toolboards
• Wiring diagrams for FLY SHT toolboards
• Clear up toolboards power wiring, show the plug
• Wiring diagram for Manta M8P
• Fan wiring diagram for Manta M8P
• Wiring diagram for Manta M4P
• Fan wiring diagram for Manta M4P
• Wiring diagram for SKR 3
• Wiring diagram for SKR 3 EZ
• Wiring diagram for Mini E3 3.0 (WIP)
• Docs rewrite, since MCU's are now flashed through the wizard
• Docs for BTT EBB toolboards
• Docs for FLY SHT toolboards
• Docs for Manta M8P
• Docs for Manta M4P
• Docs for SKR 3
• Docs for SKR 3 EZ
• Moonlight for notifications
• Short documentation for Voron V0.1 similar to the existing printer docs
• Short documentation for Voron V2.4 similar to the existing printer docs
• #42
• Docs on how to use stowable probes (basically an include and some position fiddling via a couple of variables).

nice to haves - may be moved to 2.1

• Preinstalled and configured crowsnest and timelapse (comes with the MainsailOS merge)
• DFU instructions in board-definition.json for control boards
• Configurator support for selecting and sequentially flashing multiple control boards and multiple toolboards. Currently multiple boards can be flashed by jumping back and forth in the wizard, which is meh.
• Hevo support (Rat-OS/RatOS-configuration#74).

Hello Mikkel,

My name is Alexander. I guess I am the "PR-Manager" (:D) of the telegram bot.
In the last couple of weeks we are being contacted by users of your image, which install our bot, and then the image considers itself "compromised" in your terms.

I think the amount of bot and RatOS users is only going to increase in the future, so we would like to integrate the bot properly, instead of doing half-baked attempts at evading your integrity checks.

We don't see any issues with you providing our bot in the way you find most useful/clean, maybe directly through your installer.
Let's get together and discuss the possibilities. Should I reach out to you via mail to give you my Telegram/Discord contact data?

Best regards,
Alexander

no Can Bus support for this image

... config.txt for SPI RPI CAN HAT. not working
dtoverlay=mcp2515-can0,oscillator=12000000,interrupt=25,spimaxfrequency=2000000

if i boot with raspi lite it works fine
i need this support for BIQU HermitCrabCan for VCORE 3

What happened

There is an inherent problem when using a system that can only add or replace values, as you can't remove a key-value pair once introduced. This means that for every option that requires you to use a different key-value pair, you need to double the number of includes. This becomes unwieldly, is impossible to manage, and is impossible for users to use.

With your current configuration it is completely impossible to use CAN, as the baud and serial keys under [mcu] will cause Klipper to fail. This is just 1 of many situations that I ran into while attempting to use RatOS. In the end I had to stop using your templates entirely, and instead copy and paste the required sections into the printer.cfg file, which is not a good option.

What did you expect to happen

This should be easier to manage. The only possible way for this to work would require that Klipper provides an option for removing key-value pairs from the configuration after they've been defined.

How to reproduce

(see What happened)

Additional information

No response

The simple solution is to just add scan_ssid=1

More complex solution is to also add support in the wizard
But I got by with changing it to visible for the wizard and then hide it again

Running the latest Rat-OS.

klipper
v0.11.0-92-g4cd5e9d2
KlipperScreen
v0.3.1-17-g059f1a8
RatOS
v1.2.4-1-ge155499
RatOSTheme
v1.2.0-1-g692057f
moonraker
v0.7.1-831-g61d3182
ratos-configurator
deployment: v0.1.0-6-g05d0ba5
mainsail
v2.4.1
System
OS-Packages

Home All works. BLTouch operates as expected. Z Tilt keeps failing with the BLTouch probe failing to deploy at the first calibration point and a subsequent head crash.

If one has used SET_CENTER_KINEMATIC_POSITION, MAYBE_HOME 'believes' everything is homed when it isn't; which can result in a nozzle/bed crash.

SET_CENTER_KINEMATIC_POSITION should set a RatOS variable to tell MAYBE_HOME that it needs to do a proper homing run.

Hi

I may have an issue with the DEPLOY_PROBE macro in RatOS2.
I am trying to implement a servo wich is bringing my probe into the bed area, the servo works fine, converted it from the brushing tool by the voron guys.
I do a homing in X and Y and and then i try to do a home Z, inside my home Z is the order to deploy the arm into the buildarea, the arm deploys fine but the hotend never reaches the dock position. Using this to drive the arm: SET_SERVO SERVO=wipeServo ANGLE=134 connected on the Neopixel-port.
The whole position is offset by 30mm in X and Y wich means if i drive to X=0 or Y=0 it could crash into the endstops and on the other side it stops 30mm before the endstop and says max_position.
Even if i put in a home-X Y after i deploy the arm it acts still the same, it could not reach it and offsets the position.
Some klipper cracks looked over it but could also not help to solve this, so may it is an issue in RatOS

Thanks in advance

Is your feature request related to a problem? Please describe

With support for the Vorons, there should be support for the Revo Voron hotend.

Describe the solution you'd like

Addition of a hotend option for the Revo Voron

Describe alternatives you've considered

No response

Additional information

No response

What happened

Running http://ratos.local/configure, where I select my MCU as btt-octopus-pro-429, but in printer.cfg the following is selected

[include RatOS/boards/btt-octopus-11/config.cfg]
instead of
#[include RatOS/boards/btt-octopus-pro-429/config.cfg]

And Mainsail repports that

Klipper reports: ERROR
mcu 'mcu': Unable to connect
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer

In the klipper log it reopports
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'

What did you expect to happen

I expecteded it to select [include RatOS/boards/btt-octopus-pro-429/config.cfg]

How to reproduce

Clean setup with new image using "2023-02-12-RatOS-v2.0.0-beta2-raspberry-rpi64.img"
Perform setup for BTT Octopus Pro V1.1

Additional information

No response

I'm using the primeblob for start gcode without any changes and I get an error from time to time about an unhandled exception.

Stats 525740.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6312248 bytes_read=1159062 bytes_retransmit=9 bytes_invalid=0 send_seq=151190 receive_seq=151190 retransmit_seq=2 srtt=0.001 rttvar=0.001 rto=0.025 ready_bytes=0 stalled_bytes=0 freq=179999926 Octopus: temp=34.7 raspberry_pi: temp=33.1 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.09 cputime=27525.155 memavail=3384124 print_time=828.586 buffer_time=2.709 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
b'Got EOF when reading from device'
Stats 525741.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6313486 bytes_read=1159260 bytes_retransmit=1303 bytes_invalid=0 send_seq=151220 receive_seq=151208 retransmit_seq=151220 srtt=0.001 rttvar=0.001 rto=0.200 ready_bytes=54 stalled_bytes=96 freq=179999929 Octopus: temp=34.7 raspberry_pi: temp=33.6 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.09 cputime=27525.301 memavail=3383920 print_time=830.128 buffer_time=3.251 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
Stats 525742.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6313486 bytes_read=1159260 bytes_retransmit=1303 bytes_invalid=0 send_seq=151220 receive_seq=151208 retransmit_seq=151220 srtt=0.001 rttvar=0.001 rto=0.200 ready_bytes=54 stalled_bytes=97 freq=179999929 Octopus: temp=34.7 raspberry_pi: temp=34.6 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.09 cputime=27525.432 memavail=3383928 print_time=830.128 buffer_time=2.250 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
Stats 525743.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6313486 bytes_read=1159260 bytes_retransmit=1303 bytes_invalid=0 send_seq=151220 receive_seq=151208 retransmit_seq=151220 srtt=0.001 rttvar=0.001 rto=0.200 ready_bytes=54 stalled_bytes=242 freq=179999929 Octopus: temp=34.7 raspberry_pi: temp=32.6 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.08 cputime=27525.597 memavail=3383928 print_time=831.671 buffer_time=2.792 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
Stats 525744.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6313486 bytes_read=1159260 bytes_retransmit=1303 bytes_invalid=0 send_seq=151220 receive_seq=151208 retransmit_seq=151220 srtt=0.001 rttvar=0.001 rto=0.200 ready_bytes=54 stalled_bytes=387 freq=179999929 Octopus: temp=34.7 raspberry_pi: temp=33.1 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.08 cputime=27525.758 memavail=3383928 print_time=833.214 buffer_time=3.334 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
Stats 525745.0: gcodein=0  mcu: mcu_awake=0.295 mcu_task_avg=0.000137 mcu_task_stddev=0.000000 bytes_write=6313486 bytes_read=1159260 bytes_retransmit=1303 bytes_invalid=0 send_seq=151220 receive_seq=151208 retransmit_seq=151220 srtt=0.001 rttvar=0.001 rto=0.200 ready_bytes=54 stalled_bytes=388 freq=179999929 Octopus: temp=34.7 raspberry_pi: temp=32.6 sd_pos=43709 heater_bed: target=68 temp=68.3 pwm=0.039 sysload=1.08 cputime=27525.919 memavail=3384124 print_time=833.214 buffer_time=2.333 print_stall=0 extruder: target=215 temp=214.9 pwm=0.248
Unhandled exception during run
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/klippy.py", line 217, in run
    self.reactor.run()
  File "/home/pi/klipper/klippy/reactor.py", line 292, in run
    g_next.switch()
  File "/home/pi/klipper/klippy/reactor.py", line 340, in _dispatch_loop
    timeout = self._check_timers(eventtime, busy)
  File "/home/pi/klipper/klippy/reactor.py", line 163, in _check_timers
    self._next_timer = min(self._next_timer, waketime)
RecursionError: maximum recursion depth exceeded in comparison
Transition to shutdown state: Unhandled exception during run
Dumping gcode input 0 blocks
Dumping 20 requests for client 3045709136

On a restart attempt I can find something like this:

[Kugel_Kugelhalter_0.2mm_PLA_11m.zip](https://github.com/Rat-OS/RatOS/files/10097780/Kugel_Kugelhalter_0.2mm_PLA_11m.zip)

mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
webhooks client 3037072720: New connection
webhooks client 3037072720: Client info {'program': 'Moonraker', 'version': 'v0.7.1-775-gb67a08a'}

Because it is not finding any serialboard then, I tryed a bit in the shell of my raspberry pi:

root@vcore3:~# ls /dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00
/dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00
root@vcore3:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1d50:614e OpenMoko, Inc.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

That is looking absolutly ok for me. So now I'm a bit lost on how to find the problem. I will open a 2nd issue on klipper repo because I think it is not RatOS 2.0 related, isn't it?

EDIT: I tryed to reslice my file and then it was printing. Maybe something related to prusaslicer then.... mhhhh

18:40:56
echo: Firmware binaries compiled successfully! You can find them in the firmware_binaries folder in the machine tab!
18:40:56
Command {compile_binaries} finished
18:40:56
cp: cannot create regular file '/home/pi/klipper_config/firmware_binaries/firmware-btt-octopus-pro-446.bin': Permission denied

if you delete the files before than it works

Checking the logs on ROS I noticed that I have 2 files of 16G each.

pi@ratos:~ $ ll -h /var/log/
total 32G
-rw-r--r-- 1 root root 5.7K Aug 14 18:07 Xorg.0.log
-rw-r--r-- 1 root root 5.7K Aug 14 18:07 Xorg.0.log.old
-rw-r--r-- 1 root root    0 Sep  1 00:00 alternatives.log
-rw-r--r-- 1 root root  21K Aug  4 21:57 alternatives.log.1
drwxr-xr-x 2 root root 4.0K Oct  1 00:00 apt
-rw-r----- 1 root adm  579K Nov  8 09:55 auth.log
-rw-r--r-- 1 root root    0 Jan 28  2022 bootstrap.log
-rw-rw---- 1 root utmp    0 Nov  1 00:00 btmp
-rw-rw---- 1 root utmp    0 Oct  1 00:00 btmp.1
-rw-r----- 1 root adm   16G Nov  8 10:03 daemon.log
-rw-r----- 1 root adm   49K Nov  3 12:57 debug
-rw-r--r-- 1 root root    0 Oct  1 00:00 dpkg.log
-rw-r--r-- 1 root root  22K Sep 18 18:30 dpkg.log.1
-rw-r--r-- 1 root root  24K Aug 20 21:11 dpkg.log.2.gz
-rw-r--r-- 1 root root 2.6K May 31 22:17 faillog
-rw-r--r-- 1 root root 1.8K May 31 22:07 fontconfig.log
-rw-r----- 1 root adm   55M Nov  8 09:52 kern.log
-rw-rw-r-- 1 root utmp 286K Nov  3 09:41 lastlog
-rw-r----- 1 root adm  1.1M Nov  8 09:52 messages
drwxr-xr-x 2 root adm  4.0K Nov  8 00:00 nginx
drwx------ 2 root root 4.0K Jan 28  2022 private
-rw-rw-r-- 1 root root  11K Nov  7 16:17 ratos.log
-rw-r--r-- 1 root root   61 Jan 28  2022 regenerate_ssh_host_keys.log
-rw-r----- 1 root adm   16G Nov  8 10:03 syslog
-rw-r----- 1 root adm  227K Nov  7 16:17 user.log
-rw-r--r-- 1 root root 1.4K Nov  2 21:25 vcore.log
-rw-r--r-- 1 root root 197K Nov  3 00:18 webcamd.log
-rw-rw-r-- 1 root utmp  69K Nov  3 09:41 wtmp

-rw-r----- 1 root adm   16G Nov  8 10:03 daemon.log
-rw-r----- 1 root adm   16G Nov  8 10:03 syslog

I also see that logrotate it's installed but nothing is configured on it

pi@ratos:~ $ cat /etc/logrotate.conf
# see "man logrotate" for details
# rotate log files weekly
weekly

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# use date as a suffix of the rotated file
#dateext

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# system-specific logs may be also be configured here.

Checking a bit further I see this things in the logs:

Nov  8 11:05:47 ratos python[594]: [app.py:log_request()] - 200 GET /printer/objects/query?heater_bed&extruder&print_stats&toolhead&display_status&virtual_sdcard&gcode_move&filament_switch_sensor%20Filament (192.168.200.11) [_TRUSTED_USER_] 29.01ms
Nov  8 11:05:48 ratos systemd[1]: KlipperScreen2.service: Succeeded.
Nov  8 11:05:48 ratos python[594]: [app.py:_log_debug()] - HTTP Request::GET /printer/info::{}
Nov  8 11:05:48 ratos python[594]: [app.py:_object_parser()] - Parsed Arguments: {'heater_bed': None, 'extruder': None, 'print_stats': None, 'toolhead': None, 'display_status': None, 'virtual_sdcard': None, 'gcode_move': None, 'filament_switch_sensor Filament': None}
Nov  8 11:05:48 ratos python[594]: [app.py:_log_debug()] - HTTP Request::GET /printer/objects/query::{'objects': {'heater_bed': None, 'extruder': None, 'print_stats': None, 'toolhead': None, 'display_status': None, 'virtual_sdcard': None, 'gcode_move': None, 'filament_switch_sensor Filament': None}}
Nov  8 11:05:48 ratos python[594]: [app.py:_log_debug()] - HTTP Response::GET /printer/info::{'result': {'state_message': 'mcu \'mcu\': Unable to connect\nOnce the underlying issue is corrected, use the\n"FIRMWARE_RESTART" command to reset the firmware, reload the\nconfig, and restart the host software.\nError configuring printer\n', 'klipper_path': '/home/pi/klipper', 'config_file': '/home/pi/klipper_config/printer.cfg', 'software_version': 'v0.10.0-584-g7527e57e5', 'hostname': 'ratos', 'cpu_info': '4 core ARMv7 Processor rev 3 (v7l)', 'state': 'error', 'python_path': '/home/pi/klippy-env/bin/python', 'log_file': '/home/pi/klipper_logs/klippy.log'}}
Nov  8 11:05:48 ratos python[594]: [app.py:log_request()] - 200 GET /printer/info (192.168.200.11) [_TRUSTED_USER_] 9.55ms
Nov  8 11:05:48 ratos python[594]: [app.py:_log_debug()] - HTTP Response::GET /printer/objects/query::{'result': {'status': {'virtual_sdcard': {'progress': 0.0, 'file_position': 0, 'is_active': False, 'file_path': None, 'file_size': 0}, 'display_status': {'progress': 0.0, 'message': None}, 'filament_switch_sensor Filament': {}, 'print_stats': {'print_duration': 0.0, 'total_duration': 0.0, 'filament_used': 0.0, 'filename': '', 'state': 'standby', 'message': ''}, 'toolhead': {'square_corner_velocity': 10.0, 'max_accel': 6000.0, 'homed_axes': '', 'estimated_print_time': 0.0, 'max_velocity': 400.0, 'print_time': 0.0, 'max_accel_to_decel': 3000.0, 'axis_minimum': [0.0, 0.0, -5.0, 0.0], 'stalls': 0, 'axis_maximum': [500.0, 500.0, 500.0, 0.0], 'position': [0.0, 0.0, 0.0, 0.0], 'extruder': 'extruder'}, 'gcode_move': {'homing_origin': [0.0, 0.0, 0.0, 0.0], 'speed_factor': 1.0, 'gcode_position': [0.0, 0.0, 0.0, 0.0], 'absolute_extrude': True, 'absolute_coordinates': True, 'position': [0.0, 0.0, 0.0, 0.0], 'speed': 1500.0, 'extrude_factor': 1.0}, 'heater_bed': {'temperature': 0.0, 'power': 0.0, 'target': 0.0}, 'extruder': {'pressure_advance': 0.0, 'target': 0.0, 'power': 0.0, 'can_extrude': False, 'smooth_time': 0.0, 'temperature': 0.0}}, 'eventtime': 481198.159779165}}

I want to mention that I have homeassistant querying the ROS for data.
As for the versions I have currently installed I am adding a screenshot for better visibility

I am trying to use a RTD Pt1000 sensor however everything I can find tells me to add it in the "printer.cfg" under the extruder.... After a restart the software comes back with unknown sensor..

I can not be the first to try this sensor.. Can you please point me in the right direction

Configuration
RatRig 500
BBT Octopus Pro STM32F446
Raspberry Pi
Extruder LGX
Hotend Mosquito Magnum
Sensor - RTD Pt1000

Using pi as the username is a potential security risk. Using the Raspberry Pi installer and modifying the username and password causes the installation to fail. Running the setup script via SSH fails due to the pi username not existing. The setup script should take a user argument so that it can be installed from the command line.

It would seem that the LAN port on the Raspberry Pi 4 B is not initializing after booting up the Alpha 2 image. If I boot it normally and don't do anything else, it will not light up and won't show up as a device on my router. However, if I unplug the ethernet cable and then plug it back in, the LAN port lights up and starts transmitting. The Pi's IP is then reachable after ~30-seconds and shows the Moonraker interface. The ratos.local page shows that Mainsail can't connect to Moonraker.

This is repeatable every time I boot the device. I've attached my most recent moonraker.log and klippy.log files.

moonraker.log
klippy (1).log

Klipper and Moonraker are very chatty even in their quietest modes, I've made the folder they log to a tmpfs file system to reduce SD card wear.
It can be a pain if your pi crashes or you reboot/power it off before getting what you need, its a trade off.

I use the Octopus v1.1 after that Klipper cant connect anymore.
first of all the serial port was wrong after that macro. and after i correct it by uncommend the line in the printer.cfg the same error. i checked the serial ports in linux of the rpi with ls /dev but there is no serial like any printer.
If i try to flash the firmware of the octopus v1.1 the file gets renamed. but this is all i cant getting an connection between the raspberrypi and the octoprint. i use the delivered usb to usbc cable that was delivered and this was workig for the first time. before i used the install macro (vcore pro) i guess this was my mistake, i reset the raspberrypi already.. how can i check that the board is ok?

Extruder max_extrude_ratio=0.266081
mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
webhooks client 3044814280: New connection
webhooks client 3044814280: Client info {'program': 'Moonraker', 'version': 'v0.7.1-479-g060ca56'}
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'

actually the wirering at the back is a mess but i want to be sure that all is working before i assable all fix

i unpluged the stopkeys because one of them (the cables of the x endstop) was getting hot and the other one is useless because the back what i get blocks from being able to reach the y end key

thats all what i get:

root@ratos:/home/pi/klipper# ls /dev
autofs	       dri	  input  loop6	       mmcblk0boot1  ptmx   ram15  random	   shm	      tty1   tty18  tty26  tty34  tty42  tty50	tty59  ttyAMA0	  vc-mem  vcsa1     vcsu2	 video12
block	       fd	  kmsg	 loop7	       mmcblk0p1     pts    ram2   raw		   snd	      tty10  tty19  tty27  tty35  tty43  tty51	tty6   ttyprintk  vcs	  vcsa2     vcsu3	 video13
btrfs-control  full	  log	 loop-control  mmcblk0p2     ram0   ram3   rfkill	   spidev0.0  tty11  tty2   tty28  tty36  tty44  tty52	tty60  ttyS0	  vcs1	  vcsa3     vcsu4	 video14
cachefiles     fuse	  loop0  mapper        mmcblk0rpmb   ram1   ram4   rpivid-h264mem  spidev0.1  tty12  tty20  tty29  tty37  tty45  tty53	tty61  uhid	  vcs2	  vcsa4     vcsu5	 video15
char	       gpiochip0  loop1  media0        mqueue	     ram10  ram5   rpivid-hevcmem  stderr     tty13  tty21  tty3   tty38  tty46  tty54	tty62  uinput	  vcs3	  vcsa5     vcsu6	 video16
console        gpiochip1  loop2  media1        net	     ram11  ram6   rpivid-intcmem  stdin      tty14  tty22  tty30  tty39  tty47  tty55	tty63  urandom	  vcs4	  vcsa6     vga_arbiter  video18
cuse	       gpiomem	  loop3  mem	       null	     ram12  ram7   rpivid-vp9mem   stdout     tty15  tty23  tty31  tty4   tty48  tty56	tty7   v4l	  vcs5	  vcsm-cma  vhci	 watchdog
disk	       hwrng	  loop4  mmcblk0       port	     ram13  ram8   serial0	   tty	      tty16  tty24  tty32  tty40  tty49  tty57	tty8   vchiq	  vcs6	  vcsu	    video10	 watchdog0
dma_heap       initctl	  loop5  mmcblk0boot0  ppp	     ram14  ram9   serial1	   tty0       tty17  tty25  tty33  tty41  tty5	 tty58	tty9   vcio	  vcsa	  vcsu1     video11	 zero

i have connected a csi original raspberrypi camera, that is now shown too at the interface. i dont know if they are one of the /dev serials it can be

Hi,
I am new at using Github, not sure if I'm asking this in the correct place. I have tried searching the web for a solution.
So here goes.

I imaged my Pi with RatOS-v1.1.0. Loaded perfectly, modified the WiFi info and my PC connects to http://RatOS.local/ just fine. Ran the updates just fine in Mainsail.
I would like to use an Android phone as an interface. I opened the Chrome browser, also tried the Edge Browser to connect to http://RatOS.local/
It won't connect, I get this error in Edge Browser:
Hmmm… can't reach this page Check if there is a typo in ratos.local.
Search the web for [ratos local]
DNS_PROBE_FINISHED_NXDOMAIN
The Chrome Browser error message similar.
My PC is connected to my Home network via Ethernet, My Android connects to my home WiFi network via the same address as the Pi.
Any help connecting to ratos/local via my Android phone would be appreciated.

WARNING: the bed_mesh behavior will change when you update RatOS through mainsail. Read more about the new behavior here: https://rat-os.vercel.app/docs/configuration/macros#bed-mesh-calibration

The changes only affect you if you set variable_calibrate_bed_mesh to False. In which case a mesh will no longer be loaded until you set variable_bed_mesh_profile to a bed_mesh profile name. To restore previous behavior, add variable_bed_mesh_profile: "ratos" to [gcode_macro RatOS] in your printer.cfg.

SO, long time listener first time caller...
Printed a F-bomb (two color) on the minion..
When it came to the color change it moves to the front of the bed and only about 2mm above the current layer. This typically wouldnt be an issue but the print is only @6mm in total z. Suffice to say once the old filament is removed getting the new purge clear is problematic. But, RAT OS reports this as a pause state rather than any color change... Code clearly identifies an m600 however.

G1 Z1 F12000
;AFTER_LAYER_CHANGE
;1
;COLOR_CHANGE,T0,#46A601
M600
; printing object F_Bomb.stl id:0 copy 3

PrusaSlicer 2.6

Version: v0.11.0-99-g56444815
OS: Raspbian GNU/Linux 10 (buster)
Distro: RatOS v 1.2.4 (buster)
Load: 0.16, Mem: 136.9 MB / 237.9 MB, Temp: 40°C
wlan0 (10.0.0.189) : Bandwidth: 5.8 kB/s , Received: 208.9 MB , Transmitted: 610.4 MB

Because of necessary major changes (bullseye and ~/printer_data conformity), you are encouraged to upgrade to the newest alpha image ASAP. RatOS updates will break your configuration in the near future.

The start date format on the table is correct, but when you view the full details, it is showing this. See the attached screenshot.

My timezone is +8:00.