Rob Bocchino

This isn't a bug; it's in the language specification. Limits are for numeric types only. In particular, it is not clear what a low or high limit should mean for...

Sure, we could add the feature of specifying red, orange, and yellow *values* (as opposed to limits) for any telemetry channel type. Can you open a discussion topic on this,...

This looks great! I suggest we do the following: - [x] Merge https://github.com/nasa/fprime/pull/2485. This will bring fpp/main into sync with fprime/devel. - [x] Merge https://github.com/fprime-community/fpp/pull/385. - [x] Make a new...

I am working on integrating this PR with FPP. It's looking good so far. Here is one issue I see: `FW_OBJECT_NAME_MAX_SIZE` is technically not a correct name. It should be...

I agree, let's defer this to a separate issue.

We should also consider auto-defining FW_ARRAY_TO_STRING and FW_SERIALIZABLE_TO_STRING to 1 on the command line when building unit tests. This would make it easier for users.

Also, we should merge FW_ARRAY_TO_STRING and FW_SERIALIZABLE_TO_STRING into the same condition. This is an FPP issue. See https://github.com/fprime-community/fpp/issues/375.

Maybe I'm missing something, but it seems this revised algorithm should handle all the comments and use cases so far: 1. Open the file 2. For each data packet received,...

Note: I'm assuming that we currently check the CRC against the file data. To do that, we have to know the size of the data in the file, so we...

Also, looking at the design, it seems that the CRC in the end packet is compared against the CRC computed from the file data. So I don't understand how the...