The PEAK CAN Ethernet Gateway
The PEAK gateway is configured to send all of its CAN data via TCP to the CAN_LOCAL interface which runs a tcp ip server on port 4000 of the COSMOS machine.
The PEAK sends out all CAN packets via TCP in this standard 36-byte format. ↓
Our Cosmos configuration which is located in DS1OPS/flatsat/config/targets/CAN_LOCAL/cmd_tlm/tlm.txt is modeled after the Peak's packet structure as seen below.
Tlm.txt is filled with quite a few packet declarations like this. What allows Cosmos to differentiate one 36 byte packet from another is the ID_ITEM CANID_ID which contains the 29 bit extended CAN id. This allows us to process the 8 byte field which contains the actual data correctly. If a message's id is not yet in our COSMOS tlm.txt file, it will be identified as a general_can_message.
First to get commands working you must change the ip and port of the CAN_LOCAL_CMD interface to match either the route configured on your PEAK Ethernet gateway or whatever server you may have set up. That is located in DS1OPS/flatsat/config/targets/CAN_LOCAL/cmd_tlm_server.txt . The Commands are structured identically to the telemtry objects and they reside in DS1OPS/flatsat/config/targets/CAN_LOCAL_CMD/cmd_tlm/cmd.txt .