You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/LedStrip.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -237,6 +237,12 @@ The mapping between modes led placement and colors is currently fixed and cannot
237
237
238
238
#### Indicator
239
239
240
+
##### For fixed wing (INAV 6.1 onwards)
241
+
242
+
This mode flashes LEDs that correspond to the roll stick position. Rolling left will flash any `indicator` LED on the left half of the grid. Rolling right will flash any `indicator` on the right side of the grid.
243
+
244
+
##### For other platforms (all platforms pre INAV 6.1)
245
+
240
246
This mode flashes LEDs that correspond to roll and pitch stick positions. i.e. they indicate the direction the craft is going to turn.
Copy file name to clipboardExpand all lines: docs/SITL/SITL.md
+38-14Lines changed: 38 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ The sensors are replaced by data provided by a simulator.
12
12
Currently supported are
13
13
- RealFlight https://www.realflight.com/
14
14
- X-Plane https://www.x-plane.com/
15
+
- fl2sim [replay Blackbox Log via SITL](https://github.com/stronnag/bbl2kml/wiki/fl2sitl), uses the X-Plane protocol.
15
16
16
17
INAV SITL communicates for sensor data and control directly with the corresponding simulator, see the documentation of the individual simulators and the Configurator or the command line options.
17
18
@@ -30,25 +31,38 @@ The following sensors are emulated:
30
31
Select "FAKE" as type for all mentioned, so that they receive the data from the simulator.
31
32
32
33
## Serial ports+
33
-
UARTs are replaced by TCP starting with port 5760 ascending. UART 1 port 5760, UART2 6761, ...
34
-
By default, UART1 and UART2 are available as MSP connections.
35
-
To connect the Configurator to SITL: Select TCP and connect to ```127.0.0.1:5760``` (if SITL is running on the same machine).
36
-
IPv4 and IPv6 are supported, either raw addresses of hostname lookup.
34
+
UARTs are replaced by TCP starting with port 5760 ascending. UART 1 port 5760, UART2 5761, ...
35
+
By default, UART1 and UART2 are available as MSP connections. Other UARTs will have TCP listeners if they have an INAV function assigned.
36
+
To connect the Configurator to SITL: Select TCP and connect to ```localhost:5760``` (or ```127.0.0.1:5760``` if your OS doesn't understand `localhost`) (if SITL is running on the same machine).
37
+
IPv4 and IPv6 are supported, either raw addresses or host-name lookup.
37
38
38
39
The assignment and status of user UART/TCP connections is displayed on the console.
39
40
40
-

41
+
```
42
+
INAV 6.1.0 SITL
43
+
[SYSTEM] Init...
44
+
[SIM] No interface specified. Configurator only.
45
+
[EEPROM] Loaded 'eeprom.bin' (32768 of 32768 bytes)
46
+
[SOCKET] Bind TCP :: port 5760 to UART1
47
+
[SOCKET] Bind TCP :: port 5761 to UART2
48
+
[SOCKET] ::1 connected to UART1
49
+
```
41
50
42
51
All other interfaces (I2C, SPI, etc.) are not emulated.
43
52
44
53
## Remote control
45
-
Joystick (via simulator) or serial receiver via USB/Serial interface are supported.
54
+
MSP_RX (TCP/IP) or joystick (via simulator) or serial receiver via USB/Serial interface are supported.
55
+
56
+
### MSP_RX
57
+
58
+
MSP_RX is the default, 18 channels are supported over TCP/IP serial emulation.
46
59
47
60
### Joystick interface
48
61
Only 8 channels are supported.
49
62
Select "SIM (SITL)" as the receiver and set up a joystick in the simulator, details of which can be found in the documentation for the individual simulators.
50
63
51
64
### Serial Receiver via USB
65
+
52
66
Connect a serial receiver (e.g. SBUS) to the PC via a UART/USB adapter. Configure the receiver in the Configurator as usual.
53
67
54
68
The Configurator offers a built-in option for forwarding the serial data to the SITL TCP port, if SITL is started manually the following option can be used:
@@ -65,7 +79,11 @@ For this you need a FT232 module. With FT-Prog (https://ftdichip.com/utilities/)
65
79
For SBUS, the command line arguments of the python script are:
66
80
```python tcp_serial_redirect.py --parity E --stopbits 2 -c 127.0.0.1:[INAV-UART-PORT] COMXX 100000```
67
81
68
-
Note: Telemetry via return channel through the receiver is not supported by SITL (yet).
82
+
### Telemtry
83
+
84
+
LTM and MAVLink telemetry are supported, either as a discrete function or shared with MSP.
85
+
86
+
RX Telemetry via a return channel through the receiver is not yet supported by SITL.
69
87
70
88
## OSD
71
89
For the OSD the program INAV-Sim-OSD is available: https://github.com/Scavanger/INAV-SIM-OSD.
@@ -74,20 +92,22 @@ For this, activate MSP-Displayport on a UART/TCP port and connect to the corresp
74
92
Note: INAV-Sim-OSD only works if the simulator is in window mode.
75
93
76
94
## Command line
77
-
The command line options are only necessary if the SITL executable is started by hand, e.g. when debugging.
78
-
For normal use, please use the SITL tab in the configurator.
95
+
96
+
The command line options are only necessary if the SITL executable is started by hand.
97
+
98
+
There is also a SITL tab in the INAV Configurator (6.1.0 and later).
79
99
80
100
The following SITL specific command line options are available:
81
101
82
102
If SITL is started without command line options, only a serial MSP / CLI connection can be used (e.g. Configurator or other application) can be used.
83
103
84
-
```--path```Full path and file name to config file, if not present, eeprom.bin in the current directory is used. Example: ```C:\INAV_SITL\flying-wing.bin```
104
+
```--path```Path and file name to config file. If not present, eeprom.bin in the current directory is used. Example: ```C:\INAV_SITL\flying-wing.bin```, ```/home/user/sitl-eeproms/test-eeprom.bin```.
85
105
86
106
```--sim=[sim]``` Select the simulator. xp = X-Plane, rf = RealFlight. Example: ```--sim=xp```
87
107
88
-
```--simip=[ip]``` IP address of the simulator, if you specify a simulator with "--sim" and omit this option localhost (127.0.0.1) will be used. Example: ```--simip=172.65.21.15```
108
+
```--simip=[ip]```Hostname or IP address of the simulator, if you specify a simulator with "--sim" and omit this option IPv4 localhost (`127.0.0.1`) will be used. Example: ```--simip=172.65.21.15```, ```--simip acme-sims.org```, ```--sim ::1```.
89
109
90
-
```--simport=[port]``` Port number of the simulator, not necessary for all simulators. Example: ```--simport=4900```
110
+
```--simport=[port]``` Port number of the simulator, not necessary for all simulators. Example: ```--simport=4900```. For the X-Plane protocol, the default port is `49000`.
91
111
92
112
```--useimu``` Use IMU sensor data from the simulator instead of using attitude data directly from the simulator. Not recommended, use only for debugging.
93
113
@@ -100,6 +120,8 @@ Please also read the documentation of the individual simulators.
100
120
101
121
```--help``` Displays help for the command line options.
102
122
123
+
For options that take an argument, either form `--flag=value` or `--flag value` may be used.
124
+
103
125
## Running SITL
104
126
It is recommended to start the tools in the following order:
105
127
1. Simulator, aircraft should be ready for take-off
@@ -124,6 +146,8 @@ make
124
146
Compile under cygwin, then as in Linux.
125
147
Copy cygwin1.dll into the directory, or include cygwin's /bin/ directory in the environment variable PATH.
126
148
149
+
If the build fails (segfault, possibly out of memory), adding `-DCMAKE_BUILD_TYPE=MinRelSize` to the `cmake` command may help.
150
+
127
151
#### Build manager
128
152
129
153
`ninja` may also be used (parallel builds without `-j $(nproc)`):
@@ -135,12 +159,12 @@ ninja
135
159
136
160
### Compiler requirements
137
161
138
-
* Modern GCC. Must be a *real* GCC, macOS faking it with clang will not work.
162
+
* Modern GCC. Must be a *real* GCC, macOS faking it with clang will not work. GCC 10 to GCC 13 are known to work.
139
163
* Unix sockets networking. Cygwin is required on Windows (vice `winsock`).
140
164
* Pthreads
141
165
142
166
## Supported environments
143
167
144
-
* Linux on x86_64, Aarch64 (e.g. Rpi4), RISC-V (e.g. VisionFive2)
168
+
* Linux on x86_64, ia-32, Aarch64 (e.g. Rpi4), RISCV64 (e.g. VisionFive2)
0 commit comments