search

whpthomas / GPX

Gcode to x3g conversion post processor
GNU General Public License v2.0
98 stars 16 forks source link

Possible serial port issue on Linux #3

Open KazW opened 10 years ago

KazW commented 10 years ago

When I compile and run this on Linux (I've tried Debian and Fedora on x86 and ARM), there seems to be an issue with serial communications.

On Fedora on an x86 machine, the serial port is opened, the build notification is sent to the printer, but then the process hangs and the printer doesn't move.

On Debian on a Raspberry Pi, the process goes a bit further and the printer starts moving, but dies once the command to heat the build plate of my 2X is sent, the process dies. The build completed notification is not sent to the printer and the HBP remains on

Fedora output (x86_64):

Reading from: butterfly.gcode
Communicating via: /dev/ttyACM1

Debian output (ARM):

Reading from: butterfly.gcode
Communicating via: /dev/ttyACM0
Extrusion length: 0.030 metres
Estimated print time: 10 minutes 51 seconds
X3G output filesize: 663 bytes

OR

Reading from: butterfly.gcode
Communicating via: /dev/ttyACM0
Extrusion length: 0.000 metres
Estimated print time: 10 minutes 32 seconds
X3G output filesize: 267 bytes
Mjolinor commented 10 years ago

I to have this problem with Linux. My start.gcode gets about half way through and that is it, the printer will sit for ever after that..

Mjolinor commented 10 years ago

With the -v option I get: Reading from: ./serialtest.gcode Writing to: ./serialtest.gcode.x3g Extrusion length: 0.000 metres Estimated print time: 2 minutes 39 seconds X3G output filesize: 10078 bytes

when I make an X3G file but sending over serial I get: Reading from: ./serialtest.gcode Communicating via: /dev/ttyACM0 Extrusion length: 0.000 metres Estimated print time: 2 minutes 6 seconds X3G output filesize: 702 bytes

The 702 bytes transferred can be any number from 20 or so up to around 700 maximum and the machine behaves accordingly.