Clooney82 / MavLink_FrSkySPort

This MavLink_FrSkySPort repository is discontinued! The development is moved to athertop/MavLink_FrSkySPort. Please do not use this repo, and follow the link to athertop.
https://github.com/athertop/MavLink_FrSkySPort
GNU General Public License v3.0
61 stars 17 forks source link

Arduino compiling problem #56

Closed Luftpumpa252 closed 8 years ago

Luftpumpa252 commented 8 years ago

Hello when arduino is compiling telemetry code, arduino error occur.

Arduino: 1.6.7 (Windows 10), TD: 1.27, Vývojová deska: "Teensy 3.2 / 3.1, Serial, 72 MHz optimized, US English"

FrSkySPortTelemetry:116: error: token "Â" is not valid in preprocessor expressions

if defined USE_SINGLE_CELL_MONITOR || defined USE_FLVSS_FAKE_SENSOR_DATA

^ exit status 1 token "Â" is not valid in preprocessor expressions

athertop commented 8 years ago

That "Â" character does not exist in the source code. Is your desktop maybe doing some strange language translation perhaps?

Luftpumpa252 commented 8 years ago

Hm, edit #if defined USE_SINGLE_CELL_MONITOR || defined USE_FLVSS_FAKE_SENSOR_DATA to

if defined USE_SINGLE_CELL_MONITOR||defined USE_FLVSS_FAKE_SENSOR_DATA and now is working.

athertop commented 8 years ago

I am using the freshly downloaded source, and it compiles perfectly for me on a Mac using Arduino 1.6.4. It appears you have a newer version of Arduino, but those spaces should nor make any difference. Your original post stated the error was due to a stray character in the line (FrSkySPortTelemetry:116: error: token "Â" is not valid in preprocessor expressions), but you don't mention this above. Did you initially download the zip file and unpack it to get the source files onto your PC? or did you cut/paste from the source in Github (this could introduce stray chars, so downloading the zip avoids this).

gnkarn commented 8 years ago

Try this, go to the line with the error indicated by compiler Delete the line completely, Type it again,.

That would resolve that problem ,

Saludos

athertop commented 8 years ago

The issue is now resolved