[chirp_users] Problem with a Mac
Hi Everyone
Well my main computer is a Mac and I can't get it to Read from a Yaesu VX-8G. I have kk7ds python in there And I think my driver is correct, it is /dev/cu.PL2303-002112FD
I turn on the radio wed have the F/W pressed CLONE is displayed I select the BAND button and wait and it displays ERROR
Can anybody give my any hints I can do?
WB0ZUR
Denton Larson wb0zur@gmail.com
I was under the impression that the port showed as
/dev/cu.usbserial
It's that was on my MacBook Pro OSX 10.8.2 64 bit.
But then again it doesn't work on mine either :)
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 5, 2013, at 1:05 PM, Denton Larson wb0zur@gmail.com wrote:
Hi Everyone
Well my main computer is a Mac and I can't get it to Read from a Yaesu VX-8G. I have kk7ds python in there And I think my driver is correct, it is /dev/cu.PL2303-002112FD
I turn on the radio wed have the F/W pressed CLONE is displayed I select the BAND button and wait and it displays ERROR
Can anybody give my any hints I can do?
WB0ZUR
Denton Larson wb0zur@gmail.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Tue, Feb 5, 2013 at 10:05 AM, Denton Larson wb0zur@gmail.com wrote:
Hi Everyone
Well my main computer is a Mac and I can't get it to Read from a Yaesu VX-8G. I have kk7ds python in there And I think my driver is correct, it is /dev/cu.PL2303-002112FD
I turn on the radio wed have the F/W pressed CLONE is displayed I select the BAND button and wait and it displays ERROR
Can anybody give my any hints I can do?
You don't mention clicking Download from Radio in Chirp. Do this. Once Chirp is waiting, click the BAND button. If your cable and driver work, it will download successfully.
On Tue, Feb 5, 2013 at 2:42 PM, Phaeton phaeton@neo.rr.com wrote:
I was under the impression that the port showed as
/dev/cu.usbserial
This just depends on the driver. Some drivers use different names.
Tom KD7LXL
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name. I know from my linux experience dating back to 1998 that from what I remember most devices carried a system device name. And this device I referred to was for the latest driver from prolific.com.tw.
On Tue, Feb 5, 2013 at 2:42 PM, Phaeton phaeton@neo.rr.com wrote:
I was under the impression that the port showed as
/dev/cu.usbserial
This just depends on the driver. Some drivers use different names.
On Wed, Feb 6, 2013 at 12:57 PM, Phaeton phaeton@neo.rr.com wrote:
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name.
On Linux, udev usually chooses the device name. On OS X, the driver tells the OS what name it wants.
FTDI usually shows up as /dev/cu.usbserial-xxxxxxxx, where xxxxxxxx is either the device's serial number or, for unserialized devices, a location string that depends on which USB port your device is connected to.
The Prolific PL2303 driver enumerates devices at /dev/cu.usbserial.
I think /dev/cu.PL2303-XXXXXXXX is associated with the open source PL2303 project.
Tom KD7LXL
Thanks for the info, I still have a Windows 7 netbook, 15.4" Asus laptop, a Toshiba 15" laptop, and a quad core hombrew AMD on Asus main board running 4 ghz per core.
But my main computer is the 2011 MacBook 15.4" quad. I love the unix OS. Spent a decade supporting SCO and BSD and Novell 3xx and 4xx. Started out when networks were Thomas Conrad 100 mbps coax on DOS and business software from IBM and Macola.
Fun stuff but I was not involved in any coding other than being an official beta for NT4. So I love learning and asking questions as you might have guessed by now.
Will I Am.
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 6, 2013, at 5:01 PM, Tom Hayward esarfl@gmail.com wrote:
On Wed, Feb 6, 2013 at 12:57 PM, Phaeton phaeton@neo.rr.com wrote:
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name.
On Linux, udev usually chooses the device name. On OS X, the driver tells the OS what name it wants.
FTDI usually shows up as /dev/cu.usbserial-xxxxxxxx, where xxxxxxxx is either the device's serial number or, for unserialized devices, a location string that depends on which USB port your device is connected to.
The Prolific PL2303 driver enumerates devices at /dev/cu.usbserial.
I think /dev/cu.PL2303-XXXXXXXX is associated with the open source PL2303 project.
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
All that stuff below is completely foreign to me, but I wanted you to know that on my MAC, my (working perfectly) port is /dev/cu.PL2303-0000203A I have no idea if that helps at all...
Jeff
On Feb 6, 2013, at 3:24 PM, Phaeton wrote:
Thanks for the info, I still have a Windows 7 netbook, 15.4" Asus laptop, a Toshiba 15" laptop, and a quad core hombrew AMD on Asus main board running 4 ghz per core.
But my main computer is the 2011 MacBook 15.4" quad. I love the unix OS. Spent a decade supporting SCO and BSD and Novell 3xx and 4xx. Started out when networks were Thomas Conrad 100 mbps coax on DOS and business software from IBM and Macola.
Fun stuff but I was not involved in any coding other than being an official beta for NT4. So I love learning and asking questions as you might have guessed by now.
Will I Am.
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 6, 2013, at 5:01 PM, Tom Hayward esarfl@gmail.com wrote:
On Wed, Feb 6, 2013 at 12:57 PM, Phaeton phaeton@neo.rr.com wrote:
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name.
On Linux, udev usually chooses the device name. On OS X, the driver tells the OS what name it wants.
FTDI usually shows up as /dev/cu.usbserial-xxxxxxxx, where xxxxxxxx is either the device's serial number or, for unserialized devices, a location string that depends on which USB port your device is connected to.
The Prolific PL2303 driver enumerates devices at /dev/cu.usbserial.
I think /dev/cu.PL2303-XXXXXXXX is associated with the open source PL2303 project.
Tom KD7LXL _______________________________________________ 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
Yeah sure it is a help to everyone. What I was trying to figure out for my further education is how these ports when opened by the device plugged in and installed were named in /dev/. Tom pretty much had the answer. I'm a very avid linux user and was comparing the port device name be it USB, SATA, Firewire, PCIe etc.. So it seemed a bit odd to to have the enumerated USB to serial device to convey an actual name from the driver developer rather than a standard name that linux uses. Occasionally I have to remind myself that OSX 10.8.2 is now unix and not linux and while very similar, still possess differences as in this port name convention.
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 6, 2013, at 7:22 PM, Jeffrey Deuel Jeff@deuelgroup.com wrote:
All that stuff below is completely foreign to me, but I wanted you to know that on my MAC, my (working perfectly) port is /dev/cu.PL2303-0000203A I have no idea if that helps at all...
Jeff
On Feb 6, 2013, at 3:24 PM, Phaeton wrote:
Thanks for the info, I still have a Windows 7 netbook, 15.4" Asus laptop, a Toshiba 15" laptop, and a quad core hombrew AMD on Asus main board running 4 ghz per core.
But my main computer is the 2011 MacBook 15.4" quad. I love the unix OS. Spent a decade supporting SCO and BSD and Novell 3xx and 4xx. Started out when networks were Thomas Conrad 100 mbps coax on DOS and business software from IBM and Macola.
Fun stuff but I was not involved in any coding other than being an official beta for NT4. So I love learning and asking questions as you might have guessed by now.
Will I Am.
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 6, 2013, at 5:01 PM, Tom Hayward esarfl@gmail.com wrote:
On Wed, Feb 6, 2013 at 12:57 PM, Phaeton phaeton@neo.rr.com wrote:
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name.
On Linux, udev usually chooses the device name. On OS X, the driver tells the OS what name it wants.
FTDI usually shows up as /dev/cu.usbserial-xxxxxxxx, where xxxxxxxx is either the device's serial number or, for unserialized devices, a location string that depends on which USB port your device is connected to.
The Prolific PL2303 driver enumerates devices at /dev/cu.usbserial.
I think /dev/cu.PL2303-XXXXXXXX is associated with the open source PL2303 project.
Tom KD7LXL _______________________________________________ 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)
-
Denton Larson -
Jeffrey Deuel -
Phaeton -
Tom Hayward