The app uses the configuration file pyUC.ini

First 2 way QSO (Thanks Ken!!!!!)

Looking at your logs, I see that the station transmitting with dmr2ysf is placing the users DMR ID in the callsign field. I would bet that their dmr id database is not up to date so it is just sending

#mmdvm_bridge

Try different audio codecs in the mobile app.

Use pushFile, I was looking at the function name not the command name.

Do not use fromDMRPort and toDMRPort. I asked you to use TXPort and RXPort in AB. You should have gotten a nasty message in your AB log file, did you see it? Also, just to make sure, what version of A

Also note that this will not cross connect the XLX servers with each other. That is possible by using the same technique on the dvswitch.ini [DMR] TXPorts. However I would take it one step at a time.

I will start by saying I know nothing about the limitation you are running into with XLX (or even if it can be configured to do what you want). With that being said, let's assume you DO want multiple

A transcoder should NEVER receive a tune command. Use static TG info in your gateway and BM. If you MUST have the DMR or P25 side tuneable, then the TLV tune should be directed at the MB instances tha

Andrew, By the error you are seeing I have to assume you are running AMBEServer on the same machine as Analog_Bridge is running on. If this is so, you can just run the DV3000 (or other stick) directly

#analog_bridge

And yes you did misunderstand. Nodes in the database (node_list.txt) are preceded by a *2 when invoked from the "Nodes" menu or using the long press for the first 10 Nodes in the "Macro" menu, accesse

Sorry, ment *30 so a string like *22100*30 would dial node 2100 in RX mode then change over to TX. DVSM supplies the *2 so you would not need that in your database.

Hmmm, I have not look at that code in a while. Yes, I did make the decision to use monitor rather than transceive. You can just do a *3 at the end of the node number to fix it I guess. The proper solu

I added the gain block after the AGC processing, so this should address your needs. Steve will release soon as there are some other changes in the pipeline as well.

Run it with quem-arm qemu-arm /opt/md380-emu -S 2470 &

I have addressed the issue. We will need to test in-house for a while to make sure it is solid (more changes than a simple listener). Steve will release when it is solid

Make your Modules match. You have “C” and “G”

It appears that the ASL node list moved from its old location in Feb, and I missed it. I have changed the dvswitch.sh script, and when Steve merges the change, it will be available.

That sucks. I will add an export talkgroup in the future so you no longer need to run through dmrgateway just to adjust the destination.

#mmdvm_bridge

Hello Waldek, So, this is a BIG topic which covers several ways you may want to use the DVSwitch components. The multiple transmit ports in general will allow you to have a much richer assortment of n