The Navigatrix has been updated. The new website can be found at navigatrix.net.




Post new topic Reply to topic  [ 93 posts ]  Go to page 1, 2, 3, 4, 5  Next
Author Message
 Post subject: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Here we are again, the new Nx beeing even greater then the old one but still no way to get it to communicate with Pactor. What is so incredible complicate on these serial converters SCS Pactor is using that it seems impossible to bring NX to recognize it. Commset not found, comm 1 error 6 it states. Copying and pasting pages after pages of Sudo commands, no gain..
Question: Is there anybody out there who ever got a pactor modem working on Nx?
To write this I also had to go back to windows because on NX the @ sign does not work.... It did in the old version.
Without Pactor I can't do a harddrive install because I need the superslow annoying windows for it..
So again: Has anybody ever got it going with Pactor? Well, if not, it looks like I have to give up. I am trying since one year now on two different Computers.
The old version also had something like commports showing up in the directory, the new one doesn't.
Hardware is Pactor PTC 2E, Pc is a Panasonic toughbook and a Macbook 13 with a dedicated windows partition for the Usb selector on dos

Any help is very much appreciated.

Cheers,
Atmo


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
Ok, the USB ports should come out as com3 and com4 in Airmail, as I recall.

Are you using a USB Pactor or a serial pactor with a USB/Serial converter?

...and just to be clear; are we talking Airmal/Pactor/USB?

Pick one machine and solve the problem, and then solve the problem on the other machine.

If you have made any changes....recreate your persistence file.

Isolate your variables..isolate the problem.


Top
   
 
 Post subject: Re: Pactor
Site Admin

Joined: 20 Mar 2012, 13:32
Posts: 116
I have used a Pactor Ptc-II-USB with NX via USB over that past 3 years without any problem on different computers (first NX04. and now NX0.5, both from USB stick and hard disk). The same is the case for friends on a neighboring boat with different hardware (older modem with serial to USB converter in their case).

My Airmail options are set as follows:
Attachment:
AirMail Options_007.png
AirMail Options_007.png [ 11.93 KiB | Viewed 32482 times ]

I guess your comport setting may have to be different, depending on what other peripherals you have connected (although NX might pick that up automatically when you start Airmail). When I run 'comports' at the command line after connecting the Pactor I get the following output:
Code:
markus@markus-laptop:~$ comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0 (/sys/devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.0/ttyUSB0/tty/ttyUSB0/uevent)

What is important is the sequence in which things are switched on/connected:
[1] NX up and running, Pactor off
[2] Power on Pactor *before* you start Airmail on NX
[3] After Pactor has successfully initialized - start Airmail

My connection window with Pactor firmware version is shown below:
Attachment:
Terminal_008.png
Terminal_008.png [ 8.29 KiB | Viewed 32482 times ]

My Pactor firmware is a bit dated but works fine and I'm reluctant to mess with it. If your's is sigificantly older, updating the Pactor firmware may be worth the hassle (current versions for this models are somewhere in the 4.x I believe).

The only times I got a connection error was when the Pactor did not initialize correctly, which you can tell from the Pactor's LED display. Switching the Pactor off and on again has always resolved this.

Regarding the '@' symbol: I vaguely remember having this issue at one point. If I recall this correctly, I was running from a USB stick and it turned out that the keyboard layout setting was incorrect.


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Great, thanks for your input Moe and Markus.
We are running a PaPactor 2 E, which is the one with RS232 so I'm using a Digitus USB2 Converter. According to Digitus and SCS Pactor they are using the same ConverterChip/Board in the Pactor 2 USB.
I'm very happy to hear that there are actually system who made it to connect to Pactor.
But how do I get NX to recognise the modem respective the Converter?
I could not find any Commports at the system folder/ manager/ Profiler.The Linux drivers for the Converter are a couple of pages I copied and pasted into Terminal which didn't seem to do anything.
Would there be a converter on the market which is known to work with Linux?
Digitus states their's run on Linux though.
As I said; I'm working on it since Panama last year and I'm still more the keen to get it running.
Regarding the @ you were right Markus, the system set itself up to US and I needed Ireland...., took a while to figure.
Further, it's absolutely amazing how fast my Celeron 900 Toughbook runs on Nx.
At least ten times faster the Windows XP. Slowing down is probably only the USB Port.
Even all the Digitizer screen and other Toughbook specific specials are running like a dream.
Once I get the Pactor going I'll reduce the windows to a minimal size and do a harddrive installation.
DA-70156 is the Converter with Chipset: FTDI / FT232RL which is supposed to work with Linux.
As you stated Markus your neighbour had it running with I guess exactly this Converter.
Would there be a hidden tool somewhere in Nx where I could get it to search for the plugged in Converter without having the Modem connected?
In the moment I get Pactor 2e family modem not found at the airmail setup wizard and in Airmail terminal I get commport failure error 6.
One doesn't go without the other so it's a bit of a catch 22 situation.

