Can anyone confirm that Serproxy or Tinkerproxy works on Lion? I need to upgrade to continue the GFX development but I do not know if anyone is running Lion with GFX. If someone can confirm either way I would appreciate it very much.
Cheers.
9 thoughts on “Serproxy or Tinkerproxy on Lion 10.7?”
Leave a Reply
You must be logged in to post a comment.
I haven’t used tinkerproxy but serproxy worked after I did a make in 10.7 from the 32 bit linux source
jevon, can you do a quick test of tinkerproxy to see if it works?
http://code.google.com/p/tinkerit/downloads/detail?name=tinkerproxy-2_0.zip
sorry I stepped out for a bit
I haven’t gotten tinker to work although we did run the last race on a source built serproxy in 10.7.
I’ve just installed an ssd so I’m going through the process again, and with a purely 10.7 install not an upgrade.
gfx is my backup at this point as I’m writing a gold sprints program for gameduino, I don’t like taking my macbook to bars or really anywhere that drunken people might wander.
I’ll try tinker though
Ed, I don’t have an Apple, otherwise I would try. Luke does, and he is off until late January, so he is going to give it a shot and get back to you.
Is there anything else we can help you with?
I tried both tinkerproxy and serproxy built from source on Lion.
both seem to connect to the comm port, but Goldsprints FX just hangs at GO!
When gfx starts, (ser|tinker)proxy prints out
Server thread launched
server(1) – thread started
The configuration file changed slightly for tinkerproxy vs. serproxy. This should create the correct one for tinkerproxy:
http://www.opensprints.com/howto_configure_serproxy.php
I found this GUI for Tinkerproxy (Mac OSX 10.5+)
http://wolfgang.reutz.at/software/serproxygui/
this is the output from serproxygui. it seems to connect to the arduino. GFX doesn’t get past the GO! screen
Serproxy 0.2.0 – Tinker.it
Based on code by (C)1999 Stefano Busti, (C)2005 David A. Mellis
Waiting for clients
Server thread launched
server(1) – thread started
actually, Tinkerproxy does work for me. I was using the current development version of the firmware instead of the original default basic_msg version. doh!
As for serproxygui, no luck yet with that.