Re: Getting back into all this...
Posted: Sat Oct 03, 2009 1:51 am
Hey mate,walkercam wrote:Progress report:
Finally got the serial connection to open up. The problem was being caused by this section in Serial.py:What I did was take it back to the most simple form of the serial.Serial command and changed it to serial.Serial(0). This worked. I slowly added back in the other operators until it shat itself. Turns out it doesn't like 's.port' for some reason. I hard coded it to be:Code: Select all
try: self._connection = conn = serial.Serial( s.port, baudrate = s.baudrate, bytesize = s.bytesize, parity = s.parity, stopbits = s.stopbits, timeout = s.timeout, xonxoff = s.xonxoff, rtscts = s.rtscts, ) except serialutil.SerialException, msg: raise comms.interface.CannotconnectException, msg
And now it works. I turned on the TA board and packets of data started popping up in the tuner windowCode: Select all
try: self._connection = conn = serial.Serial( 0, baudrate = s.baudrate, bytesize = s.bytesize, parity = s.parity, stopbits = s.stopbits, timeout = s.timeout, xonxoff = s.xonxoff, rtscts = s.rtscts, ) except serialutil.SerialException, msg: raise comms.interface.CannotconnectException, msg
Aaron - Any ideas as to why the tuner might be unhappy with the s.port operator? I assume it works fine in linux?
Cheers guys.
I'm guessing it doesn't like the port number being cast as a string, which I imagine happens when it is loaded from the config file. I will look into the code