Maybe I would have needed to type some extra lines into Terminal, I don't know.
I will take time to learn about Linux programming but that will take a few years.
maybe that gave you guys a clue now what I could do, that would be great.

Thanks a lot again,

cheers,

Atmo :roll:


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
I think you might be trying too hard.

Most...most...USB/Serial converters are automatically detected and set up.

Try it. Open a terminal (<ctrl><alt><t>) enter:
Code:
dmesg | tail
to print the tail end of your computer's message log.
It prints out a lot of stuff, some of it is actually interesting.

Now enter <ctrl><l> to give yourself a cLear terminal.

Plug in your USB/Serial adapter...enter:
Code:
dmesg | tail
again...or just use your up key and enter.

It will look similar to this:
Quote:
wadda@mini:~$ dmesg | tail
[142460.062455] usb 3-3: USB disconnect, device number 2
[142460.062587] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[142460.062608] pl2303 3-3:1.0: device disconnected
[142511.684141] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[142511.700704] usb 3-3: New USB device found, idVendor=067b, idProduct=2303
[142511.700708] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142511.700710] usb 3-3: Product: USB-Serial Controller
[142511.700712] usb 3-3: Manufacturer: Prolific Technology Inc.
[142511.700924] pl2303 3-3:1.0: pl2303 converter detected
[142511.701451] usb 3-3: pl2303 converter now attached to ttyUSB0
wadda@mini:~$
The converter has been assigned to /dev/ttyUSB0

Since Airmail is not a Linux program it doesn't understand "/dev/ttyUSB0". There is a script that says; "If there is something at /dev/ttyUSB0 call it "com3". If there's something at /dev/ttyUSB1, call it "com4" so Airmail can understand."

Sometimes a convert is assigned to /dev/ttyACM0 because of a different chip inside.

What is the output of your converter?


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
O.k., here we go.
First step forward in a year...
Both Pc's, Mac and toughbook, recognised the Converter.

The output is /dev/ttyUSB0 on both appliances.

Now I have to find out why airmail doesnt see these as Comports.

Be back to the boat Friday and see...

Thanks heaps so far,


Atmo :D


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
...just as a reminder; Airmail won't see '/dev/ttyUSB0'; it can't.

It will see 'com3'...which is the same thing because some magic in the background sez /dev/ttyUSB0 = com3.

Check it out:
Code:
cat /usr/local/bin/comports | less
<space> to move down; <b> to move up (back); and <q> to quit.


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Elloh Elloh,

here we are again.
Really interesting stuff to get Pactor working. Thanks a lot for all the tricks and advice. Now I have a nice set of tools to see what's actually going on in NX.
Also I know Nx is recognising the USB Converter.
But it still doesn't connect to Pactor.
Airmail states " Com 3 not available" and at Com 4 it says: com 4 set state failed.
Could it be that Pactor actually sees the Converter as an occupied Port?
As mentioned before, I am using the same set up sucessfully (plug and play) on the windows partition of our Macbook and on windows on our toughbook.
Knowing you guys a little bit by now there is probably only a small trick to be applied via Terminal....
Feels good to get closer....

Cheers
Atmo
SV Elfrun :D


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
Ok, with all the USB stuff unplugged...plug in just your Pactor.

in the terminal enter:
Code:
dmesg | tail > ~/Desktop/pactor.txt
This places the output of dmesg | tail in a text file called pactor.txt on your desktop.

