Posts: 26
Threads: 3
Joined: Mar 2016
Reputation:
0
2017-05-21, 07:08 PM
(This post was last modified: 2017-05-23, 04:18 PM by Sailoog.)
Hi all..
In later builds I seem to be unable to access the temperatures from my 1-wire sensors.
They show up just fine in the 1W flip in OpenPlotter, and I give them somewhat appropriate names for propulsion.engine.temperature, environment.inside.temperature and so on..
But, I cannot find them in SK Diagnostic. None of them.
Browsing the api I see them, though the engine temperature is listed as "temperature", not the correct(?) "propulsion":{"ENGINE":{"Temperature"
{"vessels":{"urn:mrn:imo:mmsi:258202080":{"mmsi":"258202080",
"propulsion":{"ENGINE":{"exhaustTemperature":{"value":284.275,"$source":"OPsensors.1W.EXHAUST","timestamp":"2017-05-19T06:37:16.516Z"},
"temperature":{"value":284.9,"$source":"OPsensors.1W.ENGINE","timestamp":"2017-05-19T06:37:17.395Z"}}},
"environment":{"inside":{"temperature":{"value":273.15,"$source":"OPsensors.1W.INSIDE","timestamp":"2017-05-19T06:37:18.349Z"}}
I was trying to use the engine temperature in the NMEA 0183 builder, but it seems impossible to get the readings there as well.
Any suggestions?
Posts: 2,833
Threads: 60
Joined: Mar 2016
Reputation:
266
openplotter version?
any error in debug mode?
Posts: 26
Threads: 3
Joined: Mar 2016
Reputation:
0
(2017-05-21, 07:58 PM)Sailoog Wrote: openplotter version?
any error in debug mode?
0.11.7 alpha
Debug mode:
SK Diagnostics gives these:
no unit for navigation.gnss.differentialReference
no unit for navigation.gnss.horizontalDilution
no unit for navigation.gnss.geoidalSeparation
no unit for navigation.gnss.satellites
no unit for navigation.gnss.quality
No error for NMEA 0183 Diagnostic..
Posts: 2,833
Threads: 60
Joined: Mar 2016
Reputation:
266
I have reproduced your settings and all is working for me. Your tree is right:
{
"vessels": {
"urn:mrn:imo:mmsi:258202080": {
"mmsi": "258202080",
"propulsion": {
"ENGINE": {
"exhaustTemperature": {
"value": 284.275,
"$source": "OPsensors.1W.EXHAUST",
"timestamp": "2017-05-19T06:37:16.516Z"
},
"temperature": {
"value": 284.9,
"$source": "OPsensors.1W.ENGINE",
"timestamp": "2017-05-19T06:37:17.395Z"
}
}
},
"environment": {
"inside": {
"temperature": {
"value": 273.15,
"$source": "OPsensors.1W.INSIDE",
"timestamp": "2017-05-19T06:37:18.349Z"
}
}
}
}
}
}
no erros on debug and available on NMEA 0183 generator. I don't understand what is happening to you
Posts: 26
Threads: 3
Joined: Mar 2016
Reputation:
0
Seems to me I have to roll over and play dead here... :-|
Last night I tried several things, no go, even in SignalK instrumentpanel the 1-wire values came up empty.
Anyways, today I updated everything, from OpenCPN to Raspbian and booted the RPi. And now, when I try it is working just as it should.
I'm so sorry for bothering you, next time I might test a couple of times more before complaining.... or of course the same thing as I always tells MY end users: "Have you rebooted your computer? I'm not doing anything before you have."
BUT: While I have your attention:
My Raymarine ST2000+ autopilot has an NMEA0183 input which I thought to use for getting it to hold a course related to apparent wind.
It seems though, that it ONLY recognizes the kind of archaic "VWR" sentence which I'm not really up to create in NMEA generator?
VWR - Relative Wind Speed and Angle
1 2 3 4 5 6 7 8 9
| | | | | | | | |
$--VWR,x.x,a,x.x,N,x.x,M,x.x,K*hh<CR><LF>
Field Number:
- Wind direction magnitude in degrees
- Wind direction Left/Right of bow
- Speed
- N = Knots
- Speed
- M = Meters Per Second
- Speed
- K = Kilometers Per Hour
- Checksum
Especially the left/right of bow, how do you make that?
Tips?
Posts: 341
Threads: 0
Joined: Apr 2016
Reputation:
23
(2017-05-22, 07:51 PM)Arne Wrote: VWR - Relative Wind Speed and Angle
1 2 3 4 5 6 7 8 9
| | | | | | | | |
$--VWR,x.x,a,x.x,N,x.x,M,x.x,K*hh<CR><LF>
Field Number:
- Wind direction magnitude in degrees
- Wind direction Left/Right of bow
- Speed
- N = Knots
- Speed
- M = Meters Per Second
- Speed
- K = Kilometers Per Hour
- Checksum
Especially the left/right of bow, how do you make that?
Tips? NMEA0183 generator has its limits. You are right it isn't able to create this sentence. VWT is already outdated but VWR isn't, MWV works.
It also can't convert Kelvin to Farenheit.
Are you sure ST2000+ will use NMEA as wind direction system? Or does it only work with wind from seatalk. I would check this before put much effort in creating this sentence.
Posts: 26
Threads: 3
Joined: Mar 2016
Reputation:
0
As far as I can see from the docs, it should. On page 47 in the Owner Handbook:
NMEA cabling
If required, you can connect a NMEA navigator or wind instrument to the tiller
pilot. It can then use this information for Track and WindTrim modes.
Recognized NMEA data
The following table lists the recognized NMEA sentences.
Code: Information NMEA 0183 data
Cross Track Error APB, APA,RMB, XTE, XTR
Bearing to Waypoint APB, BPI, BWR, BWC, BER, BEC, RMB
Distance to Waypoint WDR, WDC, BPI, BWR, BWC, BER, BEC, RMB
Waypoint Number APA, APB,BPI, BWR, WDR, BWC, WDC, RMB, BOD, WCV, BER, BEC
Speed Through Water VHW
Apparent Wind Angle and Speed VWR
I bought a secondhand Raymarine Seatalk/NMEA interface box (E85001) on eBay recently, come to think of it, it may do what I need here from the values I already get out of OpenPlotter.
Posts: 2,833
Threads: 60
Joined: Mar 2016
Reputation:
266
2017-05-23, 04:17 PM
(This post was last modified: 2017-05-23, 04:18 PM by Sailoog.)
I have plans to make the NMEA 0183 generator more flexible to allow all kind of conversions and operations.
Marking this thread as solved, open a new one if you need for your NMEA 0183 issue. Thanks.
|