Repetier in Linux

[theverant]

Having issues with Repetier Host in Linux - anyone using RH in a *buntu environment?

- I ran the script and it downloaded and installed tons of stuff. RH boots fine.
- I set up the printer as I did in the Mac version
- I lowered the baud rate as suggested in the firmware
- Arduino has no trouble connecting to the Rambo to upload firmware, so I know what the address is
- RH hangs when connecting with 6 commands queued
- Crashes if I click the protocol dropdown menu (it is set to serial)
- Seems to reset the printer address among other settings in the first printer setup tab
- has exactly the same weirdness on two completely different machines (One is Ubuntu, one is Linux Mint)

Am I missing a step?

[geneb]

Are you using the 0.90c version of RH?

g.

[kbob]

Sounds like baud rate to me.

In RH, do you see any messages from the printer when you connect to it? You should see something like this.

Code: Select all

  1:43:38 AM: Attempting to connect to printer
  1:43:38 AM: Connection opened
< 1:43:47 AM: start
< 1:43:47 AM: FIRMWARE_NAME:RepetierMAX0.80 FIRMWARE_URL:https://github.com/seemecnc/RepetierMAX PROTOCOL_VERSION:1.0 MACHINE_TYPE:RostockMAX EXTRUDER_COUNT:1 REPETIER_PROTOCOL:2
< 1:43:47 AM: Printed filament:94.67 m
< 1:43:47 AM: Printing time:0 days 18 hours 4 min

(Note the time stamps. There is a 10 second pause in there.)

[theverant]

Sounds like baud rate to me.

In RH, do you see any messages from the printer when you connect to it? You should see something like this.

Code: Select all

  1:43:38 AM: Attempting to connect to printer
  1:43:38 AM: Connection opened
< 1:43:47 AM: start
< 1:43:47 AM: FIRMWARE_NAME:RepetierMAX0.80 FIRMWARE_URL:https://github.com/seemecnc/RepetierMAX PROTOCOL_VERSION:1.0 MACHINE_TYPE:RostockMAX EXTRUDER_COUNT:1 REPETIER_PROTOCOL:2
< 1:43:47 AM: Printed filament:94.67 m
< 1:43:47 AM: Printing time:0 days 18 hours 4 min

(Note the time stamps. There is a 10 second pause in there.)

I am using the latest version, yeah.

No, it just hangs. And I did turn down the baud rate in the firmware, and matched it in RH.

[theverant]

Tried it again, and it now works. I think this was related to the f'd up firmware/eeprom problems I was having. Thanks for the feedback, all!