Given my demonstrated ability to connect to local nodes with Vara FM via both the low power Elecraft and my IC-910H (using a RIGblaster), I’ve pushed aside further pursuit of this with the Baofeng for the time being. More generally, I’m inching up on a conclusion that HT’s are just not well suited to this application as it now stands, and I grow increasingly suspicious that HT’s in general may not be suitably robust for emcomm. TX/RX transition) that might render it impossible to connect, given the coding of the current Vara software. Via ongoing investigation I’m sensing there’s possible Baofeng timing issues (e.g. As stated above I’ve confirmed proper configuration on the cable pins.Īlso as stated above, I’ve made all the Baofeng and Win10 config changes found via multiple online sources (squelch=0, AGC=off, etc.) and still no joy. As to cabling, my homebrew cable did not initially include ferrites, but I have since added (2) mix 31 snap-ons, which did not resolve the situation. At this point I’ve definitively eliminated only the antenna from further consideration. Of course the fact that there’s multiple links to this chain (the cabling, the radio, the soundcard and the antenna) complicates the troubleshooting process. Clearly it’s not my antenna, and I consider that there’s a low probability that it’s related to the Digirig, as evidenced by my ability to reliably hit all the local nodes with my Elecraft. Pedro, I haven’t resolved my inability to hit my local nodes with the Baofeng, at least not yet. ![]() So again, it appears this issue is likely not impacted by the Digirig operation, but if anyone has any relevant experience or suggestions on this, I’m all ears. It appears it’s now time to chase down the specifics of how auto-tune functions within Vara. ![]() Specifically, with Baofeng I don’t hear activity between the pulses associated with auto-tune changing the level 1-10, whereas with Elecraft I do sense tones between the pulses. Lacking an O-scope here at home, I can’t say definitively, but to my ear, an auto-tune sounds different for Baofeng transmit as compared to Elecraft. I’ve posted it here simply because it’s on point with the title, and because I then consider it probable that others viewing it will have interest and possibly (hopefully) relevant experience to share. (Mine’s configured for 2m … I’m surprised to the point of finding it bizarre that it can even be configured for 4m!).Īs K0TX is possibly alluding to, since I’m hearing Baofeng1 on Baofeng2, I’m considering it moderately-to-very improbable that this has anything to do with the Digirig. ![]() My KX3 includes Elecraft’s optional 2m-4m transverter option. ![]() Switch to my Elecraft KX3, same antenna, change to Elecraft homebrew cables per Digirig drwg (also verified pin continuity), make Vara PTT adjustments for CAT control, no changes to any Win10 sound props, and auto-tune yields ‘Approved’ (with a strong signal), and Winlink/Vara works as it should.Īnybody have any ideas, anything I’ve overlooked with the Baofeng setup, additional things to try, etc.?Īuto-tune as monitored by another Baofeng for both setups sounds the same … but it works w/Elecraft (which has a measly 3W output) but not with the Baofeng, which has a nominal 8W on high.Įasy part first. Attempts to auto-tune to a local Winlink node (4 mi away) yield “No Signal”. This includes verifying ports & sound devices in dev mgr (Win10), configuring Vara PTT via com (verified correct port) w/PTT pin=RTS, resetting all Baofeng configs with subsequent reset to SQL=0 and TXP(power)=LOW (have also tried HIGH), Digirig playback & recording levels both at 20, playback enhancements disabled and recording AGC unchecked (these last three items in Win10 sound props), adjusting Baofeng volume to yield Vara ‘Audio Input’ meter approx 3/4, and connected via a “homebrew” cable built to the Digirig drwg, proper pin continuity verified. Watched this vid and followed it exactly. Attempting to set up VaraFM 4.2.7 w/Baofeng (UV-5R8W) w/Digirig 1.9.
0 Comments
Leave a Reply. |