[daveh]

While trying to debug a problem with my newly build system I turned on some debugging in the TX software and came up against errors when I tried to compile it.

I changed the #define for Debug_Enable, DebugID0, DebugID2, DebugID3 and DebugID5 from false to true.

The errors from the compiler were -
Debug.ino: In function 'void printDebugID2()':
Debug.ino:37:20: error: 'WindDir_Text' was not declared in this scope
Process_IDx.ino: In function 'void send_SensorID2()':
Process_IDx.ino:73:3: error: 'WindDir_Text' was not declared in this scope
Process_IDx.ino:73:21: error: 'vaneDirectionsText' was not declared in this scope
Error compiling.

The solution I found was to change a line in the main ino file from
#if Local_TestMode == 1
to
#if DebugID2
which causes the variables to get defined. I couldn't find any other references to Local_TestMode.

I also had problems compiling because printDebugID2() has statements uncommented to print to an lcd. I simply had to comment those out and uncomment the Serial.print statements.

[Wizza]

Thanks for the post Dave. I experienced exactly the same issue last night, while working with the TX code, and was still not sure exactly why. I was going to ask Werk how we use the debug options (software is not my strongest point )....

Hopefully someone can shed more light on the issue here....

[werk_ag]

The solution I found was to change a line in the main ino file from
#if Local_TestMode == 1
to
#if DebugID2
which causes the variables to get defined. I couldn't find any other references to Local_TestMode.

Hi Daveh

You are right! That change should be done for DebugID2 to work.
Thanks.

I haven't touched the debug routines since long time, maybe there are some other caveats. On next software release I will revise them at least to be sure that when enabled, they don't cause any error when compiling.

I also had problems compiling because printDebugID2() has statements uncommented to print to an lcd. I simply had to comment those out and uncomment the Serial.print statements.

Leaving the lines that print to the LCD uncommented don't cause any compile error unless you don't have the correct LCD library installed.

[werk_ag]

Thanks for the post Dave. I experienced exactly the same issue last night, while working with the TX code, and was still not sure exactly why. I was going to ask Werk how we use the debug options (software is not my strongest point )....

Hopefully someone can shed more light on the issue here....

Hi Wizza

Do the change indicated by Daveh, around line 127, and DebugID2 should work.