USB to serial converter

[eddyq]

I have a USB to serial converter. I don't know the manufacturer but found something on the internet that looked like it so I downloaded their driver.

Now (I'm new to a Mac) I need to see if it works.

1) Is there a way to display all of the devices in a GUI such that I can identify the com port? (I did "ls /dev" and I see ttys0, etc (about 20 or so))
2) I need to know which tty the converter belongs to. How do I do that?
3) Once I identify it, how do I set the serial parameters?

 

[belvdr]

See if dmesg reports the tty. Once identified, it's up to the application to determine the settings for the tty.

 

[eddyq]

dmesg does not tell me much. Here is the output followed by the output from ls /dev. I suspect the com port is one of the ttys entries. But how do I tell which one?


EddysOSX:~ eddyq$ sudo dmesg
Password:
fo 0x6ad35020 Name com.vmware.kext.vmnet Version 2.0.5 build-173382 at Jun 22 2009 15:30
vmnet: Initializing module.
vmnet: VMNet_Start allocated gOSMallocTag
vmnet: Module initialized.
vmnet: VNetUserIf_Create: created userIf at 0x78b4200.
vmnet: VMNetConnect: returning port 0x78b4200
vmnet: Hub 8 does not exist, allocating memory.
vmnet: Allocated hub 0x78cd800 for hubNum 8.
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f1:d3:cc
vmnet: Hub 8
vmnet: Port 0
vmnet: VNetUserIf_Create: created userIf at 0x7980e00.
vmnet: VMNetConnect: returning port 0x7980e00
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:e7:3e:54
vmnet: Hub 8
vmnet: Port 0
vmnet: Port 1
vmnet: VNetUserIf_Create: created userIf at 0x7980d00.
vmnet: VMNetConnect: returning port 0x7980d00
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f7:3f:94
vmnet: Hub 8
vmnet: Port 0
vmnet: Port 1
vmnet: Port 2
vmnet: VNetUserIfFree: freeing userIf at 0x7980d00.
vmnet: netif-vmnet8: Adding protocol 2.
vmnet: VNetUserIf_Create: created userIf at 0x781b800.
vmnet: VMNetConnect: returning port 0x781b800
vmnet: Hub 1 does not exist, allocating memory.
vmnet: Allocated hub 0x7931000 for hubNum 1.
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f5:88:60
vmnet: Hub 1
vmnet: Port 0
vmnet: VNetUserIfFree: freeing userIf at 0x781b800.
vmnet: netif-vmnet1: Adding protocol 2.
vmnet: VNetUserIf_Create: created userIf at 0x7980800.
vmnet: VMNetConnect: returning port 0x7980800
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:e5:d5:7c
vmnet: Hub 1
vmnet: Port 0
vmnet: Port 1
NTFS driver 2.1 [Flags: R/O].
AirPort: Link Up on en1
NTFS volume name , version 3.1.
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
vmnet: VNetUserIf_Create: created userIf at 0x7cb7800.
vmnet: VMNetConnect: returning port 0x7cb7800
vmnet: Hub 0 does not exist, allocating memory.
vmnet: Allocated hub 0x7cae000 for hubNum 0.
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f3:ba:78
vmnet: Hub 0
vmnet: Port 0
vmnet: bridge-en0: got dev 0x76aee04
vmnet: bridge-en0: up
vmnet: bridge-en0: attached
vmnet: VNetUserIfFree: freeing userIf at 0x7cb7800.
vmnet: VMNetDisconnect called for port 0x7cb7900
vmnet: bridge-en0: filter detached
vmnet: bridge-en0: down
vmnet: bridge-en0: detached
vmnet: Freeing hub at 0x7cae000.
vmnet: VNetUserIf_Create: created userIf at 0x7cb7900.
vmnet: VMNetConnect: returning port 0x7cb7900
vmnet: Hub 0 does not exist, allocating memory.
vmnet: Allocated hub 0x7cae000 for hubNum 0.
vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:f6:fe:a0
vmnet: Hub 0
vmnet: Port 0
vmnet: bridge-en1: got dev 0x774e804
vmnet: bridge-en1: wireless interface detected.
vmnet: bridge-en1: up
vmnet: bridge-en1: attached
vmnet: VNetUserIfFree: freeing userIf at 0x7cb7900.

