Visit our Popular Forums

bcn · 15-12-2015, 09:25

Larry,

did you try to enter manually/ copy

/dev/cu.usbserial

into the serial port settings drop down menu?

svserengeti · 15-12-2015, 09:51

bcn,

Thanks for the suggestion. I am using the port : /dev/cu.usbserial already with my Prolific Serial to usb converter for my ship's nmea data at 4800 baud. This port shows in up Open Cpn when I click on "add connection" and works just fine.

Thanks,

Larry
svserengeti

rgleason · 15-12-2015, 14:47

Gerhard you are a good guy, because you want it to work. Maybe there is some problem with his command window or something?

I have a similar problem in the office with others. They think they are doing what I tell them to do, and it doesn't work. I walk over and find out they misunderstood or I did not describe it completely enough. Then sure enough it works. I think Larry has been around computers quite awhile, so he has the instructions and will figure it out. He must have used the Dos prompt a lot. So lets just be patient and see if he can figure it out himself, for now.

PS: I see he did it ..

bdbcat · 15-12-2015, 20:51

Larry...

Well, it seems that there is no unix style ("'/dev/cu*") driver for the STM32 module. Or at least not that I could find.

Some info:
https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=https%3a%2f%2fmy.st.com%2fpub lic%2fSTe2ecommunities%2fmcu%2fLists%2fcortex_mx_s tm32%2fMac%20os%20x%20driver%20for%20stm32%20serie s&FolderCTID=0x01200200770978C69A1141439FE559EB459 D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=139 3

So I don't see any simple way for OCPN on Mac to support this device.

If you are looking for a fresh alternative AIS receiver, take a look at this:
https://www.tindie.com/products/astu...-ais-receiver/

Looks pretty cool.

Sorry
Dave

bcn · 15-12-2015, 23:20

If not already done please look here and try the driver:
https://em-trak.com/support/can-down...-drivers-r100/

Btw: in the ProAIS2 connection window, how is the COM port called under OS-X in your case? Reason: if ProAIS connects under OS-X there shouldn't be any reason why OCPN doesn't.

CarCode · 16-12-2015, 01:45

Once again: This device has a FTDI Chip for Serial to USB converting. So a FTDI driver is needed and not STM32 or anything else. Is this too hard to understand?

Get the driver from the already mentioned places here and install it.
The driver is called FTDIUSBSerialDriver_v2_2_14.dmg
Open the dmg file to get a window with installation instructions.

Then look in the Terminal window for the results of ls command.

Gerhard

svserengeti · 16-12-2015, 05:31

Thank you Gerhard and Dave for your detailed information. I will look at Gerhard's suggestion for a suitable driver. Thanks also to bcn.

To answer bcn's question. The Pro Ais2 in the connect box calls the port "Ais Virtual Com Port" when I connect this way, I am able to connect and control the ais via Pro AIS2 & the function is normal. As mentioned earlier,The macbook in "system information" calls this usb connection STM32 Virtual Com Port.

Thanks again for everyone's input

Larry
svserengeti

fogmachine · 17-12-2015, 07:52

Unlike Windows, OSX (and other Unix/Linux variants) are case-sensitive wrt commands and filenames. So the 'ls' command has to be lower case, as does the filenames/path arguments. Windows users also sometimes confuse / (forward slash) with \ (back slash) which can be very hard to debug over the phone.

Another thing you can try is to unplug the USB/serial converter, plug it back in, wait a few seconds, then run

Code:

ls -ltr /dev

and send us the last five lines of the results (please cut/paste).

When I do it I get:

Code:

null
tty.usbserial
cu.usbserial
ptmx
ttys000

This should tell us what the system is naming your adapter.

(In some old Unixes there is an exception to the case-sensitive part - it used to be that if you logged in with your user ID in upper case it would try to lower-case your commands before running them to cover if you were using a terminal that had no lower case. This didn't work very well.)

CarCode · 17-12-2015, 08:16

fogmaschine,

it seems something has changed in El Capitain. Commands are not case sensitive but parameters are:

Code:

MacBook:~ xyz$ ls /dev/cu*
/dev/cu.Bluetooth-Incoming-Port    /dev/cu.Qstarz818XT-SPPslave
/dev/cu.HBTSOL-SPPslave        /dev/cu.RO4800-BT-DevB
MacBook:~ xyz$ LS /dev/cu*
/dev/cu.Bluetooth-Incoming-Port    /dev/cu.Qstarz818XT-SPPslave
/dev/cu.HBTSOL-SPPslave        /dev/cu.RO4800-BT-DevB

And as said before only the items starting with letters "cu" are of interest here. So he should type /dev/cu* as parameter. It is not very helpfull to confuse people with wrong informations.

Gerhard

svserengeti · 17-12-2015, 10:32

Dave,

The driver installed currently is: FTDIUSBSerialDriver_V2_3

When I locate the driver in Extensions, it is described as :unix executable

Larry
svserengeti

svserengeti · 17-12-2015, 10:39

Ran the command: ls -ltr /dev

Results:
crw-rw-rw- 1 root wheel 18, 14 Dec 17 13:24 tty.usbserial
crw-rw-rw- 1 root wheel 18, 16 Dec 17 13:24 tty.usbmodem14261
crw-rw-rw- 1 root wheel 18, 15 Dec 17 13:24 cu.usbserial
crw-rw-rw- 1 root wheel 18, 17 Dec 17 13:24 cu.usbmodem14261
crw-rw-rw- 1 root wheel 11, 0 Dec 17 13:28 random
crw-rw-rw- 1 root wheel 3, 2 Dec 17 13:32 null
crw--w---- 1 LarrysMacbook tty 16, 0 Dec 17 13:34 ttys000
crw-rw-rw- 1 root wheel 14, 19 Dec 17 13:34 io8logtemp
crw--w---- 1 LarrysMacbook tty 16, 1 Dec 17 13:35 ttys001

CarCode · 17-12-2015, 10:40

Huh, finally a result allready.
ls -ltr /dev is wrong however for this task, take ls /dev/cu*
It is not correct what fogmaschine has wrote here...

So enter for OpenCPN in the connection settings for the new serial device:
/dev/cu.usbmodem14261

Same as you have done already for /dev/cu.usbserial but obviously together with a baudrate of 38400 instead of 4800.

Gerhard