billwil

I have a KG1000-G and run it on a 30A continuous power supply. At 50 watts, I've never really seen it use more than 10 Watts when transmitting. It might go to 11 when I'm not looking just for that little extra (extra credit for the reference). Anyway, a 30A power supply should handle two 50 W radios, especially if you're not transmitting on both at the same time...which shouldn't happen very often if ever. But if you want to be sure, and plan on using both radios at the same time for transmitting, you could go a little higher on the continuous rating just to be sure.

I have this exact problem on my KG-1000G. My buddy who I talk with a lot on it says it happens all the time. I recently ordered another KG-1000G for a vehicle and will swap them out to see if there is any difference. My buddy also has one that was bought around the same time as my first one, and his doesn't seem to do it except at the very beginning of a TX. Mine does it then, but then will randomly do it again during the TX. Just another datapoint.

Thanks for the response @MichaelLAX. I'm a little lost, then. Where did you download the RAR? When I go to the Radioddity support download page here: Radioddity Download and find the DB25-G near the bottom, it's a zip file. Or did you download that some time ago? Maybe a different site? If you still have the RAR (or the extracted contents of the RAR), is it an install package or a simple executable for the app? Will be difficult to tell without running it as they most likely will both be .exe files...but if you know, would be another data point. Thanks.

Was it an actual install or did you just unzip the executable and run it? I was pleading with them to replace that download with an actual install package instead of the app executable...so thinking maybe they did. I will check later if you don't recall. One more question...do you have other installs from Radioddity on that Wine instance? Wondering if the OCX libraries might have already been registered from other installs. Thanks.

Now that you got the software working for the db25, have you noticed that anything you program in to it above channel 30 (at least for repeaters) doesn't actually allow you to transmit? I've been working with Radioddity support on this issue and no total confirmation yet (description suggests it should work as expected but it doesn't for me). I would be interested in your experiences on that. That said, the issue with the unregistered ActiveX controls appears to stem from the fact that there is no installer for the software. They are just zipping up an executable that is the software itself. At least some of the other radioddity software has installers, so I'm guessing you could figure out what other similar software they provide would register these controls correctness and install that first before trying to run the db25 exe. For example, the db20 software is installed as one would expect. I haven't tested it yet, but installing that before trying to run the exe might work. In my case I tried it on 3 windows 10 machines and a windows 11 machine and had the same problem on all; I had to manually register the control files to get it to work also. Be careful where you get these old 32 bit control files as there is a lot of malware out there posing as legitimate controls or dlls that people download and register themselves doing half the crackers' work for them. I've reported all of this in detail to Radioddity. I might have to return the db25 if the below channel 31 to TX bug is replicatable and not easily fixed as that renders it less useful for some of my use cases. I might try the db20 to see if it has the same issue (I doubt it does). Good luck with your radios. Sent from my SM-G998U1 using Tapatalk

Another quick tip that we discovered today on the KG1000G. Once you program a tone (in the radio or via software), don't check it unless you know if it's digital or not. I noticed that I was losing tone settings on some repeater channels and we finally figured out why; if you use the menu on the radio to check for a DCS tone and you had a CTCSS tone in there, just the act of checking that DCS is "off" will clear your CTCSS setting (and vice-versa). This was frustrating and confusing until figured out. Moral of the story, set it in software and then don't check it...trust the process.