kopia lustrzana https://github.com/cyoung/stratux
Ref new status message. Web interface examples.
Christopher Young
rodzic
e7a19f2296
commit
b33b1ed098
|
|
@ -6,14 +6,13 @@ Stratux uses GDL90 protocol over port 4000 UDP. All messages are sent as **unica
|
|||
network and a DHCP lease is issued to the device, the IP of the DHCP lease is added to the list of clients receiving GDL90 messages.
|
||||
|
||||
|
||||
The GDL90 is "standard" with the exception of two non-standard GDL90-style messages: 0xCC (stratux heartbeat) and 0x4C (AHRS report).
|
||||
|
||||
The GDL90 is "standard" with the exception of three non-standard GDL90-style messages: `0xCC` (stratux heartbeat), `0x5358` (another stratux heartbeat), and `0x4C` (AHRS report).
|
||||
|
||||
### How to recognize stratux
|
||||
|
||||
In order of preference:
|
||||
|
||||
1. Look for 0xCC heartbeat message. This is sent at the same time as the GDL90 heartbeat (0x00) message.
|
||||
1. Look for `0xCC` (or `0x5358`) GDL90 heartbeat message. This is sent at the same time as the GDL90 heartbeat (0x00) message.
|
||||
2. Look for Wi-Fi network that **starts with** "stratux".
|
||||
3. Detect 192.168.10.0/24 Wi-Fi connection, verify stratux status with JSON response from ws://192.168.10.1/status.
|
||||
|
||||
|
|
@ -52,4 +51,108 @@ Traffic information roughly follows this path:
|
|||
|
||||
When traffic information is being received both from UAT and 1090ES sources, it is not uncommon to see a flip/flop in tail numbers on targets.
|
||||
Some 1090ES transponders will send the actual registration number of the aircraft, which then becomes a TIS-B target whose tail number may be
|
||||
a squawk code.
|
||||
a squawk code.
|
||||
|
||||
|
||||
### Additional data available to EFBs
|
||||
|
||||
Stratux makes available a webserver to retrieve statistics which may be useful to EFBs:
|
||||
|
||||
* `http://192.168.10.1/getTowers` - a list of ADS-B towers received with attached message receipt and signal level statistics. Example output:
|
||||
|
||||
{
|
||||
"(28.845592,-96.920400)": {
|
||||
"Lat": 28.845591545105,
|
||||
"Lng": -96.920399665833,
|
||||
"Signal_strength_last_minute": 55,
|
||||
"Signal_strength_max": 69,
|
||||
"Messages_last_minute": 97,
|
||||
"Messages_total": 196
|
||||
},
|
||||
"(29.266505,-98.309097)": {
|
||||
"Lat": 29.266505241394,
|
||||
"Lng": -98.309097290039,
|
||||
"Signal_strength_last_minute": 78,
|
||||
"Signal_strength_max": 78,
|
||||
"Messages_last_minute": 1,
|
||||
"Messages_total": 3
|
||||
},
|
||||
"(29.702547,-96.900787)": {
|
||||
"Lat": 29.702546596527,
|
||||
"Lng": -96.900787353516,
|
||||
"Signal_strength_last_minute": 87,
|
||||
"Signal_strength_max": 119,
|
||||
"Messages_last_minute": 94,
|
||||
"Messages_total": 203
|
||||
}
|
||||
}
|
||||
|
||||
* `http://192.168.10.1/getStatus` - device status and statistics. Example output (commented JSON):
|
||||
|
||||
{
|
||||
"Version": "v0.5b1", // Software version.
|
||||
"Devices": 0, // Number of radios connected.
|
||||
"Connected_Users": 1, // Number of WiFi devices connected.
|
||||
"UAT_messages_last_minute": 0, // UAT messages received in last minute.
|
||||
"UAT_messages_max": 17949, // Max UAT messages received in a minute (since last reboot).
|
||||
"ES_messages_last_minute": 0, // 1090ES messages received in last minute.
|
||||
"ES_messages_max": 0, // Max 1090ES messages received in a minute (since last reboot).
|
||||
"GPS_satellites_locked": 0, // Number of GPS satellites used in last GPS lock.
|
||||
"GPS_connected": true, // GPS unit connected and functioning.
|
||||
"GPS_solution": "", // "DGPS (WAAS)", "3D GPS", "N/A", or "" when GPS not connected/enabled.
|
||||
"RY835AI_connected": false, // GPS/AHRS unit - use only for debugging (this will be removed).
|
||||
"Uptime": 227068, // Device uptime (in milliseconds).
|
||||
"CPUTemp": 42.236 // CPU temperature (in ºC).
|
||||
}
|
||||
|
||||
* http://192.168.10.1/getSettings` - get device settings. Example output:
|
||||
|
||||
{
|
||||
"UAT_Enabled": true,
|
||||
"ES_Enabled": false,
|
||||
"GPS_Enabled": true,
|
||||
"NetworkOutputs": [
|
||||
{
|
||||
"Conn": null,
|
||||
"Ip": "",
|
||||
"Port": 4000,
|
||||
"Capability": 5
|
||||
},
|
||||
{
|
||||
"Conn": null,
|
||||
"Ip": "",
|
||||
"Port": 49002,
|
||||
"Capability": 2
|
||||
}
|
||||
],
|
||||
"AHRS_Enabled": false,
|
||||
"DEBUG": false,
|
||||
"ReplayLog": true,
|
||||
"PPM": 0,
|
||||
"OwnshipModeS": "F00000",
|
||||
"WatchList": ""
|
||||
}
|
||||
|
||||
* `http://192.168.10.1/setSettings` - set device settings. Use an HTTP POST of JSON content in the format given above - posting only the fields containing the settings to be modified.
|
||||
|
||||
* `http://192.168.10.1/getSituation` - get GPS/AHRS information. Example output:
|
||||
|
||||
{
|
||||
"Lat": 39.108533,
|
||||
"Lng": -76.770862,
|
||||
"Satellites": 7,
|
||||
"Accuracy": 5.88,
|
||||
"NACp": 10,
|
||||
"Alt": 170.10767,
|
||||
"LastFixLocalTime": "2015-12-18T23:47:06.015563066Z",
|
||||
"TrueCourse": 0,
|
||||
"GroundSpeed": 0,
|
||||
"LastGroundTrackTime": "0001-01-01T00:00:00Z",
|
||||
"Temp": 6553,
|
||||
"Pressure_alt": 231.27980834234,
|
||||
"Pitch": -0.006116937627108,
|
||||
"Roll": -0.026442866350631,
|
||||
"Gyro_heading": 45.844213419776,
|
||||
"LastAttitudeTime": "2015-12-18T23:47:06.774039623Z"
|
||||
}
|
||||
|
||||
Ładowanie…
Reference in New Issue