I agree with @Stefan, that what people reported who connected an unconfigured RPi. I don't think that is firmware dependent. Maybe the RPi default image initialized the USB port somehow an Marlin thinks it has to report via USB but cannot for some reason and that's lets it do nothing... Just a thought. I didn't connect as long as I didn't set it up and after setting it up you have to explicitly connect in OctoPrint...
Just flashed my V1.0 pro firmware to RC6 with Octoprint plugin, worked after a few corrections to the process. I downloaded the firmware hex from the Github (https://github.com/BigBox3D/Firmware) Installed the plugin to Octoprint using URL - https://github.com/OctoPrint/OctoPrint-FirmwareUpdater/archive/master.zip Installed avrdude on the Pi with - sudo apt-get update sudo apt-get install avrdude sudo reboot Extracted the hex file from the download from the github to my desktop from Octoprint, disconnect the Printer. into setting and plugins - Firmware Updater. Used the spanner to input path to avrdude - /usr/bin/avrdude Browsed to the hex file on my desktop and hit Flash from File. 30 seconds later, all done.
First print test after upgrade, all looking good so far, noticed the the nozzle temp varies more than it did before, by about 4 degrees, before it was pretty much rock steady at when you set it to, got it running at 210, and going to 214 and down to 207. seems to be running a little quicker than before as well.
Alex, thanks, will do that looks like there is a plugin for Octoprint to tune the PID, will try that and let you know.
Alex, used the Octoprint pidtune plugin, and worked great, nozzle temp now varying only 1 degree +/-.
I cant get the plugin to work... avrdude installed and seems to work... but the plugin never receive and version numbers. Have tried to run the flashing without the check for version but nothing happens... (maybe good...) But I do not understand why everybody else seem to have no problem. Anyone have any idea what the problem is? I can connect fine and print but do not seem to update the marlin software.
@GrodanB What you talk about does not work... You should only use the flash from file or flash from URL functions, the rest does not work... Also you have to select the port, do NOT leave AUTO in the selection, this does not work here, and be sure you disconnected OctoPrint before you try, otherwise the buttons won't get active...
I built RC6 and things are working fine except, speaking as a designer, THE KNOB IS BROKEN. SERIOUSLY WTF? Turn left, value decreases, turn right, value increases. (Or is this another one of the reasons metric still isn't accepted in the US, all the knobs have to go backwards? There's also another problem where the rate of increase/decrease feels over sensitive, it's easy for me to dial past the desired value when I'm setting temperatures. Is there a patch to get the RC6 knob to work the same as it did in the pre-installed binary?
First the plugin tries to get the version number... does not work... secondly when that fails I try the flashing... and nothing happens... except that the "progress bar"... So the automatic that you mentioned is that auto connect? Because if it is, that is probably my problem...
There is a fix for the nob... There seem to be no fix to the US measuring system... even if the US is migrating to metric "Inch by inch". (all US units are based on metric standards since 1963...)
You are supposed to only point it to a file or URL then select a port and hit the button. Do not use the check for updates or check version after update thing...
Shall the OctoPi function automatic connect be on or off? What I see is that in the background OctoPI reconnects and start talking to the Marlin/Rumba. And THANKS for all your help. You have realy made a big difference in getting this to work.
You can the auto connect on startup on though I don't do this because connecting resets the RUMBA... You have to open the connection section and disconnect. Also if you have the auto port detection plugin this shows an AUTO in the ports selection also in the firmware updates but this does not work there...
OK, then I need to think.. I use /dev/tty/ACM0 as my device. I have checked that AVRDude is in /usr/bin/ and that the plugin has /usr/bin/avrdude in the path settings... (is that wrong? I tested JUST the path /usr/bin/ (which is was I call a "path") but no success... also the test button does noting so I feel absolutely blind....) I have also via PuTTY run AVRDude at commad line and with no arguments it seem to execute fine. Will test again... printing a BIG tie fighter for my son as a test... and also trying to prove that the 3D printer was something that we "need"