EddysOSX:~ eddyq$ ls /dev >th
EddysOSX:~ eddyq$ cat this.tx
ath0
autofs
autofs_control
autofs_nowait
bpf0
bpf1
bpf2
bpf3
console
cu.Bluetooth-Modem
cu.Bluetooth-PDA-Sync
disk0
disk0s1
disk0s2
disk0s3
dtrace
dtracehelper
fbt
fd
fsevents
klog
lockstat
machtrace
null
pmCPU
profile
ptmx
ptyp0
ptyp1
ptyp2
ptyp3
ptyp4
ptyp5
ptyp6
ptyp7
ptyp8
ptyp9
ptypa
ptypb
ptypc
ptypd
ptype
ptypf
ptyq0
ptyq1
ptyq2
ptyq3
ptyq4
ptyq5
ptyq6
ptyq7
ptyq8
ptyq9
ptyqa
ptyqb
ptyqc
ptyqd
ptyqe
ptyqf
ptyr0
ptyr1
ptyr2
ptyr3
ptyr4
ptyr5
ptyr6
ptyr7
ptyr8
ptyr9
ptyra
ptyrb
ptyrc
ptyrd
ptyre
ptyrf
ptys0
ptys1
ptys2
ptys3
ptys4
ptys5
ptys6
ptys7
ptys8
ptys9
ptysa
ptysb
ptysc
ptysd
ptyse
ptysf
ptyt0
ptyt1
ptyt2
ptyt3
ptyt4
ptyt5
ptyt6
ptyt7
ptyt8
ptyt9
ptyta
ptytb
ptytc
ptytd
ptyte
ptytf
ptyu0
ptyu1
ptyu2
ptyu3
ptyu4
ptyu5
ptyu6
ptyu7
ptyu8
ptyu9
ptyua
ptyub
ptyuc
ptyud
ptyue
ptyuf
ptyv0
ptyv1
ptyv2
ptyv3
ptyv4
ptyv5
ptyv6
ptyv7
ptyv8
ptyv9
ptyva
ptyvb
ptyvc
ptyvd
ptyve
ptyvf
ptyw0
ptyw1
ptyw2
ptyw3
ptyw4
ptyw5
ptyw6
ptyw7
ptyw8
ptyw9
ptywa
ptywb
ptywc
ptywd
ptywe
ptywf
random
rdisk0
rdisk0s1
rdisk0s2
rdisk0s3
sdt
stderr
stdin
stdout
systrace
tty
tty.Bluetooth-Modem
tty.Bluetooth-PDA-Sync
ttyp0
ttyp1
ttyp2
ttyp3
ttyp4
ttyp5
ttyp6
ttyp7
ttyp8
ttyp9
ttypa
ttypb
ttypc
ttypd
ttype
ttypf
ttyq0
ttyq1
ttyq2
ttyq3
ttyq4
ttyq5
ttyq6
ttyq7
ttyq8
ttyq9
ttyqa
ttyqb
ttyqc
ttyqd
ttyqe
ttyqf
ttyr0
ttyr1
ttyr2
ttyr3
ttyr4
ttyr5
ttyr6
ttyr7
ttyr8
ttyr9
ttyra
ttyrb
ttyrc
ttyrd
ttyre
ttyrf
ttys0
ttys000
ttys001
ttys1
ttys2
ttys3
ttys4
ttys5
ttys6
ttys7
ttys8
ttys9
ttysa
ttysb
ttysc
ttysd
ttyse
ttysf
ttyt0
ttyt1
ttyt2
ttyt3
ttyt4
ttyt5
ttyt6
ttyt7
ttyt8
ttyt9
ttyta
ttytb
ttytc
ttytd
ttyte
ttytf
ttyu0
ttyu1
ttyu2
ttyu3
ttyu4
ttyu5
ttyu6
ttyu7
ttyu8
ttyu9
ttyua
ttyub
ttyuc
ttyud
ttyue
ttyuf
ttyv0
ttyv1
ttyv2
ttyv3
ttyv4
ttyv5
ttyv6
ttyv7
ttyv8
ttyv9
ttyva
ttyvb
ttyvc
ttyvd
ttyve
ttyvf
ttyw0
ttyw1
ttyw2
ttyw3
ttyw4
ttyw5
ttyw6
ttyw7
ttyw8
ttyw9
ttywa
ttywb
ttywc
ttywd
ttywe
ttywf
urandom
vmmon
vn0
vn1
vn2
vn3
zero
EddysOSX:~ eddyq$

 

[belvdr]

Unplug the converter, then plug it back in and run dmesg. It should show something was plugged in.

 

[MisterMe]

dmesg does not tell me much. Here is the output followed by the output from ls /dev. I suspect the com port is one of the ttys entries. But how do I tell which one?


....

Are you using the USB-to-serial converter to connect a device to your Mac or do you have only the cable connected? If the latter is the case, then I would not expect the computer to behave any differently than it does when nothing is plugged into the USB port.

 

[MacTech68]

May I suggest opening Apple System Profiler and checking the USB Product ID and Manufacturer ID's. Then you might be able to determine what chipset the adapter is and get a driver for that.

I have a Prolific USB to RS232 adapter (used in many older Nokia phone cables) that I use for my old Barcode Scanner.

Apple System Profiler gives me:

USB-Serial Controller:

Version: 3.00
Bus Power (mA): 500
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Product ID: 0x2303
Vendor ID: 0x067b

