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:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Proprietary PGN
#1
I would like to use a proprietary PGN that would be supported in signalK & canboat and it would be used for configuration and configuration response.  My setup exchange data between the Raspberry Pi and a Teensy with the Actisense canboatjs for the communication and all standard PGNs works ok.  I don't want to add any work to the autors of signalK & canboat, at least not for now. 

I have found the app signalk-generic-pgn-parser that could do that. I have tried the PGN 61184 which is "Manufacturer Proprietary single-frame addressed" but it is not clear what should be used for "Base Path", Manufacturer and for "PGN fields".   

Does the signalk-generic-pgn-parser application is the right one to use? If not, which one should I use?
Does the PGN 61184 is a good choice of PGN?
What "Base Path", Manufacturer and for "PGN fields" should be used for PGN 61184?
Can we use a "Base Path" that is non standard like "configuration" ?

If I use the Node-Red to return data to the Teensy, does a PGN like 61184 would work?

Thanks for your help
Reply


Messages In This Thread
Proprietary PGN - by ptalbot - 2022-09-15, 08:48 PM
RE: Proprietary PGN - by ptalbot - 2022-09-16, 05:59 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)