Either attach the file or cut and paste the contents to a post so we can see what is going on.

...and since you've just plugged in,
Markus wrote:
What is important is the sequence in which things are switched on/connected:
[1] NX up and running, Pactor off
[2] Power on Pactor *before* you start Airmail on NX
[3] After Pactor has successfully initialized - start Airmail
...because correct advice is good advice.


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
O.k.,

here we are again. To plug in Pactor I have to use the USB Converter.
So I wasn't to sure what you meant by "just plug in Pactor, forget about the USB stuff"
But that is the outcome now.
There seem to be definitely discrepancies to what it should be.

O.k., here's the reading...

[ 62.647067] usb 5-1: Number of endpoints 2
[ 62.647070] usb 5-1: Endpoint 1 MaxPacketSize 64
[ 62.647072] usb 5-1: Endpoint 2 MaxPacketSize 64
[ 62.647075] usb 5-1: Setting MaxPacketSize 64
[ 62.650147] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 63.727451] pps_core: LinuxPPS API ver. 1 registered
[ 63.727456] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 63.727663] pps_ldisc: PPS line discipline registered
[ 63.729352] pps pps0: new PPS source usbserial0
[ 63.729363] pps pps0: source "/dev/ttyUSB0" added



And this is what I got using cat /usr/local/bin/comports | less
It does not assign Com 3 for Airport.


#!/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
:


and this is what I get if I unplug Pactor and plug my wireless router in, it can read it but it won't work on the Mac here. It does on the Toughbook though...,
very interesting...

pps0: new PPS source usbserial0
[ 1414.265157] pps pps0: source "/dev/ttyUSB0" added
[ 1414.266735] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 1414.266767] ftdi_sio 5-1:1.0: device disconnected
[ 1428.984196] usb 2-1: new high-speed USB device number 6 using ehci-pci
[ 1429.119780] usb 2-1: New USB device found, idVendor=12d1, idProduct=1446
[ 1429.119791] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1429.119799] usb 2-1: Product: HUAWEI Mobile Connect
[ 1429.119807] usb 2-1: Manufacturer: Huawei Incorporated
[ 1429.119814] usb 2-1: SerialNumber: 1234567890ABCDEF
[ 1429.123810] scsi5 : usb-storage 2-1:1.0
[ 1430.121880] scsi 5:0:0:0: CD-ROM HUAWEI Mass storage ffff PQ: 0 ANSI: 2
[ 1430.126693] sr1: scsi-1 drive
[ 1430.127000] sr 5:0:0:0: Attached scsi CD-ROM sr1
[ 1430.127254] sr 5:0:0:0: Attached scsi generic sg3 type 5
[ 1433.344938] usb 2-1: USB disconnect, device number 6
[ 1434.132232] usb 2-1: new high-speed USB device number 7 using ehci-pci
[ 1434.277516] usb 2-1: New USB device found, idVendor=12d1, idProduct=142d
[ 1434.277527] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1434.277535] usb 2-1: Product: HUAWEI Mobile Connect
[ 1434.277542] usb 2-1: Manufacturer: Huawei Incorporated
[ 1434.277549] usb 2-1: SerialNumber: 1234567890ABCDEF
[ 1434.289035] scsi6 : usb-storage 2-1:1.1
[ 1434.335055] usbcore: registered new interface driver option
[ 1434.335085] usbserial: USB Serial support registered for GSM modem (1-port)
[ 1434.336644] option 2-1:1.0: GSM modem (1-port) converter detected
[ 1434.336805] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 1434.336904] option 2-1:1.2: GSM modem (1-port) converter detected
[ 1434.337150] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 1434.362654] cdc_ether: probe of 2-1:1.3 failed with error -32
[ 1434.362696] usbcore: registered new interface driver cdc_ether
[ 1435.291329] scsi 6:0:0:0: CD-ROM HUAWEI Mass storage ffff PQ: 0 ANSI: 2
[ 1435.293305] scsi 6:0:0:1: Direct-Access HUAWEI Mass storage ffff PQ: 0 ANSI: 2
[ 1435.301338] sr1: scsi-1 drive
[ 1435.301674] sr 6:0:0:0: Attached scsi CD-ROM sr1
[ 1435.301875] sr 6:0:0:0: Attached scsi generic sg3 type 5
[ 1435.302333] sd 6:0:0:1: Attached scsi generic sg4 type 0
[ 1435.314284] sd 6:0:0:1: [sdc] Attached SCSI removable disk
nx@nx:~$


