Commit Graph

15 Commits (f560c112e78fc1c5d83e9bdfa819152c4a48c0bd)

Author SHA1 Message Date
DJ2LS 80aa0a3614 enable CWID and fidx connected message 2025-02-23 18:38:13 +01:00
DJ2LS 5ef21ed6fa first working data transmission - exept one bug: 2025-02-22 19:26:55 [info ] [P2PConnection][id=198][state=States.CONNECTED][ISS=False]: Error preparing data for socket: a bytes-like object is required, not 'str' 2025-02-22 19:28:44 +01:00
DJ2LS d8ec3f3438 radio manager now sending PTT ON OFF - next step: fixing instance of socket interface manager for data. 2025-02-22 14:28:56 +01:00
DJ2LS 351e5f8408 test related work in progress - still improving automated testing. Whats working for now is catching command socket for IRS and ISS. Pushing data on ISS side to data socket is working as well. But we are still trying to get data on IRS. 2025-02-12 10:38:38 +01:00
DJ2LS c919df71c7 adjustments to command handling 2025-02-11 08:41:01 +01:00
modernham ac0d756751 Added same code for DataSocket class as the CommandSocket class to make sure the handlers are accessible.
Started work on getting the client to accept several callsigns as connection methods, and passing the correct connecting one to the receiving client.

For now, storing some variables that need used later within the SocketInterfaceHandler.
2025-01-25 23:20:57 -05:00
modernham 4065f8df20 Returned SocketInterfaceHandler(self) to service_manager creation call as the reference to socket_interface_manager. Not sure if intention, but nothing was returned prior on line 69 of service_manager.py
Started work to store some info we will receive from CMD client. Not sure where to store this data yet. We will need to make an array of several callsigns the client will listen for, and add an exception for them within the "is_frame_for_me" method in frame_handler.py.

Before, all instances of socket_interface_manager were None within the actual command handlers, and it's created P2PSessions, as nothing was passed for it. When I passed the SocketInterfaceHandler to the CommandSocket as the socket_interface_manager, it was still invalid to use within P2PSessions because it was referencing self.socket_interface_manager.command_server as a CustomThreadedTCPServer, and not a CommandSocket type, so the command_handler was an invalid reference.
Adding the hasattr seems to make sure the command_handler is accessible. Not very sure about this solution, but I can now access the command_handler methods from within each session using self.socket_interface_manager.command_server.command_handler.

When connecting to another station using a "CONNECT" command in the command socket, the other station will not reply to the P2P_CONNECTION_CONNECT packet unless lines 221/222 are present within the connected_irs method. Not sure if this is intentional, or if this was only partially complete due to a move to use an ARQ connection. For now the connection command still calls P2PConnectionCommand, so need to find out when ARQ comes into play.
2025-01-24 19:00:42 -05:00
DJ2LS 93b4e74dd9 adjustments to handling socket interface instance 2025-01-22 09:12:19 +01:00
modernham af2aef8aad Socket IP within the config.ini file is now used instead of localhost.
Removed trailing '\n' for command socket interface as most clients only expect the \r.
2025-01-21 22:14:27 -05:00
DJ2LS 2c7c7edf1d fixed socket responses 2025-01-21 13:48:57 +01:00
DJ2LS cb105afb6f some small work on socket interface 2024-06-04 15:12:26 +02:00
DJ2LS c9685e3ee1 timeout for thread.join 2024-05-20 18:42:11 +02:00
DJ2LS 84fc2da619 more shutdown debugging 2024-05-19 10:54:16 +02:00
DJ2LS acb5b03d51 more clean server shutdown 2024-04-21 13:24:04 +02:00
DJ2LS d5097b8b94 another folder renaming 2024-04-18 11:04:25 +02:00