can't connect GPSport 245 with BT747 [solved]

[Miroslav Lachman]

Miroslav Lachman wrote on 2016/12/21 12:51:
> Achilleas Mantzios wrote on 2016/12/21 08:37:
>> On 21/12/2016 00:28, Miroslav Lachman wrote:

> I noticed that ttyU0 and cuaU0 are not accessible by my user so I
> changed permissions to 0666 but BT747 still don't see them:
>
> 24340 - isValidPort('/dev/cu.serial-0001')?: false -1
> 24341 - isValidPort('/dev/cu.SLAB_USBtoUART')?: false -1
> 24341 - isValidPort('/dev/cu.iBTAGPS-SPPslave')?: false -1
> 24341 - isValidPort('/dev/cu.usbmodem1b10')?: false -1
> 24341 - isValidPort('/dev/cu.usbmodem1d10')?: false -1
> 24341 - isValidPort('/dev/cu.usbmodem3d10')?: false -1
> 24342 - isValidPort('/dev/cu.usbmodem3a20')?: false -1
> 24342 - isValidPort('/dev/cu.usbmodem620')?: false -1
> 24342 - isValidPort('/dev/cu.usbmodemfd110')?: false -1
> 24342 - isValidPort('/dev/tty.usbmodemfd110')?: false -1
> 24342 - isValidPort('/dev/tty.usbmodemfd510')?: false -1
> 24344 - isValidPort('/dev/tty.usbserial')?: false -1
> Info: trying to open 'null'
>
> I don't know where these strange device names come from. If they are
> from rxtx package or BT747 itself and I don't know where to change them
> to /dev/cuaU0 or /dev/ttyU0

I found the main problem - file permissions.
Everything would be easier if the app says "permission denied" instead 
of "no valid port".

Making /dev/cuaU0 or /dev/ttyU0 writable is not enough. The problem is 
in lock directory:

 > ls -ld /var/spool/lock/
drwxrwxr-x  2 uucp  dialer  3 Dec 21 13:48 /var/spool/lock/

Must be writable by user running BT747

Even if I am in group "dialer" I cannot connect to cuaU or ttyU. I must 
made them writable by everyone.

I will try to find this last problem later.

Thank you for your time!

Miroslav Lachman