CCB 2019-09-25: Merge #29, #32; FT #27

Reviewed and approved #29, #32 at 2019-09-25 CCB
FASTTRACKED #27 (documentation only)

Guide-Loading-Tables.txt

@@ -0,0 +1,63 @@
+Loading Table(s) - Guide
+------------------------
+
+reference(s): cfe_tbl.dox
+              cFE Application Developers Guide
+
+    1. Make sure the table image you want to load is in the onboard computer. 
+
+    2. Open Your GroundSystem. 
+
+           a. Select "Start Command System"
+
+           b. Select "Display Page" next to Table Services. This will take you to "Table Services" 
+              menu.
+
+           c. Select "Send" next to "Load Table". 
+
+           d. Enter the location and name of the table file you want to load in the input section:
+                  Example: /cf/MyTblDefault2.tbl
+
+           e. Select "send". If successful, you should see an event:
+              "Successful load of '/cf/<Your_Table_File_Name>' into '<Your_APP>.<Your_Table_Name>' work buffer"
+
+           f. At this point, your table is loaded but still "inactive". Before you can "activate" the 
+              table, you will have to "validate" it. Go back to "Table Services" menu.
+
+           g. Select "Send" next to "Validate Table".
+
+           h. There are two rows, "ActiveTblFlag" and "TableName". Fill it out accordingly.
+                  Example: "CFE_TBL_INACTIVE_BUFFER" for ActiveTblFlag
+                           "TO_LAB_APP.MyTblDefault" for TableName 
+
+                  *Note - TableName is the actual table name, not the table file name. 
+
+           i. Select "Send". If successful, you should see an event:
+              "<Your_App_Name> validation successful for Inactive '<Your_App_Name>.<Your_Table_Name>'"
+
+           j. Last step is to activate it. Go back to "Table Services" menu.
+
+           k. Select "Send" next to "Activate Table". 
+
+           l. Enter the table name you want to activate.
+                  Example: TO_LAB_APP.MyTblDefault
+
+                  *Note - This is the full table name, not your table file name. 
+
+              If successful, you should see an event:
+              "<Your_App_Name> Successfully updated '<Your_App_Name>.<Your_Table_Name>'"
+
+Note(s)
+-------
+
+    1. If you have an event that says the message is invalid when you send "validate" or "activate" 
+       command, check your ground station packet definitions vs. your cFS definitions. There
+       could be a mismatch between the lengths.
+
+    2. If you "validate" or "activate" and no events or errors occurred, your application is not 
+       passing through the "Table Manage API". "Validate" and "activate" are application level 
+       implementations. Check if you have:
+
+           a. CFE_TBL_Manage implemented.
+
+           b. CFE_TBL_Manage is being called.

Subsystems/cmdGui/CommandFiles/cfe__sb__msg_8h

@@ -68,4 +68,4 @@ aS'struct_c_f_e___s_b___write_file_info_cmd__t'
 p35
 aS'struct_c_f_e___s_b___cmd_hdr__t'
 p36
-aa.
+aa.

Subsystems/cmdGui/CommandFiles/cfe__time__msg_8h

@@ -98,4 +98,4 @@ aS'struct_c_f_e___t_i_m_e___time_cmd__t'
 p50
 aS'struct_c_f_e___t_i_m_e___time_cmd__t'
 p51
-aa.
+aa.

Subsystems/cmdGui/CommandFiles/sample_app_cmd

@@ -0,0 +1,17 @@
+(lp0
+(lp1
+S'SAMPLE_APP_NOOP_CC'
+p2
+aS'SAMPLE_APP_RESET_COUNTERS_CC'
+p3
+aS'SAMPLE_APP_PROCESS_CC'
+p4
+aa(lp5
+S'0'
+p6
+aS'1'
+p7
+aS'2'
+p8
+aag1
+a.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___e_s___delete_c_d_s_cmd__t

@@ -15,6 +15,6 @@ aa(lp9
 S'--string'
 p10
 aa(lp11
-S'16'
+S'38'
 p12
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___e_v_s___app_name_event_i_d_mask_cmd__t

@@ -33,8 +33,8 @@ aS'--half'
 p18
 ag18
 aa(lp19
-S'20'
+S'18'
 p20
 ag11
 ag11
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___s_b___en_rout_cmd__t

@@ -12,8 +12,8 @@ aa(lp7
 S'Spare byte to make command even number of bytes.'
 p8
 aa(lp9
-S'--byte'
+S'--long'
 p10
 aa(lp11
 g6
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___abort_ld_cmd__t

@@ -15,6 +15,6 @@ aa(lp9
 S'--string'
 p10
 aa(lp11
-S'16'
+S'38'
 p12
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___activate_cmd__t

@@ -15,6 +15,6 @@ aa(lp9
 S'--string'
 p10
 aa(lp11
-S'16'
+S'38'
 p12
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___del_c_d_s_cmd__t

@@ -15,6 +15,6 @@ aa(lp9
 S'--string'
 p10
 aa(lp11
-S'16'
+S'38'
 p12
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___dump_cmd__t

@@ -37,6 +37,6 @@ aa(lp20
 g10
 aS'16'
 p21
-aS'64'
+aS'86'
 p22
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___tlm_reg_cmd__t

@@ -15,6 +15,6 @@ aa(lp9
 S'--string'
 p10
 aa(lp11
-S'16'
+S'38'
 p12
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_b_l___validate_cmd__t

@@ -26,6 +26,6 @@ aS'--string'
 p15
 aa(lp16
 g8
-aS'16'
+aS'38'
 p17
-aa.
+aa.

Subsystems/cmdGui/ParameterFiles/struct_c_f_e___t_i_m_e___signal_cmd__t

@@ -5,4 +5,4 @@ a(lp3
 a(lp4
 a(lp5
 a(lp6
-a.
+a.

Subsystems/cmdGui/command-pages.txt

@@ -28,3 +28,4 @@ Time Services (CPU1),       cfe__time__msg_8h,  0x1805, LE, UdpCommands.py,  127
 Event Services (CPU1),      cfe__evs__msg_8h,   0x1801, LE, UdpCommands.py,  127.0.0.1,   1234
 Command Ingest LAB,         ci_lab_msg,         0x1884, LE, UdpCommands.py,  127.0.0.1,   1234
 Telemetry Output LAB,       to_lab_msg,         0x1880, LE, UdpCommands.py,  127.0.0.1,   1234
+Sample App (CPU1),          sample_app_cmd,     0x1882, LE, UdpCommands.py,  127.0.0.1,   1234