🦊:foxsi-4matter $ ./bin/formatter --verbose --uart --config foxsi4-commands/systems.json log file: log/auto_2023-12-05_13:02:13.log verbose printing on UART interfaces are enabled. reading file from foxsi4-commands/systems.json finding systems... adding new System: name: gse id code: 0 added an endpoint: (udp)192.168.1.118:9999 adding new System: name: downlink id code: 5 added an endpoint: (tcp)224.1.1.0:8888 adding new System: name: uplink id code: 5 has uart! adding new System: name: formatter id code: 1 local endpoint: 192.168.1.8 adding new System: name: housekeeping id code: 2 added an endpoint: (tcp)192.168.1.16:7777 no timing info provided for commanded system housekeeping adding new System: name: power id code: 3 adding new System: name: saas id code: 4 adding new System: name: cdtede id code: 8 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: cdte1 id code: 9 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: cdte2 id code: 10 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: cdte3 id code: 11 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: cdte4 id code: 12 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: timepix id code: 13 has uart! no timing info provided for commanded system timepix adding new System: name: cmos1 id code: 14 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: cmos2 id code: 15 added an endpoint: (tcp)192.168.1.100:10030 adding new System: name: broadcast id code: 254 adding commands for cmos1, 14... this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for timepix, 13... added system commands to deck adding commands for cdte4, 12... this Command was initialized as a read-command, but expects a zero-length reply this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for cdte3, 11... this Command was initialized as a read-command, but expects a zero-length reply this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for cdte2, 10... this Command was initialized as a read-command, but expects a zero-length reply this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for cdte1, 9... this Command was initialized as a read-command, but expects a zero-length reply this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for cdtede, 8... this Command was initialized as a read-command, but expects a zero-length reply this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for cmos2, 15... this Command was initialized as a read-command, but expects a zero-length reply added system commands to deck adding commands for housekeeping, 2... added system commands to deck Timing for cdtede: Timing:: period = 2250 ms command = 204 ms request = 204 ms reply = 1636 ms idle = 204 ms retry_max_count = 5 timeout = 10 ms intercommand_space = 3 ms endpoints: uplink: uart: timepix has uart interface uart interface: UART:: tty_path = /dev/ttyAMA1 baud_rate = 9600 parity = 0 stop_bits = 1 data_bits = 8 uplink has uart interface uart interface: UART:: tty_path = /dev/ttyAMA2 baud_rate = 192000 parity = 1 stop_bits = 1 data_bits = 8 machine: did something did something else trying to set ::reuse_address opening serial ports... failed to open uplink serial port!: open: No such file or directory failed to set serial port options!: set_option: Bad file descriptor loop: initializing housekeeping system got ethernet packet: 0x01 ff transmitting to housekeeping_system got ethernet packet: 0x02 ff transmitting to housekeeping_system got ethernet packet: 0x01 f0 transmitting to housekeeping_system got ethernet packet: 0x02 f0 transmitting to housekeeping_system initializing timepix system sending ping command: got into uart send! in sync_uart_send_command_for_sys(), sending 0x80 in sync_tcp_send_command_for_sys(), sent request waiting for response will resize uart buffer to 1 starting async uart read uart read timed out! got wrong uart reply length! got response!!: 0x no pingback from Timepix! ABANDONing. initializing cdte system checking canister status... in sync_tcp_send_command_for_sys(), sending 000000000000000000000016 0102 fe 01 4d 02 00000103 fe 0000 00 0000000c 000004 3c in sync_tcp_send_command_for_sys(), sent request waiting for response TransportLayerMachine::read() attempt 0 failed. TransportLayerMachine::read() attempt 1 failed. TransportLayerMachine::read() attempt 2 failed. TransportLayerMachine::read() attempt 3 failed. TransportLayerMachine::read() attempt 4 failed. All TransportLayerMachine::read() attempts failed! got wrong reply size! 0x00 00 00 00 pulling reply from 0x last header access: 24 message too short to parse! canisters status: 0x got too-short canister status reply! Abandoning CdTe.got too-short canister status reply! Abandoning CdTe.got too-short canister status reply! Abandoning CdTe.got too-short canister status reply! Abandoning CdTe.rmap write data lookup: 0x3c 3c 01 00 01 01 01 01 3c 3c 3c 3c 3e in sync_tcp_send_command_for_sys(), sending 000000000000000000000023 0102 fe 01 75 02 00000103 fe 0000 00 00000000 00000c b2 3c3c0100010101013c3c3c3c 3e in sync_tcp_send_command_for_sys(), sent request ^C 🦊:foxsi-4matter $ 🦊:foxsi-4matter $ 🦊:foxsi-4matter $