:o :idea: :roll: :D

Cheers,

Atmo,

SV Elfrun


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Now I fired up the toughbook.

Thatś the outcome here... Pactor running that is...


ffffff pref]
[ 44.237247] pcmcia_socket pcmcia_socket1: cs: memory probe 0x20000000-0x27ffffff:
[ 44.237272] excluding 0x20000000-0x27ffffff
[ 44.340139] device-mapper: multipath: version 1.5.1 loaded
[ 44.528547] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
[ 44.528558] ipw2100: Copyright(c) 2003-2006 Intel Corporation
[ 44.529625] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
[ 44.632188] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 44.716545] NET: Registered protocol family 23
[ 45.022563] nf_conntrack version 0.5.0 (7799 buckets, 31196 max)
[ 46.221706] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 46.536509] cfg80211: World regulatory domain updated:
[ 46.536522] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 46.536529] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 46.536535] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 46.536540] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 46.536546] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 46.536551] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 47.407453] snd_intel8x0 0000:00:1f.5: setting latency timer to 64
[ 48.240921] intel8x0_measure_ac97_clock: measured 56098 usecs (2703 samples)
[ 48.240932] intel8x0: clocking to 48000
[ 48.945880] init: failsafe main process (2795) killed by TERM signal
[ 58.873993] 8139too 0000:01:02.0 eth0: link down
[ 58.874140] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 58.875228] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 58.902598] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 58.903379] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 59.376834] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 68.532212] init: plymouth-stop pre-start process (3748) terminated with status 1
[ 88.804095] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 89.367628] lib80211_crypt: registered algorithm 'CCMP'
[ 90.316528] lib80211_crypt: registered algorithm 'TKIP'
[ 144.396089] usb 2-2: new full-speed USB device number 2 using uhci_hcd
[ 144.598047] usb 2-2: New USB device found, idVendor=0403, idProduct=6001
[ 144.598063] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 144.598074] usb 2-2: Product: USB Serial Converter
[ 144.598083] usb 2-2: Manufacturer: FTDI
[ 144.598092] usb 2-2: SerialNumber: FTFE8H5V
[ 144.816858] usbcore: registered new interface driver usbserial
[ 144.819180] usbcore: registered new interface driver usbserial_generic
[ 144.821968] usbserial: USB Serial support registered for generic
[ 144.829364] usbcore: registered new interface driver ftdi_sio
[ 144.831678] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 144.834589] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[ 144.834761] usb 2-2: Detected FT232RL
[ 144.834768] usb 2-2: Number of endpoints 2
[ 144.834774] usb 2-2: Endpoint 1 MaxPacketSize 64
[ 144.834781] usb 2-2: Endpoint 2 MaxPacketSize 64
[ 144.834786] usb 2-2: Setting MaxPacketSize 64
[ 144.837209] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0
[ 146.170317] pps_core: LinuxPPS API ver. 1 registered
[ 146.170327] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 146.174140] pps_ldisc: PPS line discipline registered
[ 146.174940] pps pps0: new PPS source usbserial0
[ 146.174959] pps pps0: source "/dev/ttyUSB0" added
nx@nx:~$

same story as always, com 3 not availlable...

:cry: :lol: :lol:


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
Return the output from:
Code:
sudo comports
It will look something like this
Quote:
moe@example:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
moe@example:~$


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
Quote:
[ 144.598047] usb 2-2: New USB device found, idVendor=0403, idProduct=6001
[ 144.598063] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 144.598074] usb 2-2: Product: USB Serial Converter
[ 144.598083] usb 2-2: Manufacturer: FTDI
[ 144.598092] usb 2-2: SerialNumber: FTFE8H5V
[ 144.816858] usbcore: registered new interface driver usbserial
[ 144.819180] usbcore: registered new interface driver usbserial_generic
[ 144.821968] usbserial: USB Serial support registered for generic
[ 144.829364] usbcore: registered new interface driver ftdi_sio
[ 144.831678] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 144.834589] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
...looks strangely similar to the troubles in http://navigatrix.net/viewtopic.php?f=4&t=598; as the FTDI devices don't seem to play well with the other children.


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Goood morning moe,
yeah we are on the bot right now. Well, it's nice to have the garden just 6km. away from the boat....

