[chirp_users] Dumb 8900 queary
*Anybody have an 8900 that could walk me through the process of using chirp? The Linux one. **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
Anybody have an 8900 that could walk me through the process of using chirp? The Linux one.
What are you looking for exactly? See if this page helps:
http://chirp.danplanet.com/content/beginners-guide
In case you're not sure, your 8900 is a clone type radio.
*Well * *1 how do you tell what port to use?* *2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows "cloning". **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 1:18 PM, Dan Smith dsmith@danplanet.com wrote:
Anybody have an 8900 that could walk me through the process of using chirp? The Linux one.
What are you looking for exactly? See if this page helps:
http://chirp.danplanet.com/content/beginners-guide
In case you're not sure, your 8900 is a clone type radio.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
1 how do you tell what port to use?
I think you said you were using Linux. If you're using a USB serial adapter, then you want /dev/ttyUSB0 (assuming you only have one attached). If you're using the first real serial port, then you'll want /dev/ttyS0.
2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows "cloning".
You do get the special multi-tone beep and then get dropped into the alternate set menu, right? The cloning mode is the last one in the list, if I recall correctly. That means a single turn to the left will get you there. Then you have to press another button to actually reboot into the cloning menu and then yet another to put it into RX or TX mode.
* * On Mon, Jun 6, 2011 at 2:05 PM, Dan Smith dsmith@danplanet.com wrote:
1 how do you tell what port to use?
I think you said you were using Linux. If you're using a USB serial adapter, then you want /dev/ttyUSB0 (assuming you only have one attached). If you're using the first real serial port, then you'll want /dev/ttyS0.
Ok it's not showing an extra usb so I'll try ttyS0
2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows
"cloning".
You do get the special multi-tone beep and then get dropped into the alternate set menu, right? The cloning mode is the last one in the list, if I recall correctly. That means a single turn to the left will get you there. Then you have to press another button to actually reboot into the cloning menu and then yet another to put it into RX or TX mode.
OK is the alternate set when you hold the V/m down while turning it on?
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
* * On Mon, Jun 6, 2011 at 3:51 PM, Dan Smith dsmith@danplanet.com wrote:
That's the alternate set menu, yeah.
Got in clone mode and when I hit the left v/m tx appered for a sec then
error Alvin
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Got in clone mode and when I hit the left v/m tx appered for a sec then error
That means it didn't hear back from chirp after trying to start the transfer. That means either chirp is not yet ready to receive (i.e. you didn't hit the okay button yet) or it's listening on the wrong serial port.
*OK ls /dev/USB* got * * * * alvin@dittohead:~/POD/HDC$ ls /dev/USB* ls: cannot access /dev/USB*: No such file or directory
but lsusb got
alvin@dittohead:~/POD/HDC$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 009: ID 13fd:1340 Initio Corporation Bus 004 Device 007: ID 03f0:3f11 Hewlett-Packard PSC-1315/PSC-1317 Bus 004 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 003: ID 041e:4036 Creative Technology, Ltd Webcam Live!/Live! Pro Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub without alvin@dittohead:~/POD/HDC$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 009: ID 13fd:1340 Initio Corporation Bus 004 Device 007: ID 03f0:3f11 Hewlett-Packard PSC-1315/PSC-1317 Bus 004 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 003: ID 041e:4036 Creative Technology, Ltd Webcam Live!/Live! Pro Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub with...........maybe a loose plug cause I see no difference.
I have a cable with a 8900 data jack on 1 end & usb on the other
**Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 4:07 PM, Dan Smith dsmith@danplanet.com wrote:
Got in clone mode and when I hit the left v/m tx appered for a sec then error
That means it didn't hear back from chirp after trying to start the transfer. That means either chirp is not yet ready to receive (i.e. you didn't hit the okay button yet) or it's listening on the wrong serial port.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
* alvin@dittohead:~/POD/HDC$ ls /dev/ttyUSB* /dev/ttyUSB0 /dev/ttyUSB1 That's the 2 Ext HD partitions. I'll see if I can get someone to check (wiggle) the plugs (I have 5% use of 1 hand) Thanks **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 4:25 PM, Dan Smith dsmith@danplanet.com wrote:
ls /dev/USB*
That's not the command I suggested that you run. I said run this:
ls /dev/ttyUSB*
but lsusb got
lsusb doesn't show device names, so it won't help us here.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
/dev/ttyUSB0 /dev/ttyUSB1 That's the 2 Ext HD partitions.
No, those are USB-to-serial adapters.
I'll see if I can get someone to check (wiggle) the plugs
They're clearly connected and identified by the OS. Have you tried CHIRP against both of them?
(I have 5% use of 1 hand)
For what it's worth, all of the Icom radios are fully remotely addressable. That means you plug in the radio and CHIRP does the rest. It can place the radio into clone mode in both directions and handle multiple clone upload/download operations without you ever touching the radio. They don't make something to compete with the 8900, but I just thought I'd point that out.
* * On Mon, Jun 6, 2011 at 10:28 PM, Dan Smith dsmith@danplanet.com wrote:
/dev/ttyUSB0 /dev/ttyUSB1 That's the 2 Ext HD partitions.
No, those are USB-to-serial adapters.
I'll see if I can get someone to check (wiggle) the plugs
They're clearly connected and identified by the OS. Have you tried CHIRP against both of them?
Yup just did got an error on both
(I have 5% use of 1 hand)
For what it's worth, all of the Icom radios are fully remotely
Ya wish I had a 706mkiig buuuut,
Hay thanks for all the emails. I'll try plugging it in the front usb jack tomorrow. Alvin
Hi Alvin,
Forgive me if you know all of this already: Linux allocates and removes the ttyUSB devices "on the fly" as they are inserted or removed. It usually adds them, in order of insertion, as ttyUSB0, ttyUSB1, etc. regardless of which USB connector they are plugged into. At least that's been my experience with the Ubuntu and Fedora distributions. I find it's very easy to get the ttyUSBx devices mixed up if you have more than one, especially when troubleshooting a problem. An example, FWIW:
If you: 1. You plug in a USB serial device. Linux adds it as ttyUSB0 2. You start an application (let's use chirp for this example). 3. Chirp sees the device as ttyUSB0 and opens it. 4. The device appears to get "hung" for one reason or another. 4. The USB adapter is unplugged, then reinserted. 5. Linux makes the same USB adapter be ttyUSB1 this time because Linux thinks ttyUSB0 is still in use as far as Linux knows.
That's why I usually run: dmesg | grep ttyUSB when I remove or insert USB serial adapters to verify what ttyUSB device Linux thinks it is.
Do this before you start chirp so you know you've selected the correct USB device. If you only have one USB serial adapter it should be the only ttyUSB device chirp lists in the selection menu.
Happy testing! Mike, N0SO (using a real keyboard this time)
--- On Tue, 6/7/11, Alvin Koffman ka9qlq@gmail.com wrote:
From: Alvin Koffman ka9qlq@gmail.com Subject: Re: [chirp_users] Dumb 8900 queary To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Date: Tuesday, June 7, 2011, 4:06 AM
On Mon, Jun 6, 2011 at 10:28 PM, Dan Smith dsmith@danplanet.com wrote:
/dev/ttyUSB0 /dev/ttyUSB1
That's the 2 Ext HD partitions.
No, those are USB-to-serial adapters.
I'll see if I can get someone to check (wiggle) the plugs
They're clearly connected and identified by the OS. Have you tried
CHIRP against both of them?
Yup just did got an error on both
(I have 5% use of 1 hand)
For what it's worth, all of the Icom radios are fully remotely Ya wish I had a 706mkiig buuuut, Hay thanks for all the emails. I'll try plugging it in the front usb jack tomorrow. Alvin
-----Inline Attachment Follows-----
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
*Well I moved the cord to the front usb plugs and* *** * * alvin@dittohead:~/POD/HDC$ ls /dev/ttyUSB* /dev/ttyUSB0 /dev/ttyUSB1 alvin@dittohead:~/POD/HDC$ dmesg | grep ttyUSB [928137.560437] type=1503 audit(1306535091.695:33): operation="open" pid=5141 parent=5136 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1639614.301890] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [1639614.750609] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0 [1639988.405981] type=1503 audit(1307246960.387:40): operation="open" pid=8690 parent=8685 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1701142.174785] usb 3-2: pl2303 converter now attached to ttyUSB1 [1844891.613682] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1 [1844912.295495] usb 5-2: pl2303 converter now attached to ttyUSB1
And they still wont talk to eachother **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Tue, Jun 7, 2011 at 9:53 AM, Mike Heitmann n0so@att.net wrote:
Hi Alvin,
Forgive me if you know all of this already: Linux allocates and removes the ttyUSB devices "on the fly" as they are inserted or removed. It usually adds them, in order of insertion, as ttyUSB0, ttyUSB1, etc. regardless of which USB connector they are plugged into. At least that's been my experience with the Ubuntu and Fedora distributions. I find it's very easy to get the ttyUSBx devices mixed up if you have more than one, especially when troubleshooting a problem. An example, FWIW:
If you:
- You plug in a USB serial device. Linux adds it as ttyUSB0
- You start an application (let's use chirp for this example).
- Chirp sees the device as ttyUSB0 and opens it.
- The device appears to get "hung" for one reason or another.
- The USB adapter is unplugged, then reinserted.
- Linux makes the same USB adapter be ttyUSB1 this time because Linux
thinks ttyUSB0 is still in use as far as Linux knows.
That's why I usually run: dmesg | grep ttyUSB when I remove or insert USB serial adapters to verify what ttyUSB device Linux thinks it is.
Do this before you start chirp so you know you've selected the correct USB device. If you only have one USB serial adapter it should be the only ttyUSB device chirp lists in the selection menu.
Happy testing! Mike, N0SO (using a real keyboard this time)
--- On *Tue, 6/7/11, Alvin Koffman ka9qlq@gmail.com* wrote:
From: Alvin Koffman ka9qlq@gmail.com Subject: Re: [chirp_users] Dumb 8900 queary To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Date: Tuesday, June 7, 2011, 4:06 AM
On Mon, Jun 6, 2011 at 10:28 PM, Dan Smith <dsmith@danplanet.comhttp://mc/compose?to=dsmith@danplanet.com
wrote:
/dev/ttyUSB0 /dev/ttyUSB1 That's the 2 Ext HD partitions.
No, those are USB-to-serial adapters.
I'll see if I can get someone to check (wiggle) the plugs
They're clearly connected and identified by the OS. Have you tried CHIRP against both of them?
Yup just did got an error on both
(I have 5% use of 1 hand)
For what it's worth, all of the Icom radios are fully remotely
Ya wish I had a 706mkiig buuuut,
Hay thanks for all the emails. I'll try plugging it in the front usb jack tomorrow. Alvin
-----Inline Attachment Follows-----
chirp_users mailing list chirp_users@intrepid.danplanet.comhttp://mc/compose?to=chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
[1844912.295495] usb 5-2: pl2303 converter now attached to ttyUSB1
And they still wont talk to eachother
You've selected Yaesu FT-8900 in the chirp clone settings dialog, right?
You hit okay on that box and then hit the button to start the TX on the radio side, is that right?
Did you have the radio at the clone screen before clicking okay, or did you click okay on chirp and then do the entire special boot procedure on the radio?
* * On Tue, Jun 7, 2011 at 10:29 AM, Dan Smith dsmith@danplanet.com wrote:
[1844912.295495] usb 5-2: pl2303 converter now attached to ttyUSB1
And they still wont talk to eachother
You've selected Yaesu FT-8900 in the chirp clone settings dialog, right?
Check
You hit okay on that box and then hit the button to start the TX on the radio side, is that right?
Check
Did you have the radio at the clone screen before clicking okay,
Check Alvin
As an FYI, from the dmesg info you provided:
The cable that got unplugged and plugged back in is /dev/ttyUSB1 and that's looks like the one you should be using with chirp.
ttyUSB0, the first USB serial port that gets plugged in is getting used by the Linux printing system CUPS. I don't know if you actually have a serially attached printer or if CUPS is misconfigured to use that port.
You have two USB to serial adapters on your system, one made by FTDI and the other a Prolific PL-2303. As others have mentioned the name of the port is going to be dependent on the order they get plugged in so play close attention to which is which and watch out for CUPS opening the wrong one.
You might want to try shutting down cupsd when you are trying to debug the radio connectivity.
Hope this helps, --Rob
On 6/7/2011 10:25 AM, Alvin Koffman wrote:
alvin@dittohead:~/POD/HDC$ ls /dev/ttyUSB* /dev/ttyUSB0 /dev/ttyUSB1 alvin@dittohead:~/POD/HDC$ dmesg | grep ttyUSB [928137.560437] type=1503 audit(1306535091.695:33): operation="open" pid=5141 parent=5136 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1639614.301890] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [1639614.750609] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0 [1639988.405981] type=1503 audit(1307246960.387:40): operation="open" pid=8690 parent=8685 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1701142.174785] usb 3-2: pl2303 converter now attached to ttyUSB1 [1844891.613682] pl2303 ttyUSB1: pl2303 converter now disconnected from ttyUSB1 [1844912.295495] usb 5-2: pl2303 converter now attached to ttyUSB1
And they still wont talk to eachother **Alvin Koffman
*If you like computer viruses stay with windows but If you want to be virus free try.*
On Tue, Jun 7, 2011 at 9:53 AM, Mike Heitmann <n0so@att.net mailto:n0so@att.net> wrote:
Hi Alvin, Forgive me if you know all of this already: Linux allocates and removes the ttyUSB devices "on the fly" as they are inserted or removed. It usually adds them, in order of insertion, as ttyUSB0, ttyUSB1, etc. regardless of which USB connector they are plugged into. At least that's been my experience with the Ubuntu and Fedora distributions. I find it's very easy to get the ttyUSBx devices mixed up if you have more than one, especially when troubleshooting a problem. An example, FWIW: If you: 1. You plug in a USB serial device. Linux adds it as ttyUSB0 2. You start an application (let's use chirp for this example). 3. Chirp sees the device as ttyUSB0 and opens it. 4. The device appears to get "hung" for one reason or another. 4. The USB adapter is unplugged, then reinserted. 5. Linux makes the same USB adapter be ttyUSB1 this time because Linux thinks ttyUSB0 is still in use as far as Linux knows. That's why I usually run: dmesg | grep ttyUSB when I remove or insert USB serial adapters to verify what ttyUSB device Linux thinks it is. Do this before you start chirp so you know you've selected the correct USB device. If you only have one USB serial adapter it should be the only ttyUSB device chirp lists in the selection menu. Happy testing! Mike, N0SO (using a real keyboard this time) --- On *Tue, 6/7/11, Alvin Koffman /<ka9qlq@gmail.com <mailto:ka9qlq@gmail.com>>/* wrote: From: Alvin Koffman <ka9qlq@gmail.com <mailto:ka9qlq@gmail.com>> Subject: Re: [chirp_users] Dumb 8900 queary To: "Discussion of CHIRP" <chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com>> Date: Tuesday, June 7, 2011, 4:06 AM * * On Mon, Jun 6, 2011 at 10:28 PM, Dan Smith <dsmith@danplanet.com <http://mc/compose?to=dsmith@danplanet.com>> wrote: > /dev/ttyUSB0 /dev/ttyUSB1 > That's the 2 Ext HD partitions. No, those are USB-to-serial adapters. > I'll see if I can get someone to check (wiggle) the plugs They're clearly connected and identified by the OS. Have you tried CHIRP against both of them? Yup just did got an error on both > (I have 5% use of 1 hand) For what it's worth, all of the Icom radios are fully remotely Ya wish I had a 706mkiig buuuut, Hay thanks for all the emails. I'll try plugging it in the front usb jack tomorrow. Alvin -----Inline Attachment Follows----- _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <http://mc/compose?to=chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Tue, Jun 7, 2011 at 10:37 AM, Robert Terzi rct@r-t.org wrote:
As an FYI, from the dmesg info you provided:
The cable that got unplugged and plugged back in is /dev/ttyUSB1 and that's looks like the one you should be using with chirp.
Check
You might want to try shutting down cupsd when you are trying to debug the radio connectivity.
Is there an easy way to do this?
Alvin
On 6/7/2011 10:51 AM, Alvin Koffman wrote:
You might want to try shutting down cupsd when you are trying to debug the radio connectivity.
Is there an easy way to do this?
That depends on your Linux distriution. You might have a GUI to stop the printing system or from the command line something like:
/etc/init.d/cups stop
service cups stop
If you can't figure out how to shutdown the service using it's management scripts you could probably just kill all instances of cupsdwith:
killall cupsd
Of course don't forget to get that all restarted before the next time you want to print.
--Rob
*Ya I use Kubuntu 10.04 (wish I still had 8.04) I'll check systems settings **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Tue, Jun 7, 2011 at 11:22 AM, Robert Terzi rct@r-t.org wrote:
On 6/7/2011 10:51 AM, Alvin Koffman wrote:
You might want to try shutting down cupsd when you are trying to debug the radio connectivity.
Is there an easy way to do this?
That depends on your Linux distriution. You might have a GUI to stop the printing system or from the command line something like:
/etc/init.d/cups stop service cups stopIf you can't figure out how to shutdown the service using it's management scripts you could probably just kill all instances of cupsdwith:
killall cupsdOf course don't forget to get that all restarted before the next time you want to print.
--Rob
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
For a USB serial adapter, from shell prompt try:
dmeg | grep ttyUSBOn
That should list all of the active USB serial devices.
Mike, N0SO
Sent from my iPhone
On Jun 6, 2011, at 12:56 PM, Alvin Koffman ka9qlq@gmail.com wrote:
Well 1 how do you tell what port to use? 2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows "cloning". Alvin Koffman If you like computer viruses stay with windows but If you want to be virus free try. http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 1:18 PM, Dan Smith dsmith@danplanet.com wrote:
Anybody have an 8900 that could walk me through the process of using chirp? The Linux one.
What are you looking for exactly? See if this page helps:
http://chirp.danplanet.com/content/beginners-guide
In case you're not sure, your 8900 is a clone type radio.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Oops... That should have been flesh | grep ttyUSB Sent from my iPhone
On Jun 6, 2011, at 2:42 PM, Mike Heitmann n0so@att.net wrote:
For a USB serial adapter, from shell prompt try:
dmeg | grep ttyUSBOn
That should list all of the active USB serial devices.
Mike, N0SO
Sent from my iPhone
On Jun 6, 2011, at 12:56 PM, Alvin Koffman ka9qlq@gmail.com wrote:
Well 1 how do you tell what port to use? 2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows "cloning". Alvin Koffman If you like computer viruses stay with windows but If you want to be virus free try. http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 1:18 PM, Dan Smith dsmith@danplanet.com wrote:
Anybody have an 8900 that could walk me through the process of using chirp? The Linux one.
What are you looking for exactly? See if this page helps:
http://chirp.danplanet.com/content/beginners-guide
In case you're not sure, your 8900 is a clone type radio.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Oops... That should have been flesh| grep ttyUSB
Heh, let me and my keyboard lend some assistance :)
I think he means:
dmesg | grep ttyUSB
that should work, but chirp should be listing everything in the drop-down anyway, so if you only have one adapter connected, it will be the only /dev/ttyUSB option in the list.
*Grin. I can't keep that strait ether.* * * * alvin@dittohead:~/POD/HDC$ dmesg | grep ttyUSB [928137.560437] type=1503 audit(1306535091.695:33): operation="open" pid=5141 parent=5136 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1639614.301890] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [1639614.750609] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0 [1639988.405981] type=1503 audit(1307246960.387:40): operation="open" pid=8690 parent=8685 profile="/usr/sbin/cupsd" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/dev/ttyUSB0" [1701142.174785] usb 3-2: pl2303 converter now attached to ttyUSB1
I have a usb mouse, printer, ext. HD split in to 2 partitions (usb0 & usb1) a usb controled relay box, and the 8900 cable........did I forget something?????? **Alvin Koffman *
*If you like computer viruses stay with windows but If you want to be virus free try.*
*http://www.puppylinux.com/* http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 3:48 PM, Dan Smith dsmith@danplanet.com wrote:
Oops... That should have been flesh| grep ttyUSB
Heh, let me and my keyboard lend some assistance :)
I think he means:
dmesg | grep ttyUSB
that should work, but chirp should be listing everything in the drop-down anyway, so if you only have one adapter connected, it will be the only /dev/ttyUSB option in the list.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I have a usb mouse, printer, ext. HD split in to 2 partitions (usb0 & usb1) a usb controled relay box, and the 8900 cable........did I forget something??????
Most of that won't show up as a USB serial device. I'm still looking for you to say what kind of cable and adapter you're using. Perhaps you're using something that has a USB connector on one end and the 8900 connector on the other?
If you unplug your 8900, do this:
ls /dev/ttyUSB*
then plug it back in and run that again, you should be able to see which device pops up when you plugged in your cable. That is the one you should use.
The other one is probably your relay box. Note that the devices are assigned in order. So, if you plug them in in a different order tomorrow, you'll need to change what you tell chirp to use.
Ya know, sometimes I would like to *choke* this iPhone spell correction "feature". What I wanted was:
dmesg | grep ttyUSB
Mike Sent from my iPhone
On Jun 6, 2011, at 2:45 PM, Mike Heitmann n0so@att.net wrote:
Oops... That should have been flesh | grep ttyUSB Sent from my iPhone
On Jun 6, 2011, at 2:42 PM, Mike Heitmann n0so@att.net wrote:
For a USB serial adapter, from shell prompt try:
dmeg | grep ttyUSBOn
That should list all of the active USB serial devices.
Mike, N0SO
Sent from my iPhone
On Jun 6, 2011, at 12:56 PM, Alvin Koffman ka9qlq@gmail.com wrote:
Well 1 how do you tell what port to use? 2 How do you set up the radio? I tried turning the rig on while holding down on the left V/M as the book says, but nothing on rig shows "cloning". Alvin Koffman If you like computer viruses stay with windows but If you want to be virus free try. http://www.puppylinux.com/
On Mon, Jun 6, 2011 at 1:18 PM, Dan Smith dsmith@danplanet.com wrote:
Anybody have an 8900 that could walk me through the process of using chirp? The Linux one.
What are you looking for exactly? See if this page helps:
http://chirp.danplanet.com/content/beginners-guide
In case you're not sure, your 8900 is a clone type radio.
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (4)
-
Alvin Koffman -
Dan Smith -
Mike Heitmann -
Robert Terzi