multi compilation fixes
This commit is contained in:
@@ -160,9 +160,9 @@ static void processMultiTelemetryPaket(const uint8_t *packet)
|
||||
|
||||
case FrskySportPolling:
|
||||
#if defined(LUA)
|
||||
if (len >= 1 && outputTelemetryBufferSize > 0 && data[0] == outputTelemetryBufferTrigger) {
|
||||
if (len >= 1 && outputTelemetryBuffer.size > 0 && data[0] == outputTelemetryBuffer.trigger) {
|
||||
TRACE("MP Sending sport data out.");
|
||||
sportSendBuffer(outputTelemetryBuffer, outputTelemetryBufferSize);
|
||||
sportSendBuffer(outputTelemetryBuffer.data, outputTelemetryBuffer.size);
|
||||
}
|
||||
#endif
|
||||
break;
|
||||
|
||||
@@ -259,8 +259,8 @@ void telemetryInit(uint8_t protocol)
|
||||
// The DIY Multi module always speaks 100000 baud regardless of the telemetry protocol in use
|
||||
telemetryPortInit(MULTIMODULE_BAUDRATE, TELEMETRY_SERIAL_8E2);
|
||||
#if defined(LUA)
|
||||
outputTelemetryBufferSize = 0;
|
||||
outputTelemetryBufferTrigger = 0x7E;
|
||||
outputTelemetryBuffer.size = 0;
|
||||
outputTelemetryBuffer.trigger = 0x7E;
|
||||
#endif
|
||||
}
|
||||
else if (protocol == PROTOCOL_TELEMETRY_SPEKTRUM) {
|
||||
|
||||
Reference in New Issue
Block a user