Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- dtorkin@ubuntu1:~/Desktop/practice$ nc localhost 12345
- EVENT;SVM_ID:0;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x08
- EVENT;SVM_ID:1;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x09
- EVENT;SVM_ID:2;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x0A
- EVENT;SVM_ID:3;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x0B
- SENT;SVM_ID:0;Type:128;Num:0;LAK:0x08
- EVENT;SVM_ID:0;Type:ResponseTimeout;Details:CmdType=128,CmdNum=0
- EVENT;SVM_ID:0;Type:LinkStatus;Details:NewStatus=3,AssignedLAK=0x08
- SENT;SVM_ID:1;Type:128;Num:0;LAK:0x09
- EVENT;SVM_ID:1;Type:ResponseTimeout;Details:CmdType=128,CmdNum=0
- EVENT;SVM_ID:1;Type:LinkStatus;Details:NewStatus=3,AssignedLAK=0x09
- SENT;SVM_ID:2;Type:128;Num:0;LAK:0x0A
- EVENT;SVM_ID:2;Type:ResponseTimeout;Details:CmdType=128,CmdNum=0
- EVENT;SVM_ID:2;Type:LinkStatus;Details:NewStatus=3,AssignedLAK=0x0A
- SENT;SVM_ID:3;Type:128;Num:0;LAK:0x0B
- EVENT;SVM_ID:3;Type:ResponseTimeout;Details:CmdType=128,CmdNum=0
- EVENT;SVM_ID:3;Type:LinkStatus;Details:NewStatus=3,AssignedLAK=0x0B
- dtorkin@ubuntu1:~/Desktop/practice$ sudo ./uvm_app --wait-for-gui OR
- UVM: Option --wait-for-gui enabled. Will wait for GUI connection.
- DEBUG UVM: Effective RadarMode selected: 0
- UVM: Загрузка конфигурации...
- Configuration parsed successfully from 'config.ini'.
- Found configurations for 4 SVM instances in file.
- --- Effective Configuration ---
- interface_type = ethernet
- UVM Target: 192.168.189.129:8080
- SVM 0: Port=8080, LAK=0x08 (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 1: Port=8081, LAK=0x09 (Loaded: Yes)
- Simulate Control Failure: Yes
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 2: Port=8082, LAK=0x0A (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: Yes
- Send Warning on Confirm: No (TKS: 1)
- SVM 3: Port=8083, LAK=0x0B (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: 5 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- -----------------------------
- UVM: Found 4 SVM configurations in config file.
- Thread-safe UVM request queue created with capacity 50
- Thread-safe UVM Response queue created with capacity 200
- UVM: Connecting to SVMs...
- DEBUG UVM: IP before loop: 192.168.189.129
- UVM: Attempting to connect to SVM ID 0 (IP: 192.168.189.129, Port: 8080)...
- DEBUG UVM: Preparing to create interface for SVM 0 with IP=192.168.189.129, Port=8080
- Ethernet: Connected to 192.168.189.129:8080 (handle: 3)
- UVM: Successfully connected to SVM ID 0 (Handle: 3).
- UVM: Attempting to connect to SVM ID 1 (IP: 192.168.189.129, Port: 8081)...
- DEBUG UVM: Preparing to create interface for SVM 1 with IP=192.168.189.129, Port=8081
- Ethernet: Connected to 192.168.189.129:8081 (handle: 4)
- UVM: Successfully connected to SVM ID 1 (Handle: 4).
- UVM: Attempting to connect to SVM ID 2 (IP: 192.168.189.129, Port: 8082)...
- DEBUG UVM: Preparing to create interface for SVM 2 with IP=192.168.189.129, Port=8082
- Ethernet: Connected to 192.168.189.129:8082 (handle: 5)
- UVM: Successfully connected to SVM ID 2 (Handle: 5).
- UVM: Attempting to connect to SVM ID 3 (IP: 192.168.189.129, Port: 8083)...
- DEBUG UVM: Preparing to create interface for SVM 3 with IP=192.168.189.129, Port=8083
- Ethernet: Connected to 192.168.189.129:8083 (handle: 6)
- UVM: Successfully connected to SVM ID 3 (Handle: 6).
- UVM: Connected to 4 out of 4 configured SVMs.
- UVM: Запуск потоков Sender, Receiver(s) и GUI Server...
- UVM: Waiting for GUI client to connect on port 12345 (or press Ctrl+C)...
- UVM Sender thread started.
- UVM Receiver thread started for SVM ID 0 (handle: 3).
- UVM Receiver thread started for SVM ID 2 (handle: 5).
- UVM Receiver thread started for SVM ID 3 (handle: 6).
- GUI Server: Starting listener on port 12345
- GUI Server: Waiting for GUI connection on port 12345...
- UVM Receiver thread started for SVM ID 1 (handle: 4).
- GUI Server: Accepted connection from 127.0.0.1:33756 (FD 8)
- GUI Server: Sending initial state to new GUI client (FD 8).
- GUI Server: Initial state sent to GUI client (FD 8).
- UVM: GUI client connected! Proceeding with SVM operations.
- UVM: All necessary threads started. Selected RadarMode: 0
- --- Подготовка к сеансу наблюдения ---
- UVM Main: Starting observation prep for SVM ID 0 (LAK 0x08)
- UVM (SVM 0): Sending msg type 128 (num 0) and waiting for response type 129...
- Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=3
- Получено сообщение через Ethernet: Тип=129, Номер=0, Длина тела=12, Handle=3
- UVM (SVM 0): TIMEOUT waiting for response type 129 (for sent msg num 0)!
- UVM Main (SVM 0): Failed InitChannel sequence. Skipping further prep.
- UVM Main: Starting observation prep for SVM ID 1 (LAK 0x09)
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (SVM 0): Connection closed by SVM. Marking link as INACTIVE.
- UVM Receiver thread for SVM ID 0 finished.
- UVM (SVM 1): Sending msg type 128 (num 0) and waiting for response type 129...
- Sender Thread: Cannot send message to SVM ID 1 (inactive or invalid).
- UVM (SVM 1): TIMEOUT waiting for response type 129 (for sent msg num 0)!
- UVM Main (SVM 1): Failed InitChannel sequence. Skipping further prep.
- UVM Main: Starting observation prep for SVM ID 2 (LAK 0x0A)
- UVM (SVM 2): Sending msg type 128 (num 0) and waiting for response type 129...
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (SVM 1): Connection closed by SVM. Marking link as INACTIVE.
- UVM Receiver thread for SVM ID 1 finished.
- Sender Thread: Cannot send message to SVM ID 2 (inactive or invalid).
- UVM (SVM 2): TIMEOUT waiting for response type 129 (for sent msg num 0)!
- UVM Main (SVM 2): Failed InitChannel sequence. Skipping further prep.
- UVM Main: Starting observation prep for SVM ID 3 (LAK 0x0B)
- UVM (SVM 3): Sending msg type 128 (num 0) and waiting for response type 129...
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (SVM 2): Connection closed by SVM. Marking link as INACTIVE.
- UVM Receiver thread for SVM ID 2 finished.
- Sender Thread: Cannot send message to SVM ID 3 (inactive or invalid).
- UVM (SVM 3): TIMEOUT waiting for response type 129 (for sent msg num 0)!
- UVM Main (SVM 3): Failed InitChannel sequence. Skipping further prep.
- --- Подготовка к сеансу съемки ---
- DEBUG UVM: Mode before sending parameters: 0
- UVM: Все сообщения подготовки к съемке отправлены.
- UVM: Ожидание асинхронных сообщений от SVM (или Ctrl+C для завершения)...
- UVM Main: Ignored message type 129 from non-active/failed SVM ID 0 (Status: 0)
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (SVM 3): Connection closed by SVM. Marking link as INACTIVE.
- UVM Receiver thread for SVM ID 3 finished.
- dtorkin@ubuntu1:~/Desktop/practice$ sudo ./svm_app
- [sudo] пароль для dtorkin:
- SVM Multi-Port Server starting...
- Message handlers initialized.
- SVM: Loading configuration...
- Configuration parsed successfully from 'config.ini'.
- Found configurations for 4 SVM instances in file.
- --- Effective Configuration ---
- interface_type = ethernet
- UVM Target: 192.168.189.129:8080
- SVM 0: Port=8080, LAK=0x08 (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 1: Port=8081, LAK=0x09 (Loaded: Yes)
- Simulate Control Failure: Yes
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 2: Port=8082, LAK=0x0A (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: Yes
- Send Warning on Confirm: No (TKS: 1)
- SVM 3: Port=8083, LAK=0x0B (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: 5 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- -----------------------------
- SVM: Will attempt to start 4 instances based on config.
- DEBUG SVM MAIN - Instance 0 Settings: LAK=0x08, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
- DEBUG SVM MAIN - Instance 1 Settings: LAK=0x09, simulate_control_failure=1, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
- DEBUG SVM MAIN - Instance 2 Settings: LAK=0x0A, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=1, send_warning=0, tks=1
- DEBUG SVM MAIN - Instance 3 Settings: LAK=0x0B, simulate_control_failure=0, disconnect_after=5, simulate_timeout=0, send_warning=0, tks=1
- SVM: Loading configuration...
- Configuration parsed successfully from 'config.ini'.
- Found configurations for 4 SVM instances in file.
- --- Effective Configuration ---
- interface_type = ethernet
- UVM Target: 192.168.189.129:8080
- SVM 0: Port=8080, LAK=0x08 (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 1: Port=8081, LAK=0x09 (Loaded: Yes)
- Simulate Control Failure: Yes
- Disconnect After: -1 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM 2: Port=8082, LAK=0x0A (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: -1 messages
- Simulate Response Timeout: Yes
- Send Warning on Confirm: No (TKS: 1)
- SVM 3: Port=8083, LAK=0x0B (Loaded: Yes)
- Simulate Control Failure: No
- Disconnect After: 5 messages
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- -----------------------------
- SVM: Will attempt to start 4 instances based on config.
- Thread-safe QueuedMessage queue created with capacity 400
- SVM: Listener thread 0 initiated for Port 8080 (LAK 0x08).
- SVM: Listener thread 1 initiated for Port 8081 (LAK 0x09).
- SVM: Listener thread 2 initiated for Port 8082 (LAK 0x0A).
- SVM: Listener thread 3 initiated for Port 8083 (LAK 0x0B).
- SVM: Starting common threads (Timer, Sender)...
- SVM: All common threads started. 4 listeners active. Running...
- SVM Main: Waiting for shutdown signal...
- Ethernet: Listening on port 8080 (handle: 3)
- Listener thread started for SVM ID 0 (LAK 0x08, Port 8080, Listen FD 3)
- Listener (SVM 0): Waiting for connection on port 8080...
- Ethernet: Listening on port 8081 (handle: 5)
- Listener thread started for SVM ID 1 (LAK 0x09, Port 8081, Listen FD 5)
- Listener (SVM 1): Waiting for connection on port 8081...
- Ethernet: Listening on port 8082 (handle: 7)
- Listener thread started for SVM ID 2 (LAK 0x0A, Port 8082, Listen FD 7)
- Listener (SVM 2): Waiting for connection on port 8082...
- Ethernet: Listening on port 8083 (handle: 9)
- Listener thread started for SVM ID 3 (LAK 0x0B, Port 8083, Listen FD 9)
- Listener (SVM 3): Waiting for connection on port 8083...
- SVM Timer thread started.
- SVM Sender thread started (reads global outgoing queue).
- Listener (SVM 0): Accepted connection from 192.168.189.128:45914 (Client FD 4)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 0): Instance activated. Worker threads started.
- Listener (SVM 1): Accepted connection from 192.168.189.128:41620 (Client FD 6)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 1): Instance activated. Worker threads started.
- SVM Processor thread started for instance 0.
- SVM Receiver thread started for instance 0 (handle: 4).
- SVM Receiver thread started for instance 1 (handle: 6).
- SVM Processor thread started for instance 1.
- Listener (SVM 2): Accepted connection from 192.168.189.128:53122 (Client FD 8)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 2): Instance activated. Worker threads started.
- SVM Processor thread started for instance 2.
- Listener (SVM 3): Accepted connection from 192.168.189.128:57012 (Client FD 10)
- Thread-safe QueuedMessage queue created with capacity 100
- SVM Receiver thread started for instance 2 (handle: 8).
- Listener (SVM 3): Instance activated. Worker threads started.
- SVM Receiver thread started for instance 3 (handle: 10).
- SVM Processor thread started for instance 3.
- Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=4
- Processor (Inst 0): Обработка 'Инициализация канала'
- Параметры: LAUVM=0x1, LAK=0x08 (assigned)
- SVM (Inst 0): Эмуляция выключения лазера...
- Ответ 'Подтверждение инициализации' сформирован (LAK=0x08).
- Отправка сообщения через Ethernet: Тип=129, Номер=0, Длина тела=12, Общий размер=18, Handle=4
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (Inst 0): Connection closed by UVM. Stopping instance.
- Receiver Thread (Inst 0): Marked instance as inactive.
- Receiver Thread (Inst 0): Shutting down incoming queue.
- Thread-safe QueuedMessage queue shutdown initiated.
- SVM Receiver thread finished for instance 0.
- Processor Thread (Inst 0): Incoming queue empty and shutdown. Exiting.
- SVM Processor thread finished for instance 0.
- Listener (SVM 0): Receiver thread joined.
- Listener (SVM 0): Processor thread joined.
- Listener (SVM 0): Worker threads finished. Cleaning up instance...
- Ethernet: Closing handle 4
- Thread-safe QueuedMessage queue destroyed
- Listener (SVM 0): Instance deactivated. Ready for new connection.
- Listener (SVM 0): Waiting for connection on port 8080...
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (Inst 1): Connection closed by UVM. Stopping instance.
- Receiver Thread (Inst 1): Marked instance as inactive.
- Receiver Thread (Inst 1): Shutting down incoming queue.
- Thread-safe QueuedMessage queue shutdown initiated.
- SVM Receiver thread finished for instance 1.
- Processor Thread (Inst 1): Incoming queue empty and shutdown. Exiting.
- SVM Processor thread finished for instance 1.
- Listener (SVM 1): Receiver thread joined.
- Listener (SVM 1): Processor thread joined.
- Listener (SVM 1): Worker threads finished. Cleaning up instance...
- Ethernet: Closing handle 6
- Thread-safe QueuedMessage queue destroyed
- Listener (SVM 1): Instance deactivated. Ready for new connection.
- Listener (SVM 1): Waiting for connection on port 8081...
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (Inst 2): Connection closed by UVM. Stopping instance.
- Receiver Thread (Inst 2): Marked instance as inactive.
- Receiver Thread (Inst 2): Shutting down incoming queue.
- Thread-safe QueuedMessage queue shutdown initiated.
- SVM Receiver thread finished for instance 2.
- Processor Thread (Inst 2): Incoming queue empty and shutdown. Exiting.
- SVM Processor thread finished for instance 2.
- Listener (SVM 2): Receiver thread joined.
- Listener (SVM 2): Processor thread joined.
- Listener (SVM 2): Worker threads finished. Cleaning up instance...
- Ethernet: Closing handle 8
- Thread-safe QueuedMessage queue destroyed
- Listener (SVM 2): Instance deactivated. Ready for new connection.
- Listener (SVM 2): Waiting for connection on port 8082...
- receive_protocol_message: Соединение закрыто при чтении заголовка.
- Receiver Thread (Inst 3): Connection closed by UVM. Stopping instance.
- Receiver Thread (Inst 3): Marked instance as inactive.
- Receiver Thread (Inst 3): Shutting down incoming queue.
- Thread-safe QueuedMessage queue shutdown initiated.
- SVM Receiver thread finished for instance 3.
- Listener (SVM 3): Receiver thread joined.
- Processor Thread (Inst 3): Incoming queue empty and shutdown. Exiting.
- SVM Processor thread finished for instance 3.
- Listener (SVM 3): Processor thread joined.
- Listener (SVM 3): Worker threads finished. Cleaning up instance...
- Ethernet: Closing handle 10
- Thread-safe QueuedMessage queue destroyed
- Listener (SVM 3): Instance deactivated. Ready for new connection.
- Listener (SVM 3): Waiting for connection on port 8083...
Advertisement
Add Comment
Please, Sign In to add comment