OpenCPN Beta Version 3.3.1606 Released

[sy_gilana]

@ Dave and all the developers.

I want to share some info on configuration problems and solutions without creating a new thread (there are so many already)

Many of the boats that I have set up OpenCPN on, have had problems with the difference between RS422 and RS232. Fortunately the majority work although they should not. I have found a product that is a possible solution. These guys make and sell RS422 to USB, Ethernet, and WiFi adapters. The interesting part is that each RS422 port can be individually configured for baud rate, one on 38400, another on 4800 etc. Here is a link to their site USB to RS422

Of course the people who have pads or portable devices will find it a boon to have all NMEA on WiFi.

The prices are very attractive.

If this is not the place to share this info, please advise, or cut and paste to the correct forum.

/\/\ike

[CarCode]

/\/\ike,

as you wrote already it is usually not a problem to connect the RS422 NMEA0183 to RS232 when you know that RS422 NMEA0183 takes line A and line B while connecting this to RS232 you will need line A and ground only.

Problems arises however when some manufacturers don't built new drivers for their RS232/USB adapters for new Windows versions e.g.

So I use since 12 years my Kespan USA-19HS adapter and got all the years actual drivers. I suppose not every company delivers such a service.

Gerhard

[sy_gilana]

Originally Posted by CarCode

/\/\ike,

as you wrote already it is usually not a problem to connect the RS422 NMEA0183 to RS232 when you know that RS422 NMEA0183 takes line A and line B while connecting this to RS232 you will need line A and ground only.

Problems arises however when some manufacturers don't built new drivers for their RS232/USB adapters for new Windows versions e.g.

So I use since 12 years my Kespan USA-19HS adapter and got all the years actual drivers. I suppose not every company delivers such a service.

Gerhard

Thanks for your input Gerhard. I am not talking about the PC<>RS232 that I have sussed. Sometimes on Ray***** systems, and on some autopilots, they cannot understand the RS232 because its a voltage sensed system. I have fudged it with a resistor across 2 or 3 to 5 to simulate a current loop, but its only a half solution. When RS232 talks to RS422 (485) it sometimes fails. Eg. OpenCPN outputting APB to a Robertson AP45. the navigation equipment needs to see current loop ie. RS422, and this is where the items above are of interest (to me at least).

Another possible use of the above is to have:

GPS in at 38400
AIS/DSC in at 38400
Depth/speed in at 4800
A/P out at 4800

All at the correct RS422 levels, and only have one wire to the PC bringing those VCP (Virtual Com Ports) in an individually addressable and configurable environment. I think that's cool!

Just thought I would share it....

[CarCode]

As I said the real bottle neck are companies which do not built new drivers for new operating systems and I doubt small companies will do that.

Gerhard

[bdbcat]

Folks...

Another query:

Anyone having trouble with Route creation in Touch/Tablet mode?

Baikal: What is your OS and touch hardware, please?

Thanks
Dave

[bdbcat]

And another thing....

Lots of "Implemented in current Beta" tasks in Flyspray tracker yet (6).

I appreciate your effort to create the tasks in the first place. Now lets follow through and amplify or close them as resolved.

Thanks
Dave

[Baikal]

Originally Posted by bdbcat

Folks...

Another query:

Anyone having trouble with Route creation in Touch/Tablet mode?

Baikal: What is your OS and touch hardware, please?

Thanks
Dave

OS Windows 7 Pro
Panel PC with touch panel

[cagney]

Dave
Looking at the "AIS Target Query" dialog. I think that we need to clarify that the "ETA" mentioned is given in UTC. The easiest is to change "ETA" to "ETA (UTC)". Like this:



Thomas

[AISEAG]

Originally Posted by cagney

Dave
Looking at the "AIS Target Query" dialog. I think that we need to clarify that the "ETA" mentioned is given in UTC. The easiest is to change "ETA" to "ETA (UTC)". Like this:

Attachment 79168

Thomas

Thomas,

I do agree with you it is easy, but is it in accordance with the ETA presented in the "activate route menu" ?.

AFAIK, the question about setting time (UTC/LOCAL) is only ask in the Grib's pluging menu, This should be reconsider and be part of options offered to the user.

Could become a Tracker features ?

Serge

[bcn]

Serge,

ETA as broadcasted by AIS is by definition UTC.
Of course this might be translated to PC local or local time at destination. But does this make sense?

Hubert

[bdbcat]

Baikal....

Can you temporarily connect a mouse to your PC, set OCPN for Touch mode, and try using the mouse to make a Route instead of touch?

I wonder if the touch panel driver that you have produces a different combination of simulated up/down clicks than the panel I am using.

Thanks
Dave

[bdbcat]

cagney/serge/bcn....

I like cagney's approach. Best to be explicit here, otherwise one has to guess. "Which time zone is this one reported in? My time zone where I am now? His TZ now? His TZ at the his destination? Or (my favorite) my TZ where I will be when he gets to wherever he will be?"

And anyway, the ETA reported in the AIS Class A query is the Master's best guess, manually entered into the AIS transponder console by him or the mate. I have often seen non-sense values in this field. We report it in OCPN for completeness only.

Dave

[bcn]

Dave, cagney's idea is absolutely in place. I had to look at the specs to confirm that UTC is mandatory...
And yes, Class A voyage related data are very often crap...

Hubert

[NEVERMIND]

Hi,
The link from the page download opencpn don't work for mac.
Thanks
JP

[bcn]

Can't confirm this.
On the Mac here (Mavericks) we downloaded and installed.
What' is happening exactly?