Installing the kext "osx-pl2303.kext" gives me

tty.PL2303-3B1

in ls /dev

another driver that works with this adapter is a different kext name and a different tty in dev.

EDIT: I use CoolTerm which reminds me a lot of Z-Term. Just click on the "Options" button. Your adapter may show up in the "Port" pop-up list. Other serial ports may show there as well. Internal Modems and Bluetooth Serial ports.
________
Pedro Rodr?guez (racing driver)

 

[eddyq]

Are you using the USB-to-serial converter to connect a device to your Mac or do you have only the cable connected? If the latter is the case, then I would not expect the computer to behave any differently than it does when nothing is plugged into the USB port.

It is to connect my Mac to a TTY program on my PC.

I tried unplugging and replugging it and dmesg does not seem to show anything different than above.

I tried CoolTermMac and that only shows the Bluetooth.

I tried System Profiler and it does not show it.

So I plugged the device into XP and that shows it up in Device Manager. Doesn't the Mac have something like Device Manager?

 

[eddyq]

So I plugged the device into XP and that shows it up in Device Manager. Doesn't the Mac have something like Device Manager?

I found it it is made by FTDI Ltd. I searched the internet for a Mac driver but didn't have any luck. Does anyone know if there is a driver for the MacBook Pro running OSX 10.5.8?

I just found a driver. If anyone else is interested it is at www.tfpichip.com/Drivers/VCP.htm. I have not tried it yet and will report back after I do.

 

[MacTech68]

I found it it is made by FTDI Ltd. I searched the internet for a Mac driver but didn't have any luck. Does anyone know if there is a driver for the MacBook Pro running OSX 10.5.8?

I just found a driver. If anyone else is interested it is at www.tfpichip.com/Drivers/VCP.htm. I have not tried it yet and will report back after I do.

Click on the Apple logo, top left of the screen. Select "About This Mac".

Now click on "More Info". That launches Apple System Profiler.

Under USB in Apple System Profiler, check what the Product ID and Device ID values are and post the results here.

The following driver may need "customization" depending on the Vendor ID of your FTDI chipset adapter:

http://www.ftdichip.com/Drivers/VCP/MacOSX/UniBin/FTDIUSBSerialDriver_v2_2_14.dmg

EDIT: SNAP!
________
marijuana trichomes

 

[eddyq]

I downloaded the driver I mentioned above. It now shows up under System Profiler and it shows up with CoolTerm. I connected via a Null Modem to my PC and ran Hyperterminal there and CoolTerm at the Mac. I set them both up for 9600 8-N-1 and clicked the Connect icon on each. CoolTerm shows CTS, DSR and DCD and if I unplug from my PC those go out ... so I'm sure I have the connections at the PC correct.

But when I type I get nothing at either side. Does anyone know if there is anything else I need to do or if there is some other way to test it.

Edit: Never mind ... I got it all working. Now I need to write some software to use it. Does anyone know if there is some sample software written in C that I can refer to?

 

[belvdr]

What are you trying to accomplish?

 

[eddyq]

I'm writing a kext. I don't have a 2nd mac so I can't use the firewire to get debugging printed output. So I want to try to use the serial connection to my XP computer. If I could see some user level C code then that would help me understand how to write the kernel level C code that I will add to my kext.

 

[MacTech68]

...I got it all working. Now I need to write some software to use it. Does anyone know if there is some sample software written in C that I can refer to?

Nope. You've got me there. I use an AppleScript Scripting Addition called "SerialPort X" to allow me to use AppleScript to do what I need for the Barcode Scanner.

Just depends on what you're trying to do.

EDIT... I see. Perhaps this is why the only other solution for my Barcode Scanner was about $45
________
volcano vaporizer

 

[schneideris]

I downloaded the driver I mentioned above. It now shows up under System Profiler and it shows up with CoolTerm. I connected via a Null Modem to my PC and ran Hyperterminal there and CoolTerm at the Mac. I set them both up for 9600 8-N-1 and clicked the Connect icon on each. CoolTerm shows CTS, DSR and DCD and if I unplug from my PC those go out ... so I'm sure I have the connections at the PC correct.

But when I type I get nothing at either side. Does anyone know if there is anything else I need to do or if there is some other way to test it.

Edit: Never mind ... I got it all working. Now I need to write some software to use it. Does anyone know if there is some sample software written in C that I can refer to?

I have the same issue and manufacture and am trying to download the driver you wrote about. The link appears to be broken. Could you check it and re-post?

You might try DigiTemp for its source code on writing to and from the com.

 

[MacTech68]

I have the same issue and manufacture and am trying to download the driver you wrote about. The link appears to be broken. Could you check it and re-post?

You might try DigiTemp for its source code on writing to and from the com.

Try the link in my post above (the OP's domain name is incorrect).
________
Honda G engine specifications