g4klx/DMRGateway
1
0
Fork 0
mirror of https://github.com/g4klx/DMRGateway.git synced 2026-01-02 22:49:59 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
381 commits 10 branches 0 tags 1.6 MiB
Commit graph

6 commits

Author SHA1 Message Date
Jonathan Naylor 04146faa81 Convert to use of MQTT for command, APRS, and dynamic TG control. 2023-07-07 11:14:34 +01:00
Daniel Caujolle-Bert 0e72349913 Add a way to disable the RemoteCommand logging (annoying when RemoteCommand is heavily used). 2022-01-24 14:20:58 +00:00
Daniel Caujolle-Bert 6c36e29f88 Add new remote command: 
- hosts: display connected hosts, or NONE if disconnected (surrounded with double quotes).
 2022-01-21 08:13:24 +00:00
Daniel Caujolle-Bert d9a09a9364
Fix network ports datatype (unsigned int -> unsigned short). UDPSocket: fix old bug using m_port instead of m_port[x]. 2021-04-25 07:44:55 +02:00
Jonathan Naylor 68b81086a4 Add VS2019 support. 2021-03-22 22:18:59 +00:00
Daniel Caujolle-Bert 41a49d5785 Implement remote command support. 
- Defaut port is 7643 (totally arbitrary)

- Using RemoteCommandDMRG, each network can be enabled or disabled (net1 .. net5, xlx):
    ~ $ RemoteCommandDMRG 7643 disable net2
    M: 2021-03-20 11:48:40.494 Command sent: "disable net2" to port: 7643
    M: 2021-03-20 11:48:40.545 OK

- Using RemoteCommandDMRG, a connection status can be retrieved:
    ~ $ RemoteCommandDMRG 7643 status
    M: 2021-03-20 11:49:13.513 Command sent: "status" to port: 7643
    M: 2021-03-20 11:49:13.563 xlx:conn net1:conn net2:n/a net3:n/a net4:conn net5:n/a

A returned string is expected from the socket connection, this is why I did not reuse the MMDVMHost's RemoteCommand (unless MMDVMHost RemoteControl is modified as well).

The exit value can be used in scripting (also 1 if we didn't get any reply).
 2021-03-20 13:03:19 +01:00