Welcome to the SeeMeCNC Community

Hey guys,
I'm still in the process of building my Rostock V2 kit (mounting LCD and closing case right now.. woooohoooo ) but I wanted to start thinking ahead. After I calibrate and print a few prints I would ideally like to have something like my raspi and octoprint with the camera on the printer.

My friends use it for their PrintrBotJr, Mendel and reprap (i think). I saw a thread on this forum for the V1 Rostock and the creator of Octoprint chiming in but I can't seem to find any info about the V2. If it's too much of a PIA then might not be worth it yet but having the ability to monitor prints, live stream etc from my Pi (not dedicated computer or SD) even if the Pi is super slow for slicing would make me very happy ..

If anybody has it running with the Rostock V2 could you chime in and let me know of any settings thoughts etc ?

Below are links i've found:
[list]http://forum.seemecnc.com/viewtopic.php?f=54&t=1227[/list]

• http://blog.rymnd.com/articles/rostock-upgrades/

• https://github.com/seemecnc/OctoPrint

octoprint fork on the seemecnc site.

I just started printing, so take my post with a grain of salt.

I have remote access to my desktop via my S4. I've set up my webcam so it only faces my print bed and placed it on motion sensor recording. from my remove desktop view i can watch my print and control the camera and printer as needed with no additional purchases.

v1 and v2 use the same electronics so it will be the same setup.

yea, this is way less cool than your project, but ustream + teamviewer works really quite well

So I just setup my V2 and octoprint. It was a pain in the ass. First I was having some serious communication problems with the current 0.91 firmware available from seemecnc. To make it work I had to manually update the firmware from repetier. I think it was 0.91 rev 8. I had to manually compare configuration.h and pinouts.h and make sure all was configured correctly. I initially fucked up and missed a few things like endstop settings which cause me to grind the belts a bit. If you do it, keep your finger on the power button. Take your time and double check.

Once the firmware is current its onto octoprint. I overclock the PI to 1ghz with some heatsinks I got from amazon. Install the octopi image and update everything.

sudo apt-get update
Sudo apt-get upgrade
sudo rpi-update

I forget the octoprint git commands for updating but you can find those. There are a few things you can add to config.yaml that give you very similar functionality to repetier-host. Things like easy calibration and flow rate.

I bought a known working webcam from amazon. A c270. And it just works out of the box with octopi.

Now I don't have to have a laptop taking up space next to the printer. I can use my gaming PC to slice with whatever slicer I want, upload it, and then watch it being printed from anywhere in the house.

You can also use the GPIO on the PI to power on and off the print. Create the button in octoprints config to run GPIO commands.

Weird,
So I didn't get notified of these messages. In any case thanks for the update (i use ssh and teamviewer for work etc.. but i'd like to use my pi)..

Is there a reason you sped up your pi for this?

Also out of curiosity do you feel like making na image backup of this and sharing it for an easy install ..

Finally what was the major reason for updating the firmware on the Rostock? Was it really just communication? If so is that a serial/usb issue or another reason ?

Thanks guys for the feedback

I could connect to the RaMbo board @ 250000 baud but something to do with the way the wait command was being received would lock up my rostock. It would just repeatedly send the wait command. The dial and LCD would stop functioning altogether. I would have to unplug the printer and wait a minute or two before attempting to reconnect. At the time I wasn't sure if even upgrading the firmware would help. I spent a few hours getting it working and now everything seems fine. I've printed multiple times with it so far and everything is working. On a stock OctoPI image, 250000 baud isn't supported initially, hence all the updating. Once I updated and was able to connect at 250000, I ran into the new problems of the printer locking up. I believe the firmware upgrade fixed the printer locking up although I couldn't find anyone else complaining or having the same issues with octoprint and the Rambo board.

I sped up the PI because I saw a lot of people complaining about the printer occasionally slowing down during prints and It seamed a lot to do with time-lapse's gobbling up a lot of CPU. It seams either lowering the resolution of the feed or O.C. helped. I did both.

If you want an image of Octoprint, just download OctoPI and run the update commands. Here is the Official mirror: http://docstech.net/OctoPiMirror/

as for the firmware, I could upload my Configuration.h and Pinout.h but you would have to use it at your own risk.

Nips,
So finally had a few hours to get my Octoprint connected to the Rostock. I'm seeing the same deal you are with the Rostock locking up and some commands being sent continuously. You said you spent a few hours woking on it and got it working can you provide more details?

Also I have no idea how to convert my Repetier ABS/PLA settings to ones useable by octoprint. For example (mind you i'm a newbie) what does https://www.dropbox.com/s/86pn84lzrlhw2 ... 9.png?dl=0 this correspond to in Repetier my guess is: https://www.dropbox.com/s/ds39wwnwayrr5 ... 6.png?dl=0

Also so you said you updated and then you could connect at 250000. What did you update? Firmware upgrade on Rostock or updated the octoprint software?

In any case i'd love to get whatever files you had to change to make this work. This includes the ABS/PLA yaml files if you have them?

On the bright side the camera is now running so I can remotely monitor my prints now

P.s. I repeated some of these questions because I seem to already have the newest firmware versions on rostock and the octopi..