Yes, port shunting was one of the first things I did when i first suspected RF and that didn't solve the issues. Thanks for your suggestion a while back. I apologize for not confirming it was already done back months ago when you originally suggested it.

I'm officially claiming victory:). Since I updated to the new firmware to fix the RF on the RX port and also went to CM ASIO Protocol 2 has worked perfectly for two months. Maybe that little bit of RF from the RX port was what was messing with the firmware timings. Vin KD1GA

Hi Vin, Check to see if there is a '-CV' in the serial number of the unit. That would tell you if it had a Cyclone 5 'V'. There is no harm in trying both the EP4CE115 Cyclone IV or 5CEFA9F31 Cyclone V firmware images. If one works, that is the Cyclone variant that your unit has. -Rick / N1GP Hi Ric...

Thanks so much for the fix. Interesting I always thought all the MKIII had the same Cyclone chip. Guess I'm opening up my Anan this weekend .

I wanted to post a follow up to my Protocol 2 issues, so it wouldn't just be hanging out there. I believe I found the issue , so with my fingers crossed it appears to have been RF into the computer. I looks like some stray RF through an HDMI cable from a monitor close the amp output. I switched out ...

Does anyone have news or thoughts regarding Protocol 2 ever being more than Beta for the 7000's?

Working great here, Thanks for everything you do!!!

I found another source of RFI through and Mic switch that showed up on my audio even with Protocol 1. Removed the offending switch and ran XLR direct to mt sound card and all is fine with Protocol 1. I'll reflash back to 2 and advise, fingers crossed again. I guess when the leaves come down I will h...

Nope all the issues have returned... Errr guess a G2 is in my future.

Okay folks so far so good. Reloaded Protocol 2, Metis_Orion_MkIII_P2_CV_21.7. Removed and installed latest Thetis and restored existing data base. So far rock solid, fingers crossed. I would like to apologize for being convinced it was a hardware problem and spreading information that so far appears...

It might be time to try a different Ethernet card. They are cheap enough. I had a NIC with a Qualcomm chipset that wouldn't work at all with our radios. I had another with an Intel chipset that might have been a counterfeit device, it worked but poorly. Thanks for the suggestion. I have tried a few...

When I was having a issue with my 7000dle mkIII and protocol II I went into the network card setting and reduced it down to 100mbps with a bandwidth of 768000. And I still run 768000 just to keep it tamed. I no longer have to run the nic card at limited 100mbps after the latest firmware. I hope som...

Thanks for the response so I can rule out Windows hopefully. Guess I'll role the Thetis version back well .

Hi Vin, Sorry to hear of your troubles getting P2 to work on your ANAN. I take it you have a MkIII which is using the Cyclone V FPGA, 5CEFA I wonder if you could try the below gateware, it is generally all of the Protocol 2 with the exception of Gigabit Ethernet support. It runs the same speed as P...

Same issue here, started after latest Windows 11 beta update that did fix the Direct-X meter sizing issues. I'm wondering if are using Windows 11 and if so what version.

I would love to hear what NIC tweaks you applied that actually help, please share.. I have purchase three different NIC's messed with the settings until I was blue in the face and still had a very sketchy connection. Anyway its all a moot point now, Apache labs has got back to me and explained very ...

Yes both of you were correct it was a in override settings, operator error for sure. Thanks all.

I don't believe so, VAC works fine when initiating transmit with a mouse click of the MOX button. The issue is when initiating transmit with footswitch, transmit is initiated, however no modulation.

Okay a plea to Apache Labs has been sent. Thanks again Vin KD1GA

So you think it could actually be a hardware problem? I guess I was simply convinced it was a timing issue, but I guess slight differences in chip run could mean some are less tolerant than others. I'll ping Apache and see if they will help. Thanks as always for the great support you provide to the ...

Thanks for responding. Running VAC, no mic, really strange just rolled back to protocol 1 wonder if as you stated if I do have a hardware issue.

Owning my 7000 MKIII for a few months now I really had no choice but roll it back to protocol 1. Radio worked moderately well but was plagued by intermittent issues, I.e., buffer overruns that would cause receive audio issues, sequence errors that also caused actual transmit audio issues, infrequent...

I recently rolled back my MK III to protocol 1 but that disappointing but needed change aside, I’m sure my problem was me changing a setting but can’t seem to find it. My issue is when I transmit by using mouse click on MOX all is fine but when I use my foot switch radio goes into transmit but no mo...

Thanks for confirming. Short run for the MKIII so I would guess that limits the chances of seeing a P2 firmware timing enhancement anytime soon.

Has this model been discontinued?

Yes! The latest update fixed the Direct-X issues here as well.

Yep but now may change to TCIP

You didn't show the HRD settings. Assuming HRD and Thetis are running on the same computer you don't want to use a splitter, you want to use a pair, and you don't need the connector either. Delete the connector. Change the splitter to a pair. Put COM20 into HRD and COM21 into Thetis and you should ...

Hi, can u share the VSPE configuration? Maybe a screenshot. I am using a "Pair" in VSPE (ie. COM15, COM16). In Thetis I have set COM15 and in the logger COM16 (but its not HRD) 73 Ernst Sorry for the late response and thanks in advance for the help KD1GA Here are a few screen shots of con...