CF app didn't use Sch Pipe for Schedule Messages

[ynielson]

CF app used Cmd Pipe for all messages(Cmd messages, Schedule messages, Incoming PDUs). Schedule messages should be received through Sch Pipe.(CF_WAKE_UP_REQ_CMD_MID, CF_SEND_HK_MID). And Incoming PDU messages can be received through Data Pipe rather than Cmd Pipe.

• Test case: Test_CF_AppPipe_HousekeepingCmdPbSuccess(), Test_CF_AppPipe_HousekeepingCmdUpFreezeErr()

[ynielson]

Based on the MID numbers for the incoming PDUs(CF_PPD_TO_CPD_PDU_MID, CF_GND_TO_CPD_PDU_MID), these two MIDs have their own MIDs rather than "CF_CMD_MID", although these two MIDs are both defined as CMD_MSG.

So these two MIDs have the form of Cmd Message but without "command code", And in case of the incoming Cmd MID, CF_GND_TO_CPD_PDU_MID, the response message is configured to send as a Tlm Msg through the Pb channel 1 with timestamp, if the file is "Class 2".

These are just a factor to consider when deciding which pipe to use. Other than the pipe, the app is coded to handle both Cmd Msg and Tlm Msg when sending the Pb Message/Incoming Ack. And it works, even though the app used the command pipe for all messages.