Re: [Xastir] Non communication with radio
Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
Another issue with prolific and USB CDC devices (e.g. OT USB or new arduino variants) is that there is no unique identifier on the device, so if you have a prolific for the GPS, plug it in, get it configured, then plug in a second prolific for the tnc, get it configured, then reboot the computer with the devices still plugged in, the two devices may swap device special file names so that the GPS software is trying to talk to the tnc, and vice versa. -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
That's partially true. You have the identifier of the device AND the physical port you plug it into. I'm currently away from the computer and will follow up with how I established my prolific device to recognize multiple devices in the event of a reboot, and not mixing up attached devices. 73 John KC4LZN On Dec 8, 2013 4:15 PM, Jason KG4WSV kg4...@gmail.com wrote: Another issue with prolific and USB CDC devices (e.g. OT USB or new arduino variants) is that there is no unique identifier on the device, so if you have a prolific for the GPS, plug it in, get it configured, then plug in a second prolific for the tnc, get it configured, then reboot the computer with the devices still plugged in, the two devices may swap device special file names so that the GPS software is trying to talk to the tnc, and vice versa. -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On Sun, 08 Dec 2013 09:31:40 -0800 David Ranch xas...@trinnet.net wrote: Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD Debian mixed Jessie / Sid (testing/unstable) Xastir V2.0.1 (July 2012, that wasn't updated) D710 haven't tried any other cable nor any other programs yet ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
Here are the steps I provided to another ham to designate a specific
adapter to a port.
If you wish to make a more permanent change for your device, you can
follow these instructions for running a rule in UDEV and not have to
worry about your port assignment.
To establish a local rule in linux for your USB device (or any device
for that matter), several steps must be taken to always recognize your
device with a specific name instead of the standard /dev/ttyUSB0 or
USB1, etc.
I retrieved my guidance from this site.
http://hackaday.com/2009/09/18/how-to-write-udev-rules/
I did it for my USB to Serial adapter for my TT4. The adapter I have
is made by plugable.com and has the PL2303 Prolific chip in it that is
good up to Windows 8 and works great with any linux version out there.
The rule I wrote was extracted from the command that was listed in the
website.
First, plug in your adapter. In terminal, type dmesg and press enter.
This will show you where your device was registered to. For example,
mine took the position of ttyUSB0. I then typed:
Code
udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0)
It spit out a whole string of stuff. In your terminal, there will be
several paragraphs of information, each giving a description with
the following paragraph giving more descriptive stuff on your device.
I found out later that you can only take your rule information from
one paragraph. You can't just pick and choose from all of the stuff
you see. Each paragraph started off with looking at parent device
and I chose as much information from one of the lower paragraphs, so
as not to confuse it with anything else.
For this particular device, there is not a serial number. What
differentiates this device from all the rest is the physical location
that I plugged it into. That is identified by the KERNELS==2-2
listed below. If you were to plug it into another location, it may be
2-1 or 3-2, however your computer assigns its ports.
Open your text editor and write a rule. I wrote a rule, just as it
stated and saved it in the /etc/udev/ruled.d/ directory, naming it
60-aprsisce.rules. Depending on the version of Linux you are using,
you will have to be a super user to save to this directory. I saved
the rule with the following information in it.
SUBSYSTEMS==usb, ATTRS{product}==USB-Serial Controller D,
KERNELS==2-2, SYMLINK+=tt4
Be very vigil in typing the information extracted from the previous
command or you will have failures.
Disconnect the device and reconnect into the same port.
In terminal, type:
Code
ls -al /dev | grep USB0
and it should list the new device you just created a rule for.
In the above rule, the portion of SYMLINK is the name you are giving
your new device. In this instance, I am using a Tiny Tracker 4 with
this device so I named it TT4. You can name it anything that works
for you. Also remember, the KERNELS may be different, depending on
where you plug in your device. The ATTRS{product} will also be
different, dependent on the manufacturer of your device.
When you create your symbolic link, make sure you direct it to your
newly named device, instead of the standard /dev/ttyUSB0. For example:
Code
ln -s /dev/tt4 .wine/dosdevices/com1
(or whatever com number you wish to designate)
Remember, the device with its new name should be listed in the /dev
directory and you should use that for your symbolic link command.
73 John
On 12/8/13, John Wilson kc4...@gmail.com wrote:
That's partially true. You have the identifier of the device AND the
physical port you plug it into. I'm currently away from the computer and
will follow up with how I established my prolific device to recognize
multiple devices in the event of a reboot, and not mixing up attached
devices.
73
John KC4LZN
On Dec 8, 2013 4:15 PM, Jason KG4WSV kg4...@gmail.com wrote:
Another issue with prolific and USB CDC devices (e.g. OT USB or new
arduino variants) is that there is no unique identifier on the device, so
if you have a prolific for the GPS, plug it in, get it configured, then
plug in a second prolific for the tnc, get it configured, then reboot the
computer with the devices still plugged in, the two devices may swap
device
special file names so that the GPS software is trying to talk to the tnc,
and vice versa.
-Jason
kg4wsv
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
I think it may be a question of permissions: In earlier versions of Ubuntu I have no trouble with the ownership root:dialout but in versions later than 10.04 that does not work. In Version Ubuntu 12.04 and also in Mint 15 I have to set ownership to rein:rein (where rein is my login name) I do this at bootup with a little script. Hope this helps. Rein Mann vk4alj On 8/12/13 6:06 pm, Liz wrote: I've just been on a 2000km trip. I had upgraded the computer which runs xastir in the car and it just didn't want to talk with the radio. The radio has a cable which connects to a pl2303 serial-usb interface and it was being detected and assigned /dev/ttyUSB0. I found that gpsd was grabbing the device, so I instructed gpsd to stick to /dev/ttyACM*, which was successful in terms of gpsd running smoothly but didn't help me with accessing the radio. I got as far as finding that /dev/ttyUSB0 is rw for root and group dialout, and that I belong to group dialout. Obviously after such a trip I'm a bit tired, so what other ideas for troubleshooting have people got? Liz VK2XSE ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir -- RC Mann rei...@bigpond.net.au re...@reicamann.net http://reicamann.net ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On 12/8/2013 12:56, Liz wrote: On Sun, 08 Dec 2013 09:31:40 -0800 David Ranch xas...@trinnet.net wrote: Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD Debian mixed Jessie / Sid (testing/unstable) Xastir V2.0.1 (July 2012, that wasn't updated) D710 haven't tried any other cable nor any other programs yet Try using minicom to send control commands to the radio or TNC (depending on which mode it's in) A more basic test would be to short pins 2 and 3 on the serial connector, set minicom to no local echo and see if what you type shows up on the screen (or if local echo is enabled, you should get double what you type). ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On Mon, 9 Dec 2013 07:56:39 +1100 Liz ed...@billiau.net wrote: On Sun, 08 Dec 2013 09:31:40 -0800 David Ranch xas...@trinnet.net wrote: Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD Debian mixed Jessie / Sid (testing/unstable) Xastir V2.0.1 (July 2012, that wasn't updated) D710 haven't tried any other cable nor any other programs yet pl2303 cable works fine to program radio gpsd still claims it despite altering /etc/default/gpsd alternate cable has same result with xastir, not affected by gpsd claiming it actual installed package is xastir_2.0.1-1_i386.deb from 30 Sept 2012 This is the tail of the tnc.log # 1386540601 Mon Dec 09 09:10:01 EST 2013 �� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �LH �JIYk�ZZ1j���0�� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �LH �JIYk�ZZ1j��f0�� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �� When instructed to transmit # 1386540551 Mon Dec 09 09:09:11 EST 2013 VK2XSE-9APX201,WIDE2-2:@090909/3415.98S/14606.82E154/000/A=000451/XASTIR-Linux Eeepc 701 (nothing happens) Liz VK2XSE ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On 09/12/13 10:09, Liz wrote: On Mon, 9 Dec 2013 07:56:39 +1100 Liz ed...@billiau.net wrote: On Sun, 08 Dec 2013 09:31:40 -0800 David Ranch xas...@trinnet.net wrote: Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD Debian mixed Jessie / Sid (testing/unstable) Xastir V2.0.1 (July 2012, that wasn't updated) D710 haven't tried any other cable nor any other programs yet pl2303 cable works fine to program radio gpsd still claims it despite altering /etc/default/gpsd alternate cable has same result with xastir, not affected by gpsd claiming it actual installed package is xastir_2.0.1-1_i386.deb from 30 Sept 2012 This is the tail of the tnc.log # 1386540601 Mon Dec 09 09:10:01 EST 2013 �� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �LH �JIYk�ZZ1j���0�� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �LH �JIYk�ZZ1j��f0�� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �� When instructed to transmit # 1386540551 Mon Dec 09 09:09:11 EST 2013 VK2XSE-9APX201,WIDE2-2:@090909/3415.98S/14606.82E154/000/A=000451/XASTIR-Linux Eeepc 701 (nothing happens) Liz VK2XSE ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir Liz, Perhaps a silly question, but have you ticked enable transmitting in Xastir? Ray vk2tv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On Sun, Dec 8, 2013 at 3:21 PM, John Wilson kc4...@gmail.com wrote: That's partially true. You have the identifier of the device AND the physical port you plug it into. Sorry, but the prolific and USB CDC devices do not have an identifier unique to the device, unlike the FTDI where every device has a unique serial number. Maybe you can identify by the device type, but that doesn't help if you have more than one. The location of the device in the USB tree can usually be extracted under linux (udev rules), but relying on that is a huge pain for a laptop where the physical arrangement is fluid. I just brought a CentOS 6 server online that has a 16 port USB/RS232 adapter connected. I stumbled across a new subdirectory structure in /dev/serial/by-id that lists each device with its serial number in the name. There's also /dev/serial/by-path - this is equivalent to using the USB path as you suggested (it's a longer name but you get it for free, without mucking around with udev rules). -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On Mon, 09 Dec 2013 10:18:06 +1100 Ray Wells vk...@exemail.com.au wrote: On 09/12/13 10:09, Liz wrote: On Mon, 9 Dec 2013 07:56:39 +1100 Liz ed...@billiau.net wrote: On Sun, 08 Dec 2013 09:31:40 -0800 David Ranch xas...@trinnet.net wrote: Hello Liz, We need a bit more information here. What OS and version? What version of Xastir? What kind of radio? What kind of TNC (or software TNC)? Do you know for a fact that your Prolific (pl2303) cable is good? The reason I ask this last one is that Prolific-based cables are renown for being unreliable though they usually work fine under Linux. Have you tried any other programs to interact with the radio via this USB cable? ? --David KI6ZHD Debian mixed Jessie / Sid (testing/unstable) Xastir V2.0.1 (July 2012, that wasn't updated) D710 haven't tried any other cable nor any other programs yet pl2303 cable works fine to program radio gpsd still claims it despite altering /etc/default/gpsd alternate cable has same result with xastir, not affected by gpsd claiming it actual installed package is xastir_2.0.1-1_i386.deb from 30 Sept 2012 This is the tail of the tnc.log # 1386540601 Mon Dec 09 09:10:01 EST 2013 �� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �LH �JIYk�ZZ1j���0�� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �LH �JIYk�ZZ1j��f0�� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �� When instructed to transmit # 1386540551 Mon Dec 09 09:09:11 EST 2013 VK2XSE-9APX201,WIDE2-2:@090909/3415.98S/14606.82E154/000/A=000451/XASTIR-Linux Eeepc 701 (nothing happens) Liz VK2XSE ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir Liz, Perhaps a silly question, but have you ticked enable transmitting in Xastir? Ray vk2tv Yes, and double checked the baud rate Xastir does not take control of the radio. and neither does sudo xastir What should happen is it should switch the radio into packet mode on startup, and some other things, but nothing happens, the radio ignores the computer or the computer ignores the radio. I've got cutecom on the computer and will check to see if that can send any control commands (after lunch, that is) Liz VK2XSE ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
On Sun, Dec 8, 2013 at 5:09 PM, Liz ed...@billiau.net wrote: This is the tail of the tnc.log # 1386540601 Mon Dec 09 09:10:01 EST 2013 �� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �LH �JIYk�ZZ1j�� �0�� # 1386540603 Mon Dec 09 09:10:03 EST 2013 �� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �LH �JIYk�ZZ1j�� f0�� # 1386540605 Mon Dec 09 09:10:05 EST 2013 �� looks like a baud rate mismatch. -- -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
I used a similar HowTo at http://buzzdavidson.com/?p=45 to create a udev rule in order to ensure AX25 networking is always set up using an FTDI usb to serial adapter regardless of whether it is assigned USB0, USB1 or whatever. I only have one FTDI based adapter, so I didn't have to make it too complicated. (The person who wrote the article above only had one device on the chipset his adapter was using as well). It sounds like Liz only has one Prolific device to be concerned about, so the approach listed at the site above should do OK. John's method does show how to tie in the physical port, so as long as the same physical ports are used, a re-boot that potentially changes /dev/USBn assignments among adapters should not impact the ability for software like Xastir to stay on the same port. I don't necessarily like the idea of relying on using the exact same physical USB ports, though. Regards, Lee - K5DAT On Sun, Dec 8, 2013 at 4:21 PM, John Wilson kc4...@gmail.com wrote: That's partially true. You have the identifier of the device AND the physical port you plug it into. I'm currently away from the computer and will follow up with how I established my prolific device to recognize multiple devices in the event of a reboot, and not mixing up attached devices. 73 John KC4LZN On Dec 8, 2013 4:15 PM, Jason KG4WSV kg4...@gmail.com wrote: Another issue with prolific and USB CDC devices (e.g. OT USB or new arduino variants) is that there is no unique identifier on the device, so if you have a prolific for the GPS, plug it in, get it configured, then plug in a second prolific for the tnc, get it configured, then reboot the computer with the devices still plugged in, the two devices may swap device special file names so that the GPS software is trying to talk to the tnc, and vice versa. -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Non communication with radio
Jason, You have my attention! Could you please provide us with a URL to said referenced purchase? You may have solved several problems for several people! Thank you. 73 Dave KB3EFS On 12/08/2013 07:21 PM, Jason KG4WSV wrote: On Sun, Dec 8, 2013 at 3:21 PM, John Wilson kc4...@gmail.com wrote: That's partially true. You have the identifier of the device AND the physical port you plug it into. Sorry, but the prolific and USB CDC devices do not have an identifier unique to the device, unlike the FTDI where every device has a unique serial number. Maybe you can identify by the device type, but that doesn't help if you have more than one. The location of the device in the USB tree can usually be extracted under linux (udev rules), but relying on that is a huge pain for a laptop where the physical arrangement is fluid. I just brought a CentOS 6 server online that has a 16 port USB/RS232 adapter connected. I stumbled across a new subdirectory structure in /dev/serial/by-id that lists each device with its serial number in the name. There's also /dev/serial/by-path - this is equivalent to using the USB path as you suggested (it's a longer name but you get it for free, without mucking around with udev rules). -Jason kg4wsv ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
