Communication Specification
Platform Management Service
Domain(s)
Space
System(s)
Satellite
Specialty
COMS
Profile(s)
CH, COMM, RP
Specification Type
Implementation
Citation(s)
Internal_Standard
The platform management service, service type address 130 is used to configure, manage, and monitor network specific resources. The currently defined platform management service parameters are shown in the following table.
| Service Type | Service Subtype | Subtype Description | Cmd | Tlm | Service Parameters | Data Types and Description |
| 130 | 11 | Network Topology Upload | X | N, Discovery_Map | N is an unsigned integer and is the number of routers defined in the topology; Discovery_Map is an N element array where each element consists of [Device_ID, M, [SpW_Addr, SpW_Addr, …]]; Device_ID is unsigned integer that identifies the router; M is an unsigned integer specifying the number of physical SpaceWire addresses to reach the router from the node performing the discovery, and the last argument is an unsigned character array containing M SpW addresses. | |
| 130 | 1 | Network Run Discovery Algorithm | X | |||
| 130 | 2 | Network Topology Table Request | X | |||
| 130 | 3 | Network Topology Table Report | X | N,Topology Table | N is an unsigned integer and is the number of routers defined in the topology; Topology_Table is an N element array where each element consists of [Device_ID, Router_Addr, M, [Endpoint_Addr, Port]]. Device_ID is unsigned integer that identifies the router; Router_Addr is an unsigned character which is the SpW address of the router; M is an unsigned integer specifying the number of subsequent entries which are the endpoints, and the last argument is an 2 element unsigned character array where the first element is the SpW address of the endpoint and the second element is the port number on the router it can be accessed from. | |
| 130 | 12 | Routing Table Upload | X | N, Routing_Table | N is an unsigned integer and is the number of routers and defines how many devices are specified in the subsequent tables. Routing_Table is an N element array where each element consists of [Device_ID, Router_Addr, M, [Endpoint_Addr, Primary_Port, Secondary_Port, Header_Delete_Flag]]. Device_ID is an unsigned integer that identifies the Router; Router_Addr is an unsigned character which is the SpW address of the router; M is an unsigned integer specifying the number of subsequent entries that are the endpoints, and the last argument is a 4 element unsigned character array where the first element is the SpW address of the endpoint, the second element is the primary router port, the third element is the secondary router port, and the fourth element is the header delete flag. | |
| 130 | 4 | Routing Run Routing Algorithm | X | |||
| 130 | 6 | Routing Load Tables | X | |||
| 130 | 7 | Routing Tables Request | X | |||
| 130 | 8 | Routing Tables Report | X | N, Routing_Table | N is an unsigned integer and is the number of routers and defines how many devices are specified in the subsequent tables. Routing_Table is an N element array where each element consists of [Device_ID, Router_Addr, M, [Endpoint_Addr, Primary_Port, Secondary_Port, Header_Delete_Flag]]. Device_ID is an unsigned integer that identifies the Router; Router_Addr is an unsigned character which is the SpW address of the router; M is an unsigned integer specifying the number of subsequent entries that are the endpoints, and the last argument is a 4 element unsigned character array where the first element is the SpW address of the endpoint, the second element is the primary router port, the third element is the secondary router port, and the fourth element is the header delete flag. | |
| 130 | 9 | Routing Table From Router Request | X | Device_ID | Device_ID is an unsigned integer that identifies the router. This identifier can be used as an abstract identifier to index a configuration table that contains the physical interface for accessing the router. | |
| 130 | 10 | Routing Table From Router Report | X | Device_ID, Router_Addr, M, Routing_Table | Device_ID is an unsigned integer that identifies the router. Router_Addr is an unsigned character which is the router address. M is an unsigned integer which identifies the number of entries in the routing table. Routing_Table is an M x 4 element array where each entry contains [Endpoint_Addr, Primary_Port, Secondary_Port, Header_Delete_Flag]. Endpoint_Addr is the SpW address of the endpoint entry in the router; Primary_Port, Secondary_Port, and Header_Delete_Flag are the attributes for that routing table entry. | |
| 130 | 20 | Hardware Application Load | X | File_System_ID, File_ID, Device_ID | File_ID is an unsigned integer that identifies the application to load. This identifier is used to determine the location of the file (file system and file name). Device_ID is an unsigned integer that specifies the node and part to load the application on. | |
| 130 | 21 | Hardware Application Configure | X | App_ID | App_ID is an unsigned integer that identifies the application to configure. App_ID maps to an application identifier as defined in the JAS packet format. | |
| 130 | 22 | Hardware Application Start | X | App_ID | App_ID is an unsigned integer that identifies the application to start. App_ID maps to an application identifier as defined in the JAS packet format. | |
| 130 | 23 | Hardware Application Stop | X | App_ID | App_ID is an unsigned integer that identifies the application to stop. App_ID maps to an application identifier as defined in the JAS packet format. | |
| 132 | 1 | Network Discover Topology | X | Used as part of the network discovery algorithm to discovery the topology of the network. For now the service type and subtype are 132,1 but in the future if this packet exists it will probably live within the Platform Management Service |
JAS Platform Management Service Parameters
Internal_Standard
"Internal Standards developed by Sandia National Laboratories". Experience Base, Sandia National Laboratories, Albuquerque, NM, 0000.