Great
Thanks for checking!
73

Thanks for confirming the Windows 11 change on that key. Since they're changing defaults around in there, can someone plese check to see if the "Pro Audio" key is still there by default? Thetis depends on that key being present in order to elect participation in the Multimedia Class Schedu...

Can we maybe start a new topic that covers the 8000DLE that was introduced today?

administrator wrote:1. Incorporates the Orion MKII rev5.2 with the Tx attenuator

So, what happened to the Orion MKIII that started shipping back on July 1, 2022 ??!!??

Hi Jim,
Was that a "bare metal" installation of Windows 11?
73, Bryan W4WMT

n1gp wrote:I wonder what his serial number is, hope it doesn't break the:
MkIII is S/N DX8300497A and higher
rule.

Rick,
His serial number is 534A.
So, the rule seems to hold, and he must have an Orion MkIII board after all.
Whew!

73!

n1gp wrote:BTW, I loaded the P1 F/W Metis_Orion_MKIII_rev5.rbf on my MkIII and Thetis
displays: (Protocol 1 v2.7)

Holy Smoke!
I will email WB5QFZ and get his serial number. He must have a MkIII board, in spite of what Thetis displays?

Just when you thought things couldn't get more confusing: I had a long QSO this morning with David WB5QFZ who just received his new 7000DLE MKII on Friday. It had been on order from HRO since January! It came with P1 firmware installed, version 2.7. This means it has an Orion2 board NOT an Orion3. S...

I believe the wideband data and the DDC data arrive at the computer on different UDP ports, right?
Can something be blocking the DDC port, but not blocking the wideband port?

Don't forget to check the windows firewall.
It can make Thetis act as you describe above.

n1gp wrote:Here is the Protocol 2 firmware for the Orion MkIII.

Hi Rick,
Thanks for bailing us out!
Did you have to fuss around a lot with the timing closure, or did it drop right in for you after making the mods?
73,
Bryan W4WMT

w-u-2-o wrote:You are right. Any suggestion on how to better describe the configuration that isn't a mouthful?

No clue!
Abhi is using the "Mark" designator to iterate both the rig and the board.
Sort of confusing, but we shall overcome

Just to be clear:
We're not really calling the rig a 7000MKIII are we?
Isn't it officially a 7000MKII, but with an Orion MKIII SDR board (aka Orion3)?

73!

I was talking about the buffer size shared between Thetis and VM.

AFAIK, Thetis does not send buffer size information ASIO interfaces. Therefore it is quite possible that the M-Audio buffer size and the Thetis VAC buffer size are mismatched. Purely for the benefit of someone searching this topic in the future: I recently did a deep-dive in the PortAudio source on...

Please forgive my ignorance, gents. I'm not a CW operator, nor can I hear what my 8000 is doing since it is located in a rack two floors beneath my operating location even when I pretend to be one! That's a pretty good way to solve the problem actually. Just move the SDR hardware out of earshot, an...

w-u-2-o wrote:Isn't this all a lot of effort when you can just switch to QSK and be done with it?

That's what we're talking about.
Inhibiting RL17 & RL19 while in CW (to minimize relay noise during QSK).
73

Yep. The only reason for the Nano microcontroller is to sense the input key dit and dah lines and hold off on the PS relays for 500 ms just to unnecessarily have them engage and disengage with every keyed element. I sensed the key line this way as there was no other way to tap a circuit point on th...

Not sure how that would work since RL17 and RL19 are controlled differently. Right, it wouldn't work i.e. not without reprogramming the SPI commands sent to the relevant shift registers. But after thinking about this for an hour, I now remember the terrible trouble Phil and Rick were having with th...

RL17 and RL19 are both driven by identical but separate 8-bit shift registers. Register U5 controls T/R relay K5 and RL19, and U5 must remain connected to K5 to perform the T/R function. That's even better then! Move RL19 over to the unused pin on U10 (which already controls RL17) and inhibit both ...

By the way, the PureSignal relays to mute in the 7000DLE in CW mode are RL17 and RL19. Studying the prints again, I see that the RY17 coil is tied to an 8-bit shift register (poor man's SPI). So we should be able to inhibit that relay (when in CW mode) with some relatively straightforward coding in...

FWIW, I don't get the "display glitch" here.
How does one produce it?

Like you, I don't use CW semi-break-in, but many CW ops can only operate that way. True! But that notwithstanding, wouldn't those ops be better off just increasing the "CW Break-In" delay to effect the same timing as semi? That way you'd have the best of both worlds, with that silky full-...

It is worth noting that this configuration does work for full-break-in QSK on Thetis/P2/Orion platforms. Indeed! In fact, the full-duplex QSK now available on the above platform makes old-fashioned sidetone completely passe IMO. You're just hearing yourself on the band, like a regular station. Chri...

That is what we are doing as we do not show the revision number in the title bar. 2.9.0 was the original release 2.9.0.1 can overwrite 2.9.0 2.9.0.4 can overwrite 2.9.0.1 Right, but what I was thinking is, e.g. last week when 2.9.0.3 went up to github.com/tapr for "official" maintenance r...

I will have a think about it, and probably recode the version detection for dB update. What about a scheme where the 4th segment (2.9.0.x) increments during a string of beta releases. But then, when it goes to the TAPR GitHub repo for release, the 4th segment is dropped and we increment the 3rd seg...

When I went back to 1 and 0 it continued with the weird behavior. So any settings other than this were not done by me. Could this be attributed to the "latency creep" phenomenon reported earlier (more than once) by W9AC? Paul reported this happens only when using the hardware CODEC in the...

Yes please!

In fact, all these tutorials from Dr. Pratt should be in a big wiki somewhere. IMO

ramdor wrote:Oh, and you can expand/shrink by dragging that vertical white bar left-right, up to 30% of infobar width.

Ah ha! Nice

Hi Richie,

In your video above, it appears the PureSignal indicators in the info-bar have reverted back to the old way of doing things?

73,
Bryan