Release DVPi Version 0.88 - Dual Mode, D-Star, Function Key 2
DVPi uses the USRP Client protocol.
When you install and use DVSwitch, you must read and comply with the license that appears.
Version 0.88 is a test version. If you want a stable version, please wait for Version 1.0.
1.How to install
Please check the previous installation documentation for detailed installation instructions. This post only describes what was added in Version 0.88.
2. What was added in Version 0.88
2.1 D-Star protocol
You can use D-Star only by checking whether to 'Enable D-Star' in DVPi Manager.
If you are already using D-Star, you will not be able to use it on two at the same time. If you want to use D-Star in DVPi, you need to log off in another device. If anyone has solved this problem, please tell me.
2.2 Dual Mode
You can use two VFOs in the same way as a conventional VHF/UHF transceiver.
You can use two DVSwitch servers or DVLink. Or, if you operate DVPi as Standalone, you can create session 2 by copying the existing installed DVSwitch in DVPi.
If you are using DVPi stand alone, just run the setdvs2.sh command to copy the DVSwitch installed in DVPi and add a new session.
Unique ID values must be entered differently from existing values.
Session 1 Unique ID is 51
Sesssion 2 Unique ID is 58
In order to distinguish Hotspot in DMR network, you must use different Unique ID.
Select Dual VFO in DVPi Manager.
It will operate in Dual Mode as shown below.
Important Point: If you use DVPi stand alone, D-Star only works on VFO A.
The video below shows how to create Session 2 by copying the DVSwitch installed in DVPi and operate DVPi as Dual Mode.
2.3 Function Switch 2
Function Switch2 can be used as Mode change or VFO change according to your selection.
Example of using Function Switch2 as a mode change switch
The host.brandmeister.network server is not serviced, and the entire Talkgroup status can no longer be retrieved. So, the underline of DVPi's Talkgroup Button is disabled.
I'm trying to restore that functionality in Version 0.9. If we connect to brandmester.network directly, it will generate quite a lot of traffic. This is a problem for us as well, but it could also cause problems on the brandmeister.network server.
So I am thinking of building a separate server to minimize traffic.
Until version 1.0, we plan to stabilize without adding features.
Thank you for using and testing.
We are always grateful to the DVSwitch team for implementing most of the features.