Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- dtorkin@ubuntu1:~/Desktop/practice$ nc localhost 12346
- EVENT;SVM_ID:0;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x08,ProtocolStage=1
- EVENT;SVM_ID:1;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x09,ProtocolStage=1
- SENT;SVM_ID:0;Type:128;Num:0;LAK:0x08
- SENT;SVM_ID:1;Type:128;Num:0;LAK:0x09
- SENT;SVM_ID:3;Type:128;Num:0;LAK:0x0B
- RECV;SVM_ID:0;Type:129;Num:0;LAK:0x01;BCB:0x6F000000;Details:LAK_ret=0x08;SLP=0x3;VDR=16;BOP1=17;BOP2=18
- EVENT;SVM_ID:0;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x08,ProtocolStage=3
- RECV;SVM_ID:3;Type:254;Num:0;LAK:0x01;BCB:0x6F000000;Details:UnexpectedWarning;TKS=3
- EVENT;SVM_ID:3;Type:Warning;Details:TKS=3
- EVENT;SVM_ID:3;Type:LinkStatus;Details:NewStatus=5,AssignedLAK=0x0B,ProtocolStage=2
- RECV;SVM_ID:1;Type:129;Num:0;LAK:0x01;BCB:0x6F000000;Details:LAK_ret=0x09;SLP=0x3;VDR=16;BOP1=17;BOP2=18
- EVENT;SVM_ID:1;Type:LinkStatus;Details:NewStatus=2,AssignedLAK=0x09,ProtocolStage=3
- dtorkin@ubuntu1:~/Desktop/practice$ sudo ./uvm_app --wait-for-gui OR
- [sudo] пароль для dtorkin:
- UVM: Option --wait-for-gui enabled. UVM will wait for GUI client connection before proceeding with SVM operations.
- UVM: Effective RadarMode selected: OP
- UVM: Загрузка конфигурации из 'config.ini'...
- Configuration parsed successfully from 'config.ini'.
- --- UVM Effective Configuration ---
- Interface Type: ethernet
- SVM Response Timeout: 6.00 seconds
- SVM Keep-Alive Timeout: 18.00 seconds
- GUI Listen Port: 12346
- Main Loop Idle Sleep: 60000 us
- Target IP for SVMs (UVM connects to): 192.168.189.129
- Number of SVMs with explicit config in INI: 3
- SVM Slot 0 Configuration (Explicitly loaded: Yes):
- Connect Port: 8080
- Assigned LAK: 0x08
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 1 Configuration (Explicitly loaded: Yes):
- Connect Port: 8081
- Assigned LAK: 0x09
- Simulate Control Failure: Yes
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 2)
- SVM Slot 2 Configuration (Explicitly loaded: No):
- Connect Port: 8082
- Assigned LAK: 0x0A
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 3 Configuration (Explicitly loaded: Yes):
- Connect Port: 8083
- Assigned LAK: 0x0B
- Simulate Control Failure: No
- Disconnect After Messages: 3
- Simulate Response Timeout: No
- Send Warning on Confirm: Yes (TKS: 3)
- ----------------------------------
- UVM: Найдено 3 конфигураций SVM в файле.
- Thread-safe UVM request queue created with capacity 150
- Thread-safe UVM Response queue created with capacity 150
- UVM: Подключение к сконфигурированным SVM...
- UVM: Попытка подключения к SVM ID 0 (IP: 192.168.189.129, Порт: 8080, Ожидаемый LAK: 0x08)...
- Ethernet: Connected to 192.168.189.129:8080 (handle: 3)
- UVM: Успешное подключение к SVM ID 0 (Дескриптор: 3).
- UVM: Попытка подключения к SVM ID 1 (IP: 192.168.189.129, Порт: 8081, Ожидаемый LAK: 0x09)...
- Ethernet: Connected to 192.168.189.129:8081 (handle: 4)
- UVM: Успешное подключение к SVM ID 1 (Дескриптор: 4).
- UVM: Попытка подключения к SVM ID 3 (IP: 192.168.189.129, Порт: 8083, Ожидаемый LAK: 0x0B)...
- Ethernet: Connected to 192.168.189.129:8083 (handle: 5)
- UVM: Успешное подключение к SVM ID 3 (Дескриптор: 5).
- UVM: Подключено к 3 из 3 (найденных в конфиге) SVM.
- UVM: Запуск рабочих потоков (Sender, Receivers, GUI Server)...
- UVM: Ожидание подключения GUI клиента к порту 12346 (или Ctrl+C для выхода)...
- UVM Sender thread started.
- UVM Receiver thread started for SVM ID 0 (handle: 3).
- UVM Receiver thread started for SVM ID 1 (handle: 4).
- UVM Receiver thread started for SVM ID 3 (handle: 5).
- GUI Server: Starting listener on port 12346
- GUI Server: Waiting for GUI connection on port 12346...
- GUI Server: Accepted connection from 127.0.0.1:60360 (FD 7)
- GUI Server: Sending initial state to new GUI client (FD 7).
- GUI Server: Initial state sent to GUI client (FD 7).
- UVM: GUI клиент подключен. Продолжение операций с SVM.
- UVM: Начало основного цикла работы. Выбранный режим РЛС: OP
- UVM: SVM 0 (LAK 0x08), Этап: Отправка 'Инициализация канала' (Сообщение #0)...
- UVM: SVM 1 (LAK 0x09), Этап: Отправка 'Инициализация канала' (Сообщение #0)...
- UVM: SVM 3 (LAK 0x0B), Этап: Отправка 'Инициализация канала' (Сообщение #0)...
- Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=3
- Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=4
- Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=5
- Получено сообщение через Ethernet: Тип=129, Номер=0, Длина тела=12, Handle=3
- Получено сообщение через Ethernet: Тип=254, Номер=0, Длина тела=12, Handle=5
- Получено сообщение через Ethernet: Тип=129, Номер=0, Длина тела=12, Handle=4
- UVM: SVM 0 (LAK 0x08), Получен ОЖИДАЕМЫЙ ответ: Подтверждение инициализации (129) (наш запрос #0)
- UVM: SVM 3 (LAK 0x0B) - Получен НЕОЖИДАЕМЫЙ тип ответа Предупреждение (254) (Сообщение #0), когда ожидался тип Подтверждение инициализации (129) (на наш запрос #0).
- UVM: SVM 1 (LAK 0x09), Получен ОЖИДАЕМЫЙ ответ: Подтверждение инициализации (129) (наш запрос #0)
- 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'.
- --- UVM Effective Configuration ---
- Interface Type: ethernet
- SVM Response Timeout: 6.00 seconds
- SVM Keep-Alive Timeout: 18.00 seconds
- GUI Listen Port: 12346
- Main Loop Idle Sleep: 60000 us
- Target IP for SVMs (UVM connects to): 192.168.189.129
- Number of SVMs with explicit config in INI: 3
- SVM Slot 0 Configuration (Explicitly loaded: Yes):
- Connect Port: 8080
- Assigned LAK: 0x08
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 1 Configuration (Explicitly loaded: Yes):
- Connect Port: 8081
- Assigned LAK: 0x09
- Simulate Control Failure: Yes
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 2)
- SVM Slot 2 Configuration (Explicitly loaded: No):
- Connect Port: 8082
- Assigned LAK: 0x0A
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 3 Configuration (Explicitly loaded: Yes):
- Connect Port: 8083
- Assigned LAK: 0x0B
- Simulate Control Failure: No
- Disconnect After Messages: 3
- Simulate Response Timeout: No
- Send Warning on Confirm: Yes (TKS: 3)
- ----------------------------------
- SVM: Will attempt to start 3 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=2
- DEBUG SVM MAIN - Instance 2 Settings: LAK=0x0A, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
- DEBUG SVM MAIN - Instance 3 Settings: LAK=0x0B, simulate_control_failure=0, disconnect_after=3, simulate_timeout=0, send_warning=1, tks=3
- SVM: Loading configuration...
- Configuration parsed successfully from 'config.ini'.
- --- UVM Effective Configuration ---
- Interface Type: ethernet
- SVM Response Timeout: 6.00 seconds
- SVM Keep-Alive Timeout: 18.00 seconds
- GUI Listen Port: 12346
- Main Loop Idle Sleep: 60000 us
- Target IP for SVMs (UVM connects to): 192.168.189.129
- Number of SVMs with explicit config in INI: 3
- SVM Slot 0 Configuration (Explicitly loaded: Yes):
- Connect Port: 8080
- Assigned LAK: 0x08
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 1 Configuration (Explicitly loaded: Yes):
- Connect Port: 8081
- Assigned LAK: 0x09
- Simulate Control Failure: Yes
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 2)
- SVM Slot 2 Configuration (Explicitly loaded: No):
- Connect Port: 8082
- Assigned LAK: 0x0A
- Simulate Control Failure: No
- Disconnect After Messages: -1
- Simulate Response Timeout: No
- Send Warning on Confirm: No (TKS: 1)
- SVM Slot 3 Configuration (Explicitly loaded: Yes):
- Connect Port: 8083
- Assigned LAK: 0x0B
- Simulate Control Failure: No
- Disconnect After Messages: 3
- Simulate Response Timeout: No
- Send Warning on Confirm: Yes (TKS: 3)
- ----------------------------------
- SVM: Will attempt to start 3 instances based on config.
- Thread-safe QueuedMessage queue created with capacity 300
- SVM: Listener thread 0 initiated for Port 8080 (LAK 0x08).
- SVM: Listener thread 1 initiated for Port 8081 (LAK 0x09).
- SVM: Listener thread 3 initiated for Port 8083 (LAK 0x0B).
- SVM: Starting common threads (Timer, Sender)...
- SVM: All common threads started. 3 listeners active. Running...
- SVM Main: Waiting for shutdown signal...
- SVM Sender thread started (reads global outgoing queue).
- SVM Timer thread started.
- Ethernet: Listening on port 8081 (handle: 3)
- Listener thread started for SVM ID 1 (LAK 0x09, Port 8081, Listen FD 3)
- Listener (SVM 1): Waiting for connection on port 8081...
- Ethernet: Listening on port 8083 (handle: 5)
- Listener thread started for SVM ID 3 (LAK 0x0B, Port 8083, Listen FD 5)
- Listener (SVM 3): Waiting for connection on port 8083...
- Ethernet: Listening on port 8080 (handle: 7)
- Listener thread started for SVM ID 0 (LAK 0x08, Port 8080, Listen FD 7)
- Listener (SVM 0): Waiting for connection on port 8080...
- Listener (SVM 0): Accepted connection from 192.168.189.128:43844 (Client FD 8)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 0): Instance activated. Worker threads started.
- SVM Receiver thread started for instance 0 (handle: 8).
- SVM Processor thread started for instance 0.
- Listener (SVM 1): Accepted connection from 192.168.189.128:52608 (Client FD 4)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 1): Instance activated. Worker threads started.
- SVM Receiver thread started for instance 1 (handle: 4).
- SVM Processor thread started for instance 1.
- Listener (SVM 3): Accepted connection from 192.168.189.128:58652 (Client FD 6)
- Thread-safe QueuedMessage queue created with capacity 100
- Listener (SVM 3): Instance activated. Worker threads started.
- SVM Processor thread started for instance 3.
- SVM Receiver thread started for instance 3 (handle: 6).
- Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=8
- Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=6
- Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=4
- Processor (Inst 0): Обработка 'Инициализация канала'
- Параметры: LAUVM=0x1, LAK=0x08 (assigned)
- SVM (Inst 0): Эмуляция выключения лазера...
- Processor (Inst 3): Обработка 'Инициализация канала'
- Параметры: LAUVM=0x1, LAK=0x0B (assigned)
- SVM (Inst 3, LAK 0x0B): SIMULATING warning instead of confirm init (TKS=3).
- Processor (Inst 1): Обработка 'Инициализация канала'
- Параметры: LAUVM=0x1, LAK=0x09 (assigned)
- Ответ 'Подтверждение инициализации' сформирован (LAK=0x08).
- SVM (Inst 1): Эмуляция выключения лазера...
- Ответ 'Подтверждение инициализации' сформирован (LAK=0x09).
- Отправка сообщения через Ethernet: Тип=129, Номер=0, Длина тела=12, Общий размер=18, Handle=8
- Отправка сообщения через Ethernet: Тип=129, Номер=0, Длина тела=12, Общий размер=18, Handle=4
- Отправка сообщения через Ethernet: Тип=254, Номер=0, Длина тела=12, Общий размер=18, Handle=6
Advertisement
Add Comment
Please, Sign In to add comment