Saleve receiver displayed as down

pyrog commented 7 years ago

This receiver is on according to ogn.peanutpod.de and OGN range

live.glidernet.org capture d ecran 2016-11-22 a 13 01 53

pyrog commented 7 years ago

Same issue with all the receivers in the new version 0.2.6 😉

Receiver	app_version
Bohlhof	0.2.6.ARM
EPLU	0.2.6.x64
Letzi	0.2.6.RPI-GPU
LFLE	0.2.6.x86
Padova	0.2.6.ARM
Saleve	0.2.6.ARM

PS: This issue is on the backend.

The front end use directly data from BE. https://github.com/glidernet/ogn-live/blob/master/cunimb.js#L669 https://github.com/glidernet/ogn-live/blob/master/cunimb.js#L677

@melissa similar issue in OGN range. The version is "?"

http://ognrange.onglide.com/perl/stations2-filtered.pl?start=2015-03-31&end=2100-01-01

{"s":"LFLE","lt":45.5572,"lg":5.9765,"u":"D","ut":"2016-11-20 16:26","b":0,"v":"?"}

ifly7charlie commented 7 years ago

It would be very nice if this format was documented and an announcement was made about it changing. Some form of regular structure would also make it less likely new features were going to break backwards compatibility...

EPLU>APRS,TCPIP*,qAC,GLIDERN1:>141427h v0.2.6.x64 CPU:0.0 RAM:119.3/4010.3MB NTP:3.4ms/+18.9ppm 1/1Acfts[1h] RF:+45-3.9ppm/+5.01dB/+22.9dB@10km[68]/+22.9dB@10km[1/1]

Mel

On 22 Nov 2016, at 12:43, Yves Pratter notifications@github.com wrote:

Same issue with all the receivers in the new version 0.2.6 😉

Receiver app_version Bohlhof 0.2.6.ARM EPLU 0.2.6.x64 Letzi 0.2.6.RPI-GPU LFLE 0.2.6.x86 Padova 0.2.6.ARM Saleve 0.2.6.ARM PS: This issue is on the backend.

The front end use directly data from BE. https://github.com/glidernet/ogn-live/blob/master/cunimb.js#L669 https://github.com/glidernet/ogn-live/blob/master/cunimb.js#L677

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

ifly7charlie commented 7 years ago

I've added a fallback parser to parse these more flexibly and hopefully v0.2.6 will start to show as online soon.

pyrog commented 7 years ago

@ifly7charlie The format is already documented:

http://wiki.glidernet.org/wiki:ogn-flavoured-aprs

See also the Automatic Packet Reporting System spec:

http://www.aprs.org/APRS-docs/PROTOCOL.TXT

But, yes, the wiki need to be refreshed 😉

ifly7charlie commented 7 years ago

The receiver beacon format is not documented - an annotated example of an old spec is provided. This doesn't match 0.2.5 or 0.2.6 ;) Anyway, the new regexes should pick up what I care about as long as they remain RF: and CPU: Formalising it would be useful - especially as the new Acfts field is not in the same structure as the previous so must be matched differently.

pyrog commented 7 years ago

The receiver beacon format is not documented

Shame on me 😆 And, this is not the APRS air format, but the APRS-IS format !

APRS message repeated by of of the OGN APRS servers: EPLU>APRS,TCPIP*,qAC,GLIDERN1:>141427h v0.2.6.x64 CPU:0.0 RAM:119.3/4010.3MB

APRS message from an OGN receiver sended to one of the OGN APRS servers: BdAmont>APRS:>090728h v0.2.5.ARM CPU:0.1 RAM:758.2/970.5MB NTP:1.2ms/-8.0ppm +51.5C 0/0Acfts[1h] RF:+11+7.5ppm/+0.28dB

http://ham.zmailer.org/oh2mqk/aprx/PROTOCOLS

After successfull login, communication carries "TNC2" format APRS messages. Namely text encoding of AX.25 UI frames in what became known as "TNC2 monitor style":

SOURCE>DESTIN:payload
SOURCE>DESTIN,VIA,VIA:payload

The SOURCE, DESTIN, and VIA fields are AX.25 address fields, and have "-SSID" value annexed if the SSID is not zero. Also in VIA-fields, if the "HAS BEEN DIGIPEATED" bit is set (AX.25 v2 protocol feature) a star * character is appended. VIA-fields are separated by comma , from DESTIN, and each other.

A double-colon : separates address data from payload. The payload is passed _ASIS without altering any message content bytes, however ending at first CR or LF character encountered in the packet.

AX.25 UI frame ( known as "TNC2 monitor style")

Field	description
`SOURCE>DESTIN,VIA,VIA:payload`	EPLU>APRS,TCPIP*,qAC,GLIDERN1
`:`
`Payload`	>141427h v0.2.6.x64 CPU:0.0 RAM:119.3/4010.3MB

AX.25 address fields

Field	description
EPLU	Source callsign (receiver callsign)
`>`
APRS	Destination callsign
`,`
TCPIP*	VIA addresse TCPIP is not to be relayed to APRS-IS. The star `*` character is the "HAS BEEN DIGIPEATED" bit set (AX.25 v2 protocol feature).
`,`
qAC	Packet was received from the client directly via a verified connection
`,`
GLIDERN1	APRS server's callsign-SSID

AX.25 payload field (OGN receiver status)

Field	description
`>`	Packet to be recognized as an APRS STATUS type packet
`141427h`	localtime (UTC HHMMSSh)

`v0.2.6.x64`	software version

`CPU:0.2`	CPU Load 0.2%

`RAM:119.3/4010.3MB`	RAM free / Total

`NTP:1.2ms/-8.0ppm`	NTP Status: estimated error / frequency correction

`+51.5C`	CPU temperature

`0/0Acfts[1h]`	Visible/All aircrafts received over last 1 hour

`RF:+11+7.5ppm/+0.28dB`	RF: Frequency correction / Fine calibration frequency correction

pyrog commented 7 years ago

Updated previous comment (added more fields and descriptions). Sources: ogn-rf and ogn-decode status pages (http://raspberrypi:8080 and http://raspberrypi:8081)

snip commented 6 years ago

Source of receiver has now changed. (now provided by Angel tools)

glidernet / ogn-live