Here is the outcome. It never changed whether I had Pactor switched on or off, Airmail running or not. Airport states Com3 not available whether Pactor on or off.

Converter unplugged Airmail states no port at all.

So it must recognise something..... :roll:

x:~$

nx@nx:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
nx@nx:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
nx@nx:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
nx@nx:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
nx@nx:~$ sudo comports
/dev/com1 -> /dev/ttyS0
/dev/com2 -> /dev/ttyS1
/dev/com3 -> /dev/ttyUSB0
nx@nx:~$


Thanx


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
Quote:
Airport states Com3 not available
what do you mean when you say this?

Why is "Airport" even involved?

From Wikipedia: AirPort is the name given to a series of Apple products using the (Wi-Fi) protocols


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Apologies, Airmail it is... mea culpa! :oops:


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
When you try to open Airmail Terminal it states Com three not available.

Cheers


Top
   
 
 Post subject: Re: Pactor

Joined: 04 Nov 2010, 20:51
Posts: 1062
My guess is the module (driver) that's being called is not doing it's job properly.

The problem I'm running into is find something to go on.

The device reads out as idVendor=0403, idProduct=6001

Which is a Future Technology Devices chip that seems to be use in various USB/rs485|232 serial converters.

However, the SerialNumber: FTFE8H5V doesn't show up in any major search engine.

