Hello everyone!

Just a preface:
I'm very new to the reprap scene, so please bear with me if I'm using nonspecific or incorrect terminology. Also, the machine I'm working with was bought at built by an art professor at my school, and he is kindly letting me use it. He's never actually attempted to print anything on it yet, so I'm in charge of getting it to actually work. What this means is I have little idea how it is put together and whether or not there is something done incorrectly. I AM sure he is using a GEN6 board, however (assuming the picture shown on the mendel-parts website is correct!)

The problem is as follows:
As with the guy on this post: viewtopic.php?f=35&t=184 what I think is the X-axis motor makes a high pitched whine when plugged in, as if the motor are stuck.

What I've tried:
I was using the default reprap software at first. However, after reading the thread linked above, I switched to repsnapper. The problem is, I'm using OSX, and I'm not sure if there are up to date versions of repsnapper available. The ones I've tried are from this website: https://sites.google.com/site/davidbuzz ... x-binaries. Something weird is the only available ports for connection when I open repsnapper are: /dev/tty.Bluetooth-PDA-Sync and /dev/tty.Bluetooth-Modem. The repsnapper versions available on the mendel-parts website are .exe, so they're not useful.

My questions:
1. Is there a way to get the latest, or a working version of repsnapper for OSX?
2. Is it possible this is not a software issue, and I need to tweak something else?

I too am beginning, and use RepSnapper on OSX. Try plugging in the USB cable before launching the application, that's then only way I can get it to recognize the board and show up in the drop-down menu, otherwise I see the same as you.

Alright thanks. I think I tried that, but It's worth another shot. I downloaded a program that's apparently a serial emulator for OSX. I'm hoping if RepSnapper doesn't recognize it, the emulator will and I'll be able to type in the correct port...

Update:
Still no luck. I ran USB prober with RepRap plugged in and I'm getting a kIOUSBPipeStalled (0xe000404f) error. Does anyone know what this might mean?

Hi Ostowe,

Have you installed the FDTI driver for OSX? These setup the USB as a serial port and you should see something like /dev/tty.usb.af600 in the port list.

I tried using repsnapper but whenever I click the 'Connect to Printer' it just crashes. I tried building it from scratch, but I cannot get it to compile.

I have now switched to using ReplicatorG, it you set the right parameters in the machines file it connects ok. The problem is that it uses Skeinforge for the gcode generator and that requires some effort to set it up. There is a good procedure here: viewtopic.php?f=37&t=256

Cheers
Geoff

Hi Geoff,

I did install the FTDI drivers last night, but I'm not positive I installed the correct one. I installed the 64-bit VCP driver from this page: http://www.ftdichip.com/Drivers/VCP.htm I thought since I'm using Snow Leopard I should use the 64-bit driver...not sure if that's correct.

I also downloaded ReplicatorG last night and was having trouble with it. When I set the driver to a random option in the dropdown, like Cupcake Basic or something, the only ports available with my current install of FTDI drivers are:

/dev/tty.bluetooth-PDA-Sync
/dev/tty.bluetooth-modem
/dev/cu.bluetooth-PDA-Sync
/dev/cu.bluetooth-modem

I've only just started using it though, so I'll keep working at it. Thanks for the help!

I've just had success getting movement. I apparently hadn't restarted after installing FTDI drivers.

However, now my issue is that every time I use the "switch heat on" button in repsnapper, the board shuts down and restarts, requiring me to reconnect to the printer. Any insight into this new issue?

For what it's worth, I began having problems after installing the FTDI driver, and eventually saw somewhere here or in reprapwiki forums that OSX no longer needs those. I was buying a new laptop anyway, so didn't install them onto my new Mac Air, which now works fine with Repsnapper.

Check the Gcodes (http://reprap.org/wiki/GCode) being sent to the device at that time. You're not sending M112 are you? There's a small buffer usually of four commands, so it may not be the absolute last one sent that triggers the restart...

Interesting, maybe I'll try uninstalling the FTDI drivers if I can't get this working. The laptop I'm using is a Macbook Pro 13" I got about 3 weeks ago, so I might be in the same boat as you, mkouri.

Update: I tried both M104 and M109 and both make the board shut off and restart. I can't see any instance of M112 being sent in the log.