This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server Hardware for openplotter?
I do not know your pcb board. You have to look in the datasheet.
Something like this is 5V compatible: (see voltage supply 2,3-5,5V)
https://m.media-amazon.com/images/I/C1i+9NOzn8S.pdf
Further I do not know the used adressed from the moitessier board. Take a look in the Manual. Normaly there are the i2c adresses described.
If 0x68 is also not used there, you can mount the ds3231.
in etc/modules some of the entrys already exists. Do not paste them again.
After hardware wiring, you can check the availibility with "sudo nano i2cdetect -y 1")
Reply
If there is an address conflict, you could perhaps use a I2C multiplexer TCA9548A (https://www.adafruit.com/product/2717 or https://www.aliexpress.com/item/32647486...4c4d0TSkFn).
Reply
Thus, the DS3231 conflicts with the Moitessier HAT's MPU9250. Both use the i2c x68 address. If it is not possible to change the address to either the DS3231 or the MPU9250, I think the TCA9548A multiplexer should be used. But now, if I use the multiplexer, the problem of programming arises as I am not capable of it. Can you help me ? I figured out how to physically connect everything, but I don't know how to communicate with Raspberry, MCS, etc. I ask you for help, also because if I succeed, it could be replicated by our fellow sailors. Thanks for the fantastic job you are doing.
Comet 1000 - Openplotter under construction
Reply
Hi, i think you can get overlay problems with a multiplexer...
But have not prove it.
Else you can use a "adress translater" for the clock. Something like this:
https://www.analog.com/media/en/technica...d/4316.pdf
Reply
(2021-01-14, 12:50 PM)glowntiger Wrote: Hi, i think you can get overlay problems with a multiplexer...
But have not prove it.
Else you can use a "adress translater" for the clock. Something like this:
https://www.analog.com/media/en/technica...d/4316.pdf

This also seems better to me.  But I did research to buy it and found nothing.  Where can I buy it ?
Comet 1000 - Openplotter under construction
Reply
Thats the first i have found as breakout... :
https://www.tindie.com/products/closedcu...ranslator/

You can direct wire it to the i2c connector on the MCS board...
Reply
Hi, here an owner of an MCS board version 1.2 with openplotter on it.

Looking for some help to get NMEA0183 in and out working 

Until now I was feeding the configuration from a sperate NMEA multiplexer. This multiplexer was via USB connected. Want to remove the multiplexer and connect directly tot the MCS board.
So I first tried to get NMEA0183 send out to the connected Autopilot. OpenCPN sends out the RMB message. I see this in the Signal K server.
Tried to forwarded this to the serial ttysc2. but nothing is send out physical on the NMEA0183 interface.
So i thought try to receive NMEA0183 messages. So I took my AIS transponder (CSB200) from the multiplexer and connected this one via nmea to ttysc5.
But i didn't receive anything. No LED blinking on the MCS board. I thought they were introduced with MCS board version 1.5.
Tried cat /dev/ttysc5 nothing, tried via de MCS app support serial check, doesn't see only *B.

so what 'm i doing wrong ?
Suggestions on further troubleshooting also welcome !

Thx G.
   
   
   
   
Reply
hi gniersma,
how do you get the nmea0183out data to the sentence event? 
If the TX LED did not flash, signalk did not send anything to this port.
According to my experience it is easyer to use the serial ports in signalk without the serial app....

I have take a look in the cb200 manual. The device did have rs232/485. How do you have connected it?
The RX led must flash according to the incomming data.
The manual for the connection (also in english) you find here:
https://www.gedad.de/support/
Reply
(2021-05-30, 06:12 AM)Hi Thomas, Wrote: thanks for your quick response.

Quote:how do you get the nmea0183out data to the sentence event?
Sorry don't understand this question.
I followed The configuration examples: https://openplotter.readthedocs.io/en/la...mples.html  (Input and output data) in my case using a separate interface ttysc5 (alias ttyOP_ais)  as input and ttysc2 (alias ttyOP_AP) as output.
 
Quote:If the TX LED did not flash, signalk did not send anything to this port. The RX led must flash according to the incomming data.

 don't see any Led's flashing. I've version MCS 1.2 are you sure LED's are on this board?  Understand that this was an enhancement in version 1.5   

Quote:According to my experience it is easyer to use the serial ports in signalk without the serial app....

I checked within the Signal K server the connections. they looked oke to me.

Quote:I have take a look in the cb200 manual. The device did have rs232/485. How do you have connected it?

I know you can connect both on RS232 and on NMEA (RS422) I'm sure i'm used NMEA Rs422, connecting the wires on A and B terminals of the MCS board.

If necessary i can provide a copy of the signal-K server configuration via a back-up file.

Help is appreciated

thx G.
Reply
Hi,
the TX LED is added since HW 1.5 ;-)
Did you see the Data from OCPN in SignalK Browser?
I did not know your device. But sometimes A/B is vice versa.=> A/B is not standardized. So it is possible that you must switch A/B...
For testing you can connect 2 Ports of the MCS. Then you see on the RX LED on the other port if there is any Data... ;-)
Reply


Forum Jump:


Users browsing this thread: 9 Guest(s)