Navigatrix.net - A Voyager's Companion
http://navigatrix.net/

Pactor
http://navigatrix.net/viewtopic.php?f=4&t=597
Page 2 of 5

Author:  Atmo [ 17 Feb 2014, 19:08 ]
Post subject:  Re: Pactor

Hm, Makefile and rules are not allowed to attach, I#ll try to copy and paste....:

No, can't open "rules" and "Makefile"

Author:  Markus [ 17 Feb 2014, 19:35 ]
Post subject:  Re: Pactor

I'll have to leave the drivers/hardware to Moe's superior powers. In the meantime, could you check the following though:

A while ago, in this post, David advised you to fix an error in the comports script. Did you ever confirm that the error was actually fixed?

If you open the script (in a terminal window type
Code:
medit /usr/local/bin/comports
) and scroll down to line 54, the corrected next few lines should read:
Code:
else
  find /dev/serial/by-path/*|sort|while read line
  do
    ln -s \$line /dev/com\$port
    echo -n "/dev/com\$port -> /dev/"
    ls -lisa \$line|awk -F '/' '{print \$7}'
    let port=port+1
  done
fi

It is the line with
Code:
let port=port+1
that was missing in the original script. Does your corrected comports script have this line *in this place* (it would be line 60 in the corrected script)? The same line occurs in other parts of script but it was missing in this section.

It is a bit of a long shot but probably worth eliminating as a possible error source.

Author:  Atmo [ 17 Feb 2014, 21:57 ]
Post subject:  Re: Pactor

o.k., back to the boat and check that. Then, How do you change the script?

Author:  Markus [ 18 Feb 2014, 02:12 ]
Post subject:  Re: Pactor

If the line is in there already - no need to change. If not:
    * In terminal window type
    Code:
    sudo medit /usr/local/bin/comports

    * Switch on display of line numbers under the editor's 'View' menu
    * Go to line 60
    * Insert
    Code:
        let port=port+1

    above the current line 60 so it becomes the new line 60
    * Save and exit.

Author:  Atmo [ 18 Feb 2014, 03:48 ]
Post subject:  Re: Pactor

Thanks Markus, I'll try tomorrow. Was busy cutting holes into a trawler today...

Cheers
Atmo

Author:  Atmo [ 18 Feb 2014, 06:12 ]
Post subject:  Re: Pactor

O.k., looks like I have the right script.
Still, Markus, you seem to be the only one having Pactor going with a converter. Which one are you using?

My script looks as followed:

#!/bin/bash
# script to link the non static /dev/ttyUSB[N] ports
# to static /dev/com[N]. configuration will be saved
# to a configuration file which is unique for each
# computer

exec 2>/dev/null
if [ ! "$USER" = "root" ]; then
sudo $0 $1 $2 $3 $4 $5 $6 $7 $8 $9
exit
fi

product=$(dmidecode -t 2|grep -i Product)
product=${product#*: }
product=$(echo $product | sed -e 's/[^A-Za-z0-9.]//g' | tr '[a-z]' '[A-Z]')
product=${product:0:8}
serial=$(dmidecode -t 2|grep -i Serial)
serial=${serial#*: }
serial=$(echo $serial | sed -e 's/[^A-Za-z0-9]//g' | tr '[a-z]' '[A-Z]')
serial=${serial:0:8}
comcfg=/etc/comports{$product.$serial}.conf

if [ $1 = "-d" ]; then
rm -f $comcfg
fi

if [ $1 = "-s" ]; then
rm -f $comcfg
find /dev/serial/by-path/*|sort|while read line
do
echo $line >>$comcfg
done
fi

rm -f /dev/com*
ln -s /dev/ttyS0 /dev/com1
echo /dev/com1 \-\> /dev/ttyS0
ln -s /dev/ttyS1 /dev/com2
echo /dev/com2 \-\> /dev/ttyS1
port=3
if [ -e $comcfg ]; then
cat $comcfg|while read line
do
if [ -e $line ]; then
ln -s $line /dev/com$port
echo -n "/dev/com$port -> /dev/"
ls -lisa $line|awk -F '/' '{print $7}'
else
echo "/dev/com$port -> *** not available ***"
fi
let port=port+1
done
echo com port configuration from {$product.$serial}
else
find /dev/serial/by-path/*|sort|while read line
do
ln -s $line /dev/com$port
echo -n "/dev/com$port -> /dev/"
ls -lisa $line|awk -F '/' '{print $7}'
let port=port+1
done
fi

for line in $(ls /dev/rfcomm*); do
ln -s $line /dev/com$port
echo /dev/com$port \-\> $line
let port=port+1
done

if [ $1 = "-s" ]; then
echo "new com port configuration has been saved"
fi

if [ $1 = "-d" ]; then
echo "com port configuration for this computer has been deleted"
fi


Looks like that fits the description.

Author:  Atmo [ 18 Feb 2014, 16:52 ]
Post subject:  Re: Pactor

Found something on the net about FTDI devices.
Not to sure if that touches the issues:
http://www.ikalogic.com/ftdi-d2xx-linux ... g-problem/

Author:  Markus [ 18 Feb 2014, 18:14 ]
Post subject:  Re: Pactor

Quote:
Still, Markus, you seem to be the only one having Pactor going with a converter. Which one are you using?

I have a USB Pactor, so no converter involved. However, we have a boat next to us that uses a serial-USB converters for their Pactor (probably same model as yours) under NX0.5 without any problems. I don't know what converter they use and they're currentl road-touring Australia. There are a few other folks I can ask, whom I believe also use converters with their Pactors.

Author:  GoneTroppo [ 20 Feb 2014, 03:03 ]
Post subject:  Re: Pactor

Hi, just to let you know that I have a Pactor PTC IIpro with serial port that I have used with Nx via a usb-serial converter. I have used a Belkin F5U409 and one I got on Ebay from China for $1. :D
So it is possible. :)
I now use a toughbook that has a serial comm port so I now use that for my pactor to keep it simple.
Cheers.

Author:  Moe [ 20 Feb 2014, 04:46 ]
Post subject:  Re: Pactor

I agree withh Steve, but he's sharper than I am. I paid $4.50 for my cheap converter. Ran converters on P-II and P-III.

I'm still trying to make sense of your dmesg(s).

Before I get all carried away I need to figure out the significance of a mce (Machine Check Error). I've never seen one, and I'm as giddy as a schoolgirl and I don't know what that means.

Quote:
Machine Check Exceptions (MCEs) can occur for a variety of reasons ranging from undesired or out-of-spec voltages from the power supply, from cosmic radiation flipping bits in memory DIMMs or the CPU, or from other miscellaneous faults, including faulty software triggering hardware errors.
...found in your log
Quote:
[ 146.496791] pl2303 3-2:1.0: pl2303 converter detected
[ 146.508372] usb 3-2: pl2303 converter now attached to ttyUSB0
[ 147.602251] pps_core: LinuxPPS API ver. 1 registered
[ 147.602256] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 147.602462] pps_ldisc: PPS line discipline registered
[ 147.603776] pps pps0: new PPS source usbserial0
[ 147.603785] pps pps0: source "/dev/ttyUSB0" added
[ 299.988071] mce: [Hardware Error]: Machine check events logged

I'm comparing the two logs you posted and since I have the attention span of a goldfish ...but they look like their the same converters.

I'll slog through to find out if I'm mistaken and my eyes crossed reading the lines.

Author:  Moe [ 20 Feb 2014, 04:58 ]
Post subject:  Re: Pactor

...never mind. I think I'm on the right track.

I'll take a look.

Author:  Moe [ 20 Feb 2014, 05:08 ]
Post subject:  Re: Pactor

Alll threee are the same converter
Quote:
[ 146.440364] usb 3-2: New USB device found, idVendor=067b, idProduct=2303

[ 564.073255] usb 3-2: New USB device found, idVendor=067b, idProduct=2303

[ 740.306367] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
067b:2303 Prolific Technology, Inc. PL2303 Serial Port Device

Author:  Atmo [ 20 Feb 2014, 06:08 ]
Post subject:  Re: Pactor

Hm, meaning that Nx doesn't see the different converters but is stuck with the first one. The digitus I bought three years ago and the other two were given to me by my father who didn't need them anymore. They are definitely three different ones.
Plus it's the same outcome on two different computers.
So the end of the whole story is there seems to be no way to get Airmail to see it's Pactor comport via a converter. It works only in Windows.
Sad story, Windows forever just to get my E-mails and Grib files.
Last thing I could do again is reinstall Nx the xed time and see if it is finding one of the different converters. But then again Nx seems to recognise at least the digitus. Why does Airmail stete then Com three not available?
It just doesnT make sense.
Thanks a lot for all your help.

Cheers,

Atmo

Author:  Atmo [ 20 Feb 2014, 06:19 ]
Post subject:  Re: Pactor

p.s., Hardware error could be the changeover of the converters or touching the stick. (I'm running Nx of a stick)

Author:  Moe [ 20 Feb 2014, 06:19 ]
Post subject:  Re: Pactor

I know it doesn't make sense.

You could boot up; insert converter #1

Count to 10.

Unplug it; set it aside.

Count to 10.

insert converter #2

Count to 10

Unplug it; set it aside

Count to 10.

insert converter #3

Count to 10

Unplug it; set it aside

Execute:
Code:
dmesg > /home/$USER/Desktop/converters.txt


Attach the file on your Desktop by that name to your next post.

Author:  Moe [ 20 Feb 2014, 06:36 ]
Post subject:  Re: Pactor

While I'm at it. I think pps pps0: source "/dev/ttyUSB0" added and all the other pps stuff is a reason hater hate gpsd.

When a new device is attached it probes the device, "Hey, baby. You a gps?...lets hookup. You can pps my socket."

Well not everything is a gps and not every gps will do pps (Pulse Per Second) but bless gpsd's non-existent heart, it's eager, ready if not desperate.

If it was a gps capable of pps you could turn your laptop into a time server accurate to microseconds AND tell you where you are.

The USB/Serial convert can't provide gpsd with with a pps let alone valid gps data so given the silent treatment gpsd drops all communication with the device and wait for the next opportunity.

This indiscriminate, yet upfront and ultimately choosy behaviour turns some people off.

...but that's the best way to do it.

Author:  Atmo [ 20 Feb 2014, 06:41 ]
Post subject:  Re: Pactor

Roger Wilco :)

Author:  Atmo [ 21 Feb 2014, 04:07 ]
Post subject:  Re: Pactor

O.k., here we go... checked all three, two seem to be Profilic ones, one of the two broken, the digitus is the ftdi one.

Thanx :?

Attachments:
converters.txt [114.65 KiB]
Downloaded 137 times

Author:  Moe [ 21 Feb 2014, 11:17 ]
Post subject:  Re: Pactor

At least one thing is broken. There could be multiple things broken....and not necessarily with the converters.

This is what it is suppose to happen. You will see two USB/Serial converters and two hockey puck gps inserted and removed. Unfortunately, for this example, the serial converters contain the same chip as the last (Device 20) gps.
Code:
[460862.177305] usb 3-3: new full-speed USB device number 17 using xhci_hcd
[460862.193878] usb 3-3: New USB device found, idVendor=067b, idProduct=2303
[460862.193882] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[460862.193884] usb 3-3: Product: USB-Serial Controller
[460862.193885] usb 3-3: Manufacturer: Prolific Technology Inc.
[460862.194108] pl2303 3-3:1.0: pl2303 converter detected
[460862.194924] usb 3-3: pl2303 converter now attached to ttyUSB0
[460868.210674] usb 3-3: USB disconnect, device number 17
[460868.211594] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[460868.211617] pl2303 3-3:1.0: device disconnected
[460874.936916] usb 3-3: new full-speed USB device number 18 using xhci_hcd
[460874.953368] usb 3-3: New USB device found, idVendor=0557, idProduct=2008
[460874.953372] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[460874.953652] pl2303 3-3:1.0: pl2303 converter detected
[460874.954486] usb 3-3: pl2303 converter now attached to ttyUSB0
[460881.033390] usb 3-3: USB disconnect, device number 18
[460881.033594] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[460881.033613] pl2303 3-3:1.0: device disconnected
[460889.854427] usb 3-3: new full-speed USB device number 19 using xhci_hcd
[460889.871926] usb 3-3: New USB device found, idVendor=10c4, idProduct=ea60
[460889.871932] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[460889.871935] usb 3-3: Product: CP2104 USB to UART Bridge Controller
[460889.871937] usb 3-3: Manufacturer: Silicon Labs
[460889.871939] usb 3-3: SerialNumber: 001BC735
[460889.982024] usbcore: registered new interface driver cp210x
[460889.982048] usbserial: USB Serial support registered for cp210x
[460889.982083] cp210x 3-3:1.0: cp210x converter detected
[460890.146309] usb 3-3: reset full-speed USB device number 19 using xhci_hcd
[460890.162588] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8803eba58580
[460890.162592] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8803eba585c0
[460890.162804] usb 3-3: cp210x converter now attached to ttyUSB0
[460897.093948] usb 3-3: USB disconnect, device number 19
[460897.094083] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[460897.094098] cp210x 3-3:1.0: device disconnected
[460903.932799] usb 3-3: new full-speed USB device number 20 using xhci_hcd
[460903.949396] usb 3-3: New USB device found, idVendor=067b, idProduct=2303
[460903.949400] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[460903.949402] usb 3-3: Product: USB-Serial Controller
[460903.949403] usb 3-3: Manufacturer: Prolific Technology Inc.
[460903.949682] pl2303 3-3:1.0: pl2303 converter detected
[460903.950730] usb 3-3: pl2303 converter now attached to ttyUSB0
[460911.233868] usb 3-3: USB disconnect, device number 20
[460911.234039] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[460911.234054] pl2303 3-3:1.0: device disconnected

...what is interesting is they all are assigned to /dev/ttyUSB0

That's the way it's suppose to work.

But when I do this on a Navigatrix system I get port hopping up to /dev/USB4...and then it stops hopping.

This still doesn't address the ftdi_so module; or the filesystem errors your log shows.

I wish I still smoked cigarettes because this is a 2 pack problem.

Anyone can jump in. There is a work around. I just don't know what it is yet.

Author:  Moe [ 21 Feb 2014, 13:08 ]
Post subject:  Re: Pactor

Naw, I can't remember if something was setup to work this way...or it's broken.

It will take a few days to figure out if it's a feature, a bug, or a necessary evil.

In the meantime, your filesystem is tossing errors. This either a corrupt iso; bad persistent file; or bad media on the USB.

The funky driver is 3rd on the list.

Page 2 of 5 All times are UTC - 5 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/