DVSwitch is a set of tools and programs related to provisioning and operating Amateur Radio digital voice networks.
Purpose
The purpose of DVSwitch is as follows:
1) Allows “local” networking during an outage of the regional national/international network server. 2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides. 3) Allows local segregation of localized traffic with more flexibility. 4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
Our stated position is:
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks. WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY) WHEREAS47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
I am going to make some changes to the DVSwitch repositories on Wednesday, to better align naming and distributions. One of the questions I have been getting is why jessie and not stretch. My thoughts
I am going to make some changes to the DVSwitch repositories on Wednesday, to better align naming and distributions. One of the questions I have been getting is why jessie and not stretch. My thoughts
Some of you may already know that DMR-MARC is no longer registering users or repeaters. They have also take down their .csv files with subscribers and repeaters. This breaks some of the update scripts
Some of you may already know that DMR-MARC is no longer registering users or repeaters. They have also take down their .csv files with subscribers and repeaters. This breaks some of the update scripts
Steve,
Just a quick follow up, I setup a new ASL node today using Raspbian Stretch image & have a new bridge up & going over to DMR. It’s working great! Setup was straight forward. Now I
Steve,
Just a quick follow up, I setup a new ASL node today using Raspbian Stretch image & have a new bridge up & going over to DMR. It’s working great! Setup was straight forward. Now I
Ed,
try this:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
cat /sys/bus/usb-serial/devices/ttyUSB1/latency_timer
What value do you get?
Then:
echo 1 >
Ed,
try this:
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
cat /sys/bus/usb-serial/devices/ttyUSB1/latency_timer
What value do you get?
Then:
echo 1 >
The SD card in my ASL->DMR Bridge went belly up so just redid everything on new card using the latest ASL Stretch image on RPi 2 with DV3000 (do not use cheap SD cards and make config backups -
The SD card in my ASL->DMR Bridge went belly up so just redid everything on new card using the latest ASL Stretch image on RPi 2 with DV3000 (do not use cheap SD cards and make config backups -
Steve,
Thank you Steve and all the team who participate
(Humor) you just ruined my vacation, I have to wait to go home to be able to test, implement etc;-)
Steve,
Thank you Steve and all the team who participate
(Humor) you just ruined my vacation, I have to wait to go home to be able to test, implement etc;-)
it is normally started as a service to listen on port 2470. You can stop the service with systemctl stop md380-emu.
Then cd /opt/md380-emu
./md380-emi -h will show you the options other
it is normally started as a service to listen on port 2470. You can stop the service with systemctl stop md380-emu.
Then cd /opt/md380-emu
./md380-emi -h will show you the options other