This is looking good: device is created as it should.
Re. the permissions, is your user in the dialout group? You can see that with the 'groups' command, e.g.:
octoprint@framboise ~ $ groups octoprint tty dialout video netdev
If not add your can add your user to the group:
sudo useradd -G dialout
To take effect you need to logout/login, check again that you are in the group and retry Cura...
- 1
Recommended Posts
gr5 2,268
Make sure you double check the cables to the ulticontroller.
Then I would try to reflash Marlin onto the board. That board might have the UM2 firmware instead of the UMO firmware. The displays are very different for the 2 machines I believe. Do you have a windows machine you can use for that step? I don't know Cura on linux - if it isn't connecting through USB using linux I would try windows. When installing and first running Cura there should be a step where you can load the firmware or if not you can do "load firmeare" from one of the menus at the top.
Link to post
Share on other sites
amedee 349
Hi,
Can you paste the last lines of 'dmesg' after you plugged in your printer?
Normally you should see it allocating a tty for the communication (/dev/ttyACM0 or something like that)
If that is all good you can check the permissions on that device, so we are sure Cura can access it.
Worst case I can give you an incantation to upload the firmware from the command line.
Groetjes
Link to post
Share on other sites
Mothboy 1
Hello,
Thanks for the fast replies.
This is the output for the dmesg and tty permissions.
Hope you can help me to make the printer work,
already much appreciation.
Hans
Link to post
Share on other sites