[Xastir] Device closing on failure

[John Ronan]

On 29/09/11 20:19, Curt, WE7U wrote:
> On Thu, 29 Sep 2011, John Wilson wrote:
>
>> Ironic this comes up because this happened to me this morning, outside
>> of Xastir. I was monitoring the output of a TinyTrak4 through Gtkterm
>> when I inadvertently disconnected the USB-Serial Adapter and then
>> plugged it back in. It associated it with ttyUSB1 when I did that. I
>> didn't reboot but closed the gtkterm, disconnected the adapter again,
>> waited a few seconds, plugged the adapter back in and restarted gtkterm
>> and all was well.
>>
>> My point being, is there another program running that might be using
>> that same port to read and therefore assigning to ttyUSB1?
>
> It's starting to sound like the disconnect notice takes too long to 
> trickle up to the application, therefore the app doesn't know anything 
> happened and continues to hold the port.  The USB stack sees that 
> something already has that port and assigns the "new" device to a new 
> port.
>
> This sounds like a software problem but I'll bet it's the USB stack 
> that needs to be fixed, not the apps trying to use the /dev/USB* devices.
>
Hi,

I though I replied to this earlier today, so apologies,

Have a look at udev. I'm getting ready to head to a ferry shortly, 
(EI8JA-9). you configure udev to recognise the device and give it the 
same /dev/ttywhatever id no matter where/when it connects.  I had the 
same problem with a Davis Vantage VUE and when I got the udev 
incantation right, the problem went away.

Gotta run.
John
EI7IG