Debian ddclient not updating
The reason is that a few Linux distributions (including older versions of Raspbian) still provide a Py Serial version (which is used by Octo Print to connect to your printer) that doesn't support 250000 baud (which isn't a "standard" baudrate so to say).
You have two options to solve this for yourself: Note that - as of September 2014 - the Raspbian Wheezy image available from the Raspberry Pi Foundation (dated 2014-06-20) supports 250000 baud out-of-the-box.
At the very least you'll want to configure Octo Print to be only accessible through a reverse proxy from the outside (e.g.
by setting up haproxy in front of Octo Print and forwarding its port 80 instead of Octo Print's port 5000 -- Octo Pi even already ships with haproxy in place! Better yet is to setup a VPN solution (Part 1, Part 2). It is not a full fledged network security solution and it also does not try to be that since that would open up a whole different can of worms. If you want to access Octo Print from the internet including webcam support, I strongly suggest you put haproxy in front of it and make everything reachable under port 80 (Octo Pi users: No need to do anything, Octo Pi already comes preconfigured this way, so hands off!
Please refer to the Octo Pi Github project for any problems you have with the SD card image Octo Pi.
While this FAQ also contains a section about Octo Pi specific frequently asked questions, this is just for you convenience.
If Octo Print can't seem to connect to your printer although the printer appears to be properly responding, like e.g.
in this example log of the serial communication: (port='/dev/tty USB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from 'Opening serial port' to 'Connecting' Recv: start Recv: echo: External Reset Recv: Marlin1.0.0 Recv: echo: Last Updated: Aug 6 2014 | Author: (Antonio castro, bq Hephestos) Recv: Compiled: Aug 6 2014 Recv: echo: Free Memory: 3771 Planner Buffer Bytes: 1232 Recv: echo: Hardcoded Default Settings Loaded Recv: echo: Steps per unit: Recv: echo: M92 X80.00 Y80.00 Z4000.00 E100.47 Recv: echo: Maximum feedrates (mm/s): Recv: echo: M203 X250.00 Y250.00 Z3.30 E25.00 Recv: echo: Maximum Acceleration (mm/s2): Recv: echo: M201 X3000 Y3000 Z100 E10000 Recv: echo: Acceleration: S=acceleration, T=retract acceleration Recv: echo: M204 S1000.00 T1000.00 Recv: echo: Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/ s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s) Recv: echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00 Recv: echo: Home offset (mm): Recv: echo: M206 X0.00 Y0.00 Z0.00 Recv: echo: PID settings: Recv: echo: M301 P23.05 I2.00 D66.47 Send: M105 Send: M105 Recv: echo: SD init fail Changing monitoring state from 'Connecting' to 'Closed' Connection closed, closing down monitor you should try to increasing your Connection timeouts in the Settings.
If you are running Octo Print on a Linux machine it is possible that you won't be able to connect at 250000 baud out of the box - note that Octo Pi supports 250000 baud.
your Raspberry Pi) and the port you are running Octo Print on.
With a vanilla Octo Print install that means you'll need to forward to port 5000.
There is a plugin that adds support for Makerbot (except for 5th gen) and Flash Forge printers. Makerbots up to Gen5 and clones talk s3g/x3g instead of Gcode.
That's why you print the x3g file instead of the gcode file. The Octo Print-GPX plugin wraps GPX for two-way printer communication.