VP8000 Armada on M4 MacBook Air running ARM Windows 11 Virtual Machine

[Radioman_911]

Running Armada software on an M4 MacBook Air.... software runs fine, but the radio WILL not connect to the machine. I received an ARM driver from EFJ, but even after following their directions, I still cannot get it to work with the USBLAN. Just wondering if anyone has been able to successfully get this to function (on a Mac running Windows 11 ARM based processor)

Edit: I currently have to use an old Surface Pro to program this radio. All other Motorola, Kenwood, and other radios work fine! This is becoming the death of me! I may just move forward w/ OTIP feature, but hoping to make the cable method work!

 

[kd4efm]

KPG and Armada programs were not designed for the ARM procesors.

 

[Radioman_911]

KPG and Armada programs were not designed for the ARM procesors.

Local dealer got a ARM driver from EFJ….
Software for multiple KPG programs and Armada itself run completely fine on the ARM machine.

There are ARM drivers for all of my other radios (several kenwoods including NX series) that work just fine as well. Just struggling with this current Vp8000 USBLAN driver. I have a buddy who is much better with computers remoting into my machine later on to take a look. Hoping we can get this to work (especially with this driver direct from EFJ) prior to buying OTIP.

 

[otobmark]

I have a M4 running Parallels Win11arm VM which like yours runs ARMADA but not perfectly in that the drop down boxes are often not scaled correctly (especially Scan List drop downs). I have the same driver issue as you and do hope EFJ arm drivers will fix the connectivity issues for Viking and Kenwood radios (and most other radios such as Motorola). My work around for my VP8000 is to use wifi programming which works as intended. For it to work both computer and radio must be on the same wifi network (can use phone hotspot) and make sure VPN is turned off on computer. Once set up wifi programming is much easier and cleaner than using a cable. My NX series radios do not have wifi programming so for now I cannot shoot those radios with my M4. I still write codeplugs on my M4 and save to Dropbox or Sync which allows me to open them on one of my intel machines (Mac VM or PC) to actually shoot the radio. Once you start using wifi programming you will never want to use the cable again.

 

[Radioman_911]

I have a M4 running Parallels Win11arm VM which like yours runs ARMADA but not perfectly in that the drop down boxes are often not scaled correctly (especially Scan List drop downs). I have the same driver issue as you and do hope EFJ arm drivers will fix the connectivity issues for Viking and Kenwood radios (and most other radios such as Motorola). My work around for my VP8000 is to use wifi programming which works as intended. For it to work both computer and radio must be on the same wifi network (can use phone hotspot) and make sure VPN is turned off on computer. Once set up wifi programming is much easier and cleaner than using a cable. My NX series radios do not have wifi programming so for now I cannot shoot those radios with my M4. I still write codeplugs on my M4 and save to Dropbox or Sync which allows me to open them on one of my intel machines (Mac VM or PC) to actually shoot the radio. Once you start using wifi programming you will never want to use the cable again.

Hmmm. I haven’t ran into the scaling problem yet on armada.

And that sucks about the NX series. Have you tried a different cable? I’ve been programming NX series radios with KPG111 and D1N for a while now via the ARM windows 11 VM.

My buddy wrote up a short document about the struggles we’re still seeing with the recent EFJ ARM driver. Sending it to EFJ support to see what they say.