I have been trying to figure out how to find out what number should be set, that is, 5331, 5332, 5333, etc.Now there is new Mac native software available (Chirp and not so new RUMtrol7000) and as Parallels only runs on my Mac Pro at home, I wanted to be able to use the new Mac native software on my MBP when I am not at home. Wide Compatibility, The USB DB9 adapter is with Prolific PL-2303 Chipset, compatible for Windows 10 /8.1 /8 /7 /Vista /XP /2000 and Mac OS X 10.6, Linux, etc. I have Parallels and the Window software to connect my Mac/Parallels to my radio so that I can program the radio's memories for my purposes - it works - so I know the USB port, cable and my radio are not the problem.If the FTDI, Silicon Labs or Prolific USB drivers do not work for your scanner, its most likely you need this driver Windows CH340 USB to Serial Driver: Link 1: For Windows XP/7/8.1/10 (32/64 bit) Mac OS CH340 USB to Serial Driver: Link 1: Supports 32/64 bit: Linux CH340 USB to Serial Driver: Link 1 ELM327 OBD2 USB Cable Driver Downloads. The Mac OSX System Information app recognises the cable when it is plugged in.
![]() Prolific (Clone) Usb Cable Ation For A Code From TheLoaded up the software, could choose the VCP and it works.happy days! Until Apple does something else.I also did some investigating and this issue is certainly providing a good education in how the Mac handles these things. I updated the plist for the 2 devices that i want to use and saved the file back to its original position.I used part of the code from the above listed website to check for the existing of VCPs and to a create VCP for each cable.Unplugged the cables, rebooted and plugged the cable back in. The above referenced PDF has the code that you need to add but when editing the plist I could see that code for other devices. I made a copy of the FTDI OEM driver/plist and saved it to another directory (2 times in separate folders - one as a "master" and the other to edit/test). For modifying the plist file you need to convert that number to decimal format - I searched for and used an online converter. It had the PID and VID in hexadecimal format.Once I have everything thoroughly tested I'll post the details.Thanks so much for the information. That seems to work with all my devices however I still need to verify that each one functions properly.Next I'm going to look over the technical note you mentioned and the link you recommended and try taking the approach you outlined to see how that compares with my previous two experiments. Then I disabled the Apple driver and installed the latest version FTDI VCP driver.I have a USB Standard B plug on the back of my Pactor, so I don't need a serial adapter- just a Standard USB A to USB B plug.When I plug in my Pactor I can also see that the System Information is recognizing the device.But, in Terminal, when I run the "cd /dev" command, then type "ls," I see that no new serial port has been created. I already have Parallels installed on my laptop to help bridge the gap. I have an i-com 802 ssb radio, and a MacBook Pro Retina running on 10.9 OSX.I'm having a difficult time getting my Pactor modem to communicate with my MBP. I have a Pactor II-usb modem, which I would like to use to receive email while I'm at sea on my sailboat. Osu not working for mac high sierraAnd, then, what problems are commonalities due to the fact that Mavericks is making the creation of a serial port so difficult.Does anyone have any advice as to how I could create my serial port and get communication between Parallels (and the Airmail software that I want to use for email) and the Pactor?Thanks, in advance, for any help you all could offer.
0 Comments
Leave a Reply. |
AuthorSean ArchivesCategories |