You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, it's just moonraker and klipper but simplified from the docker-compose.yml in prind repo. However when I connect to moonraker with fluidd, this is the error I receive on FIRMWARE_RESTART:
mcu 'mcu': Unable to extract params from: config_spi
This type of error is frequently caused by running an older
version of the firmware on the micro-controller (fix by
recompiling and flashing the firmware).
Known versions: host=?, mcu=v0.10.0-324-g91ba9c00
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Protocol error connecting to printer
Tihs error occurs even when running prind using the repo's docker-compose.yml. It feels like I'm missing some property in docker-compose.yml and preventing klipper from grabbing the host or config_spi data. Any ideas?
The text was updated successfully, but these errors were encountered:
I found out why this happens, the klipper version in mcu was out of sync with the host (obvious as per error msg), but also because there was a syntax error in my printer.cfg
[gcode_macro PRINT_START]
gcode:]
; extra ']' character ^
M117 Starting Print...
Removing that syntax error along with updating the firmware was able to fix this issue. Not prind related! Sorry for clogging up the issues.
I'm looking to run prind containers in a simpler docker-compose config:
As you can see, it's just moonraker and klipper but simplified from the
docker-compose.yml
inprind
repo. However when I connect to moonraker with fluidd, this is the error I receive on FIRMWARE_RESTART:Tihs error occurs even when running prind using the repo's
docker-compose.yml
. It feels like I'm missing some property indocker-compose.yml
and preventing klipper from grabbing thehost
orconfig_spi
data. Any ideas?The text was updated successfully, but these errors were encountered: