Welcome to DVSwitch
Purpose
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
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)
WHEREAS 47 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.
Re: Hoping these config files look ok
Steven Blackford
Yep, it successfully logged in & is sending the RTTPPING & MSTPONG's messages. I ran the command as /usr/bin/python /opt/hblink/HB_Bridge.py as root. I even did a reset on the IP via the selfcare page & I watched it log back in successfully. I have Telegram up & running if that'd be easier. Thanks again. Steve
On Mon, Sep 25, 2017 at 10:52 AM, Steve N4IRS <szingman@...> wrote:
--
|
|
Re: Hoping these config files look ok
You are running HB_Bridge.py? "python HB_Bridge.py" in the
foreground. Are you seeing any traffic in either direction at the
console?
toggle quoted messageShow quoted text
On 9/25/2017 10:38 AM, Steven Blackford
wrote:
|
|
Re: Hoping these config files look ok
Steven Blackford
Hi Steve, Yeah, that would help wouldn't it! Ok, I've made the adjustments & HB_Bridge successfully logs into the BM Network. I'm not seeing any response If I key up on TG 31254 though. I don't see any traffic. My "Repeater ID" is my DMR ID. Since I don't have a repeater, I made the adjustments & it's is showing up in my list of hotspots on the BM Selfcare portal. I've assigned 31254 as a static TG on TS 2 which is how I have it setup in the software. Does anything else have to be setup on the BM side? I'm using 3102 as my server in case that helps. The ID I'm using is 3137156. Thanks for helping with all this! 73 de K4SQI! Steve, K4SQI
On Mon, Sep 25, 2017 at 5:41 AM, Steve N4IRS <szingman@...> wrote:
--
|
|
Re: Hoping these config files look ok
Steve,
toggle quoted messageShow quoted text
You have hblink configured as a Master. With what you are trying yo do, you need to be a client to the BM server. See below: 73, Steve N4IRS # MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS # HomeBrew Protocol Master instances go here. # IP may be left blank if there's one interface on your system. # Port should be the port you want this master to listen on. It must be unique # and unused by anything else. # Repeat - if True, the master repeats traffic to clients, False, it does nothing. [MASTER-1] MODE: MASTER ENABLED: False REPEAT: True EXPORT_AMBE: False IP: 127.0.0.1 PORT: 62031 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 # CLIENT INSTANCES - DUPLICATE SECTION FOR MULTIPLE CLIENTS # There are a LOT of errors in the HB Protocol specifications on this one! # MOST of these items are just strings and will be properly dealt with by the program # The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz. # Latitude is an 8-digit unsigned floating point number. # Longitude is a 9-digit signed floating point number. # Height is in meters [REPEATER-1] MODE: CLIENT ENABLED: True EXPORT_AMBE: False IP: PORT: 54001 MASTER_IP: MASTER_PORT: 62031 PASSPHRASE: passw0rd CALLSIGN: K4SQI RADIO_ID: 1234567 <------- Put your repeater ID here. RX_FREQ: 449000000 TX_FREQ: 444000000 TX_POWER: 25 COLORCODE: 1 SLOTS: 3 LATITUDE: 41.7333 LONGITUDE: -50.3999 HEIGHT: 75 LOCATION: Iceberg, USA DESCRIPTION: HBlink repeater URL: https://groups.io/g/DVSwitch SOFTWARE_ID: 20170620 PACKAGE_ID: MMDVM_HBlink GROUP_HANGTIME: 5 OPTIONS:
On 09/25/2017 12:40 AM, Steven
Blackford wrote:
Hello,
|
|
Hoping these config files look ok
Steven Blackford
Hello,
I've been following the group for a while & have been exchanging emails with Steve, N4IRS over the past few days. I'm hoping to create a DMR<->D-Star bridge using Analog_Bridge, Dummy Repeater, HB_Bridge. I have the D-Star side of things configured. ircDDBGateway is running, I have DummyRepeater working & it sees traffic coming from the network. I'm wanting to create this bridge from XRF054A on D-Star over to BM TG 31254. I've attached my initial config files. I was working on things this evening when I got called out to work. Any insight would be appreciated. Thanks & 73 de K4SQI! Steve, K4SQI
|
|
Re: My availability
Peter M0NWI
Batten down the hatches Steve, hope it blows over without too much damage! Sent from Outlook From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: 08 September 2017 13:34:26 To: DVSwitch@groups.io Subject: [DVSwitch] My availability Due to a visit from our aunt Irma, my availability will be somewhat limited for the foreseeable future.
73, Steve N4IRS
|
|
Re: My availability
David KE6UPI
Be safe. Where are you heading to? David -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Fri, Sep 8, 2017 at 12:58 PM, Jean-Marc F1SCA <magnier.jeanmarc@...> wrote: Steve, take good care of yourself and your family.
|
|
Re: My availability
Jean-Marc F1SCA
Steve, take good care of yourself and your family.
Jean-Marc - F1SCA
|
|
Re: My availability
Matthew Pitts N8OHU
Stay safe.
toggle quoted messageShow quoted text
Matthew N8OHU
On September 8, 2017 8:34:26 AM EDT, Steve N4IRS <szingman@...> wrote: Due to a visit from our aunt Irma, my availability will be somewhat limited for the foreseeable future.
|
|
Re: My availability
you and mike and your families stay safe buddy Chuck K0XM
|
|
My availability
Due to a visit from our aunt Irma, my availability will be somewhat limited for the foreseeable future.
73, Steve N4IRS
|
|
Re: DVMega AMBE3000
Matthew 2E0SIP
Thanks for your testing Flo, looks good!
|
|
Re: DVMega AMBE3000
Florian Wolters
Matthev,
I am not into the details but I made a short test for you using a ThumbDV USB dongle. Results in the file attached. vy73 de Florian DF2ET
|
|
Re: DVMega AMBE3000
Matthew 2E0SIP
Hi All, By default it's configured to operate in CODEC mode, so a PKT_RESETSOFTCFG command must be issued to cause it to ignore the hardware pin configuration. I've forked the repo and included my change to AMBEtest4.py here - https://github.com/marrold/Analog_Bridge , please could someone test with a ThumbDV if possible? In theory it only forces UART PACKET mode with DTX disabled, so it shouldn't cause any problems. Cheers all!
|
|
Re: DVMega AMBE3000
On the NWDigital PiDV DTXEN is pulled low. I don't know if I have
the schematic on the DV3000u. I ASSUME it's the same state.
toggle quoted messageShow quoted text
Steve
On 8/28/2017 11:46 AM, Matthew 2E0SIP
wrote:
|
|
Re: DVMega AMBE3000
Matthew 2E0SIP
Cheers Steve, that's very helpful. I will drop Guus a message and see if he has any thoughts. Thanks again Matthew 2E0SIP
|
|
Re: DVMega AMBE3000
On 8/28/2017 8:38 AM, Matthew 2E0SIP
wrote:
Mike pointed this out to me. If you look at the logs you see a constant stream of: 61000801xxxxxxxxxxxxxxxx Where xx is an AMBE byte. 61 = Header 00 08 = 8 bytes of payload 01 = Channel data (AMBE) xxxxxxxxxxxxxxxx = The AMBE data This occurs no matter what the chip is being commanded to do. We expect to send a command followed by a response. Do not understand why we are getting more. Steve ,_._,_
Setting serial port Serial port parameters: Port name: /dev/ttyUSB1 Baudrate: 115200 Byte size: 8 Parity: N Stop bits: 1 Xon Xoff: False RTS/CTS: False DST/DTR: False a Testing Reset DV3000 Errror, DV3000 send back invalid start byte. Expected 0x61 and got 19 Reset DV3000 137461000801013068662d2264786100080101303e024f04432e61000801013028460967647c6100080101301c240e74066c6100080101303e024e37430e6100080101301c246b41176c61000801013078420d26217a6100080101307c062d0544526100080101303e062b21737e6100080101302e242 f61220a6100080101303c204b4242786100080101301e060c07767c6100080101303c260f07206861000801013038642d0646486100080101302a440f23472e6100080101301e202f07636e6100080101302e4628134194610008010130d4a4c56645666100080101306a626812145e6100080101303c 060f35510a6100080101303c242f02576e6100080101307c042d4776606100080101306e042e12742c6100080101302c220d2323686100080101303c206f04316e610008010130e404674776756100080101301e606b71762c61000801013068460c15274a6100080101303e206c12477a61000801013 05e24287555466100080101303e060852132e6100080101304a424d65774c6100080101306c224856477a6100080101307c206f2140726100080101304a460d42156c6100080101305e62285360246100080101304e060f22314e6100080101303e020f2652686100080101300c060b40673e61000801 01300e024f2431d66100080101308e068704646c6100080101307c024e3045786100080101307e060c1753726100080101303c262d3016c061000801013018424f25646c6100080101306c662945714261000801013068402c71556a610008010130b6260874656f6100080101300e006f02733861000 80101307c026b44757c6100080101 Testing Get Product ID Errror, DV3000 send back invalid start byte. Expected 0x61 and got 48 Get Product ID 306c026874256c6100080101306c062d6132426100080101301e262d14602e6100080101308e022635257d6100080101306c042c10544e6100080101303e242a77137861000801013008642d46346e6100080101303c060f20745e61000801013068424f06526a6100080101304c024c30750e6100080 101305e246b0375746100080101307e006d45662c6100080101307c260f01307461000801013068460a76637a610008010130a6260417516f6100080101305c026f04340c610008010130c2406675466f6100080101306c064d0323626100080101302e260d07710e6100080101302e024e12564e6100 080101306e242947663a6100080101304c206f03526461000801013068462f25055a61000801013084204d34566d610008010130b6240520647f6100080101303e242f05700e6100080101302e040f00356a61000801013038642d6604846100080101305c420b6567666100080101304e242941614e6 1000801013048606d20210e6100080101306c26685165766100080101303c042963135e6100080101306e026c07033a6100080101306c042b60775661000801013078626d0603686100080101302c060a76137a610008010130f2460651565f6100080101306c266d2521726100080101303a462a5347 3e6100080101301c602d27004c6100080101306a606d04646a6100080101302c040872727e61000801013068260b41463c6100080101307e024d6534246100080101301c226c10666c6100080101306e242960015a6100080101302c042967654a6100080101307a602f47323e6100080101303c424a7 0575e6100080101306c024f214172 Testing Get Version In test Get Version Error, did not get expected value from DV3000. Got: 0j`l4CJ expected 1V120.E100.XXXX.C106.G514.R009.B0010411.C0020208 01306a606c34434a Testing Set DSTAR Mode In test Set DSTAR Mode Error, did not get expected value from DV3000. Got: 0WFt expected 01304c0608574674 Testing Reset DV3000 In test Reset DV3000 Error, did not get expected value from DV3000. Got: 0|O1. expected 9 01307c024f03312e Testing Set DMR Mode In test Set DMR Mode Error, did not get expected value from DV3000. Got: 0Hb dG^ expected 013048620b64475e Testing Decode AMBE Test result: Success (6100080101302c060a74717e) Error, did not get the right number of PCM bytes back from an encode 8
|
|
Re: DVMega AMBE3000
Matthew 2E0SIP
Hi Steve, Do you have any idea why its a "no go" ? Does the carrier board not expose direct access to the AMBE 3000 chip? Cheers
|
|
Re: DVMega AMBE3000
Nope,
toggle quoted messageShow quoted text
I'm going to have to call this a "no go" Steve
On 8/25/2017 9:46 AM, Matthew 2E0SIP
wrote:
|
|
Re: DVMega AMBE3000
I just had a idea I want to check before we call it a no go.
toggle quoted messageShow quoted text
On 8/25/2017 9:46 AM, Matthew 2E0SIP
wrote:
|
|