OK while working on this problem... and at a point when I was doing nothing... The computer audio started being received by the Mumble server. Out of the Blue... Android still acting like it is sendin

#audio #ft-991a #mumble #rigpi #rss

Mumble Server not receiving audio from any device. Sending but not receiving. Reloaded Rigpi server and still mumble receives no audio. All devices connected receive audio from RigPi mumble server but

#audio #ft-991a #mumble #rigpi #rss

I have done extensive work with the C O N Cast equipment and if you are trying to do custom work on the router that is using the XFi app, you might as well forget it. They have dumbed down their equip

Sent from Samsung Galaxy smartphone.

#mumble #ft-991a #audio #rss

RigPi allows mumble users to connect but no longer hears user audio. Audio is being sent to the RigPi Mumble Server and they show as being connected but when the red lips are active on remote phones o

#ft-991a #rigpi #audio #rss #mumble

All I can say is my entire repeater associates and that is about 250 of them were privileged to hear the saga of setting up the RigPi over the air for about 4 weeks as I and the person I initially set

OK now that the damage is done... It is time to come up with Macros to fill the empty spaces again: These are some of my Macros for the Yaesu FT-991A Label - Macros PWR ON - *PS1; PWR OFF - *PS0; MIC

#lost #corrupt #error #macros #erased

WARNING ! Don't Paste any symbol into the "Label" Field when editing Macros such as "Square Root" Symbol All your Macro work will be erased. I spent hours figuring out custom macros and before I had s

#lost #corrupt #error #macros #erased

One thing I have noticed. If you get the RigPi working with a particular radio and then try getting another radio working on RigPi, The software seems to get derailed on the first radio. I am only spe

#ft-991a

Did you set the FT-991 mic to the rear connection and not the front? The radio needs to have the rear mic instead of the front to work with mumble and Rigpi

#ft-991a

I think I got them to quit running to the same server. With the documentation, I renamed one Rigpi to a different server name and also renamed the mumble server but for some reason I can't get the ren

#rigpi

I don't know if this suggestion might be of any use but I found a ticking noise on my rig and tried tracking it down until I found that the wireless router was in proximity enough that it was bleeding

Hmmmmm . Here I go again answering my own question... Maybe?... I will go over this info and try and absorb the concepts. I think Mumble Server Renaming is in the article. I hope renaming it will fix

#rigpi

2 RigPis on the same net - Router is forwarding different ports and IPs to each - 2nd rig is trying to logon to 1 rigs mumble on and off. Manually have to disconnect and reconnect to itself on the sec

#rigpi

Adding the Hex commands as macros renders the desired action except that the RigPi Report flashes on the screen each time a macro is sent. Here is the basic warning which I have no idea what it means:

Thanks Bruce. I took a look and sure enough. I hope I catch on to how all this hex works. I think I will change the radio ID and then send it a command from the 7300 and see what happens. Otherwise it

OK sorry for thinking aloud as I am not near the radio to test yet... Looking at this url: https://www.maniaradio.it/dati/IC7000BKT.pdf I see a clue and hope this is the right silver bullet to modify

Possibly just need the Radio model HEX identifier to insert into the sting and then test each command for any signs of life in the radio... So I guess the question would be... Does anyone know where I

These are all Hex so I am guessing that it may be possible to get these to work with the IC-7000? In the HEX is there anything that is known that should be changed to become specific to the IC-7000? F

Let me answer my own question as it stands so far... Use a USB to 1/8 in mono jack into the radio and the other end to the Rigpi. The audio will not work on the USB as the radio does not have an inter