Hi all,
Juma_ctrl.exe is good if you work locally in the same pc where the Juma100D serial port is connected to. Juma 1000 is different and has more options and a different software.
If you are using it remotely the nodered solution OR the container solution is the option to go for avoid to add any extra hardware.
In the nodered version you need to install nodered and the modules the Juma dedicated flow needs to use. Then you can contol the ampli via nodered UI windows in your browser.
More info on this in nodered group in
groups.ioI can talk for the container solution i developed with the help of IW7DLE who write the client/server .
This solution allow Thetis to control directly via a custom container the juma100 in the remote site. I thin is less resource consuming and, in the future can led to a automated manual band change via Thetis.
Actually can control any function of the Juma 100 in F-sense mode.
I will explain i.e. the Martin's use case.
On the remote location you have hl2, Juma100 and a pi (or a pc) connected and working.
On the pi you need to install node.js software and related modules, a small routine called server.js and his config file running. Server.js listen via your subnet the data to pass to the Juma serial port.
On your operating location you need to have a pc with Thetis configured and working. You have to add a small client.exe with his conf file to launch via the Thetis automated startup. Also you have to add a new container and import my .dat file and configure MMIO in Thetis.
The client talks with the server in remote location and can translate the serial data received from Juma in a format readable from Thetis and display in his container, at the same time can send the command to change setting in Juma via the container buttons (stby/oper, pwr levels etc.)
I set a github repository that contains all you need.
And because an image worth more than 100 words, i will add a screen capture. In the low right corner you can see the container.
Hope this helps.
'73 Luca EA8DJR