Specification • The receiver shall send a positive acknowledgment (ACK) packet for each DATA packet received without error.
COMS
Current Filters
Clear all
Allocation of Service Types and Subtypes
Specification • The PUS provides a standard set of services that are targeted for communication between spacecraft and ground systems. Many of them may not be applicable to on-board communication between applications. However, nothing precludes their use in a JAS-based system. The PUS can be extended to add additional functionality to existing...
Buffer Fragmentation and Reassembly
Specification • In cases where a higher-level transmit application (or higher layer in a communications stack) must transmit a buffer of data that exceeds the JRDDP MTU size, the buffer must be fragmented into a series of JRDDP packets and then reassembled at the receive TEP before returning the buffer to the...
Buffer Segmentation and Reassembly
Specification • In cases where a higher-level transmit application, or higher layer in a communications stack, must transmit a buffer of data that exceeds the JEEP MTU size, the buffer must be segmented into a series of JEEP packets and then reassembled at the receive TEP before returning the buffer to the...
CCSDS Telecommand and Telemetry Format Packet Standard
Specification • CCSDS Space Packet The CCSDS packet format consists of a packet primary header and packet data field. The header provides routing information for the packet and metadata that describes the packet. The data field is intended to be a user-defined field that can be customized for applications. Details of how...
Channel Closing Process
Specification • The following sections present the interactions (in the form of UML Sequence Diagrams) between transmit and receive endpoints while closing a channel. Various error conditions are presented in order to show nominal, delayed, and worst case scenarios. The hexagonal icons represent the TEP states while the dashed green lines represent...
Channel Independence
Specification • Each transport channel shall operate independently from other transport channels.
Channel Operations
Specification •
Communication Specification
Specification • The Communication Specification provides details about network interfaces, communication services, and packet structures that were described in the Communication Profile. The figure below provides context of where the Communication Specification resides in the JAS standard. JAS Standard Hierarchy
Data Transmit Queue
Specification • When packets from more than one channel are available for transmit, packets shall be transmitted in the order in which they are queued and in accordance with the transmit priority described above.
Data Types
Specification • The JAS standard does not require a specific length or encoding format for data types. Systems can define these based on what best suits their needs. Sizes, endianness, byte ordering, and bit ordering are typically driven based on the processing and memory architectures that are used. However, in order to...
Delayed Case
Specification • A delayed but recoverable scenario occurs when a receive TEP receives at least one CLOSE packet but the transmit TEP does not receive any ACK packets as shown in Figure 3. In this case the receive TEP will eventually transition to the CLOSED state via the timeout and the transmit...
Device Access Service
Specification • The device access service, service type address 128, is used to request parameters from or command parameters to a specific device. The currently defined device access service parameters are shown in the following table. Service Type Service Subtype Subtype Description Cmd Tlm Service Parameters Data Types and Description 128 1...
ECSS Packet Utilization Standard
Specification • The figures below show a PUS telecommand and telemetry packet and their utilization within the CCSDS space packet specification. The PUS specification uses the user-definable fields of the CCSDS space packet in order to create a PUS packet. The specification defines a secondary header that provides additional metadata such as...
Error Detection
Specification • Packet errors shall be detected by adding a CRC to each packet transmitted, checking it at the receiver, and discarding any erroneous packet.
File Access Service
Specification • The file access service, service type address 129 is used to read from or write to files within a file system. The currently defined file access service parameters are shown in the following table. Service Type Service Subtype Subtype Description Cmd Tlm Service Parameters Data Types and Description 129 1...
Functional Description
Specification • The JEEP provides efficient, best-effort delivery of packets. In-order delivery is only guaranteed if there are no transmission errors over the SpaceWire link, e.g., bit errors or dropped packets, and there are no routing options which could cause a segmented packet to be transmitted or received out of order. JEEP...
Header
Specification • JRDDP Packet Format Destination Address The first byte of the header shall contain the Destination SpaceWire Logical Address (SLA) field that is associated with the destination TEP to which the packet is being sent. Protocol ID The second byte of the header shall contain the SpaceWire Protocol ID field and...
JAS Command Packet
Specification • JAS Command Packet All fields are shown in bits. The variable length application data field must be an integral number of bytes for the packet error control calculation. Spare bits may be used for padding purposes at the end to ensure the packets are an even number of bytes in...
JAS Efficient Exchange Protocol
Specification • The JAS Efficient Exchange Protocol (JEEP) uses the lower level SpaceWire data link layer to provide data delivery services to one or more higher level application processes. This document specifies the functional requirements for JEEP but does not specify the interfaces to the lower or higher level processes, which may...
JAS Packet Definition
Specification • The JAS Packet is built upon CCSDS and PUS packet standards. Some modifications were made to enforce a layered architecture in order to promote reuse of applications. The following sections will highlight these differences in more detail.
JAS Packet Service
Specification • Error: unable to migrate element with tag="" The CCSDS/SOIS subnetwork packet service standard can be referenced if a generic packet service is needed. The JAS Packet Service is an implementation of the CCSDS/SOIS packet service, specifically tailored for the JAS packet. The following diagram shows how the JAS Packet Service...
JAS Packets
Specification • Applications require a messaging format to allow them to communicate with each other. Legacy programs may already have a messaging format that they prefer to use. There is nothing that precludes any of the JAS communication protocols or data links from supporting these formats. The JAS Packet was developed for...
JAS Reliable Data Delivery Protocol
Specification • The JAS Reliable Data Delivery Protocol (JRDDP) uses the lower level SpaceWire data link layer to provide reliable packet delivery services to one or more higher level host application processes. This document specifies the functional requirements for JRDDP but does not specify the interfaces to the lower or higher level...
JAS Specific Services Definitions
Specification • The JAS specific services will be based on the PUS service concept. Most PUS services were created for communication between onboard applications and ground systems. JAS adds additional services to support more onboard payload functions. [Placeholder: Additional development is needed to define the JAS specific services to support onboard payload...
Results 1–25 of 61