I want to configure my MB1 to work with my N3FJP logging software. I've searched all through the forum, but I don't find any clear process for this. I've read the MB1 Addendum document and I'm left confused with what needs to happen. It appears to be some combination of VAC, SDC, and/or OmniRig.

Has someone already solved this problem? Could you share a bullet list of your process? I'm willing to purchase the VAC software or whatever it takes, but I need a road map. Many thanks and 73!

Set up ESDR2 and VSPE per the UMA. So far as I can see, with N3FJP the 3rd party apps of SDC and Omnirig are irrelevant.

For transceiver control:



For CW set up


This is with CW in ESDR2 configured as per UMA section 6.14 page 54 com port sending.

Phone set up (i.e. voice macros) is done the same as UMA section 6.17

What else is there that is ESDR2 specific? Nothing that I can see but feel free to post additional questions.

Thank you for your reply. Last night I installed the VSPE software from Eterlogic. They graciously offer for you to try their software before you buy it, so I am running it as "unregistered" at the moment. I've completed all of the setup and settings. I've made sure to start the VSPE application and load the config settings before opening the ESDR2 application. After ESDR2 is running I open N3FJP. Unfortunately, N3FJP is not communicating with ESDR2. N3FJP is trying to poll the MB1 through virtual Com Port 6, but it is not finding it. Perhaps when I Register the Eterlogic software this will fix it? I'll try that tonight.

Here are some screen captures. Unfortunately, I failed to grab the screen capture from N3FJP CW Setup where I set the CW Com Port, but I did do that also.

You have not correctly set up ESDR2. If you refer to the UMA, you will see the actual setting and the methodology. Basically with software defined ports there are two ends, like a pipe, the host end and the client. These have different port numbers to differentiate them. You have correctly defined them in VSPE. In ESDR2 in the CAT tab, the CAT data should start on COM 5 and not COM 6. After making that change you should find that with your existing settings in the Rig Interface Setup that the logging software will connect. I would imagine correcting the setting in ESDR2 will also correct the failure with CW.

You will at some point likely need to also follow through with the whole UMA instruction by, in the ESDR2 CAT tab, enabling PTT on COM 9 with DTR and RTS checked. If you do this now, when you come to save your ESDR2 Profile, nothing will be lost should there be a need to recover that Profile following any Windows 10 problem or error with the ESDR2 options file.

You also have data stop bits incorrectly setup as well

I would suggest you set both radio and the software to 1 , you currently have radio using 1 stop bit and N3FJP using 2 that along with the incorrect setup of the comports as Erik mentioned will never connect

Thank you kindly for those tips guys. These setting changes fixed my issue. My N3FJP software is virtually connected to my MB1 and it's working great!

With VSPE the Stop Bit setting at the client end is irrelevant.