Is this thingo a converter/adaptor for your Pactor, or is it integral to the Pactor itself...i.e., out of the box?


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
O.k., this is a USB to seriell converter. SCS Pactor states they are using the same chip in their Pactor 2e usb model. Mine is the same chip in an external housing.
I'll try to attach the drivers.
I also just tried two different USB to Seriell Coverters and attach the dmesg files.
Outcome is the same like before.
The Moment I switch on Airmail and connect to Terminal it states com 3 not available and on the other ports it states set com error.

] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 23.984533] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 24.036041] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[ 24.289750] usb 3-1: New USB device found, idVendor=05ac, idProduct=8205
[ 24.289755] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 24.371231] usbcore: registered new interface driver btusb
[ 24.490653] init: failsafe main process (3043) killed by TERM signal
[ 26.106185] sky2 0000:03:00.0 eth2: enabling interface
[ 26.106630] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 26.108333] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 27.558679] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[ 27.559543] i915: render error detected, EIR: 0x00000010
[ 27.559547] i915: page table error
[ 27.559548] i915: PGTBL_ER: 0x00000100
[ 27.559552] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[ 146.284206] usb 3-2: new full-speed USB device number 4 using uhci_hcd
[ 146.440364] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
[ 146.440376] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 146.440384] usb 3-2: Product: USB-Serial Controller
[ 146.440391] usb 3-2: Manufacturer: Prolific Technology Inc.
[ 146.496419] usbcore: registered new interface driver usbserial
[ 146.496438] usbcore: registered new interface driver usbserial_generic
[ 146.496451] usbserial: USB Serial support registered for generic
[ 146.496753] usbcore: registered new interface driver pl2303
[ 146.496767] usbserial: USB Serial support registered for pl2303
[ 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

that is a different converter and the next one is a different converter again.

] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 23.627737] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -84
[ 23.676144] Unable to load isight firmware
[ 23.677027] usbcore: registered new interface driver isight_firmware
[ 23.712091] usb 3-1: USB disconnect, device number 2
[ 23.934702] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[ 23.975594] hda_codec: ALC889A: SKU not ready 0x400000f0
[ 23.984324] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 23.984533] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 24.036041] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[ 24.289750] usb 3-1: New USB device found, idVendor=05ac, idProduct=8205
[ 24.289755] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 24.371231] usbcore: registered new interface driver btusb
[ 24.490653] init: failsafe main process (3043) killed by TERM signal
[ 26.106185] sky2 0000:03:00.0 eth2: enabling interface
[ 26.106630] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 26.108333] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 27.558679] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[ 27.559543] i915: render error detected, EIR: 0x00000010
[ 27.559547] i915: page table error
[ 27.559548] i915: PGTBL_ER: 0x00000100
[ 27.559552] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[ 146.284206] usb 3-2: new full-speed USB device number 4 using uhci_hcd
[ 146.440364] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
[ 146.440376] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 146.440384] usb 3-2: Product: USB-Serial Controller
[ 146.440391] usb 3-2: Manufacturer: Prolific Technology Inc.
[ 146.496419] usbcore: registered new interface driver usbserial
[ 146.496438] usbcore: registered new interface driver usbserial_generic
[ 146.496451] usbserial: USB Serial support registered for generic
[ 146.496753] usbcore: registered new interface driver pl2303
[ 146.496767] usbserial: USB Serial support registered for pl2303
[ 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
[ 542.048148] usb 3-2: USB disconnect, device number 4
[ 542.050168] pps pps0: removed
[ 542.050417] pps pps0: new PPS source usbserial0
[ 542.050432] pps pps0: source "/dev/ttyUSB0" added
[ 542.050606] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[ 542.050633] pl2303 3-2:1.0: device disconnected
[ 563.916168] usb 3-2: new full-speed USB device number 5 using uhci_hcd
[ 564.073255] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
[ 564.073267] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 564.073275] usb 3-2: Product: USB-Serial Controller
[ 564.073282] usb 3-2: Manufacturer: Prolific Technology Inc.
[ 564.075263] pl2303 3-2:1.0: pl2303 converter detected
[ 564.087492] usb 3-2: pl2303 converter now attached to ttyUSB1
[ 565.126051] pps pps1: new PPS source usbserial1
[ 565.126074] pps pps1: source "/dev/ttyUSB1" added
[ 634.014252] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 634.014263] ata3.00: waking up from sleep
[ 634.014287] ata3: soft resetting link
[ 637.078535] ata3.00: configured for UDMA/133
[ 637.078585] ata3: EH complete
[ 693.080272] usb 3-2: USB disconnect, device number 5
[ 693.081922] pps pps1: removed
[ 693.084882] pps pps1: new PPS source usbserial1
[ 693.084899] pps pps1: source "/dev/ttyUSB1" added
[ 693.085078] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1
[ 693.085106] pl2303 3-2:1.0: device disconnected
[ 740.144218] usb 3-2: new full-speed USB device number 6 using uhci_hcd
[ 740.306367] usb 3-2: New USB device found, idVendor=067b, idProduct=2303
[ 740.306377] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 740.306386] usb 3-2: Product: USB-Serial Controller
[ 740.306393] usb 3-2: Manufacturer: Prolific Technology Inc.
[ 740.309376] pl2303 3-2:1.0: pl2303 converter detected
[ 740.321606] usb 3-2: pl2303 converter now attached to ttyUSB2
[ 741.356502] pps pps2: new PPS source usbserial2
[ 741.356528] pps pps2: source "/dev/ttyUSB2" added
nx@nx:~$


Hmm, looks like a problem with Airmail communicating with NX.
I tried 3 different converters now, Airmail alwazs states com 3 not available, using other comports in Airmail it states set com error.
I will trz to attach the linux drivers I got with mz standard converter I am normallz using.
What still puzzels me is that it is running fine on XP.

Seqence used was Start Nx, plug in converter, attach Pactor to Converter, start airmail.
Same sequence was used on all three converters.
What a riddle......


Top
   
 
 Post subject: Re: Pactor

Joined: 21 Feb 2013, 12:46
Posts: 76
Now the Linux drivers which came with the product....

I attached the files.

Where abouts are you situated Moe? I think I owe you a dinner already....
cheers,

Atmo :)
Attachment:
ftdi_sio.h [38.17 KiB]
Downloaded 161 times
Attachment:
ftdi_sio.c [80.67 KiB]
Downloaded 167 times


Top
   
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 93 posts ]  Go to page 1, 2, 3, 4, 5  Next


Search for:
cron

Credits © 2010 - 2023