LTES

The command accept counter does increment.

The config command does now work for LED1, LED2 and Processor Watchdog. However, telemetry is indicating the opposite status. i.e. if I command LED1 ON, telemetry shows it's OFF, but the GSE can verify it is, in fact, ON. Same for LED2 and Processor Watchdog. CAL FLAG still shows no effect either way. Flash Power also show ON all the time. Is it possible, just all of the binary states in Config Status telemetry are inverted? (Image Number seems OK).

With FPGA 3.12, LED1 & LED2 status are correct. Actually tested with GSE to verify their respective outputs are really on or off as expected. Also verified Processor Watchdog status in telemetry is now correct. Also verified the functionality of the Processor Watchdog, by enabling it, then starting up the GRMON debugger and observe that LTES does actually reboot.
However, Cal Flag Status is apparently a FSW issue, so keeping this issue open until that is resolved.

Turns out 3.12 didn't totally fix this. More in depth testing shows the following:
If I command LED1=ON, LED2=OFF, telemetry will show that.
If I command LED1=OFF, LED2=ON, telemetry will show that.
If I command LED1=OFF, LED2=OFF, telemetry will both LED's ON.
If I command LED1=ON, LED2=ON, telemetry will show LED's OFF.

This has been fixed in the following ways:
1. The first bit in the Config Status byte was LED1, now it's LED2.
2. The second bit in the Config Status byte was LED2, now it's LED1.
3. FPGA version 3.14 has inverted those 2 bits from what the FPGA was doing before, so now 0=off, 1=on.
The Command and Telemetry spec, DSPC101005, needs to be updated to reflect the first 2 bits swapping.