Is there a protocol-2 image for the TRX DUO / Red Pitaya yet?
Bryan

Hi All,
How do we know the rumbling sound wasn't actually a signal on the band?
His panadapter is zoomed out so far, I can't squint hard enough to see if the rumble is actually within the receiver passband or not.
73,
Bryan W4WMT

Not aware of the ".26" series.
But you did try the ".27A/B/C/E/F/G" series, right? Those are the ones that work FB here on my EP4CE based Orion.
73, Bryan W4WMT

Sorry to reincarnate this thread after all this time. With the possible exception of Juha above, no one has reported successfully running TCI with the RF-KIT amplifiers. If there are successful users out there anywhere, will you please kindly post a screenshot of your Thetis setup tab to help me get...

W7GES wrote:i monitored via my TS-890 on the other side of the shack and the audio sounded fine.

Hi George,
When using the TS-890 as an off-air monitor while transmitting on your G2, how did the audio latency seem to you?
73,
Bryan W4WMT

Hi Laurence,
I remember, from your SDRA 2022 presentation, that you were favoring 4096-byte DMA transfers on the PCIe bus for the various streaming channels within Saturn. Did you finally settle on that number, or were there further refinements?
73,
Bryan W4WMT

Yes, there was a "D" build, but it was DOA (according to Rick).
73!

EDIT:
I meant to say, there was a Orion_MkIII_Protocol_2_v2.1.27D.rbf, is that the one you're looking for?

Looks like the 7000DLE was taken down from the Apache Labs website over the past weekend.
Too bad, it was a good rig
73,
Bryan W4WMT

Joe wrote:Just thinking about interface options.

FYI another option:
Lynx Studio makes a nice line of PCIe audio interfaces that DMA your audio samples directly to/from the computer's data bus.
73,
Bryan W4WMT

Something to ponder:
Is the Saturn being manufactured under openHPSDR licensing?
Or is this now a totally new platform and considered completely proprietary to Apache Labs?
73,
Bryan W4WMT

Taiga wrote:Upgraded from 2.9.0.8 -> 2.10.0 VAC2 stopped working.

Surely, you know this.
But you did have RX2 running when you were attempting to use VAC2?
73,
Bryan

w9ac wrote:Anyway, I've not kept up with Thetis notes over the last two months, but I'm assuming there's no means at present to save and recall multimeter containers?

Good question.
So I restate it here.
73, Bryan W4WMT

I can personally recommend this one made by a couple of retired Tektronix engineers. It's sort of expensive but built like it came from Tektronix. And for an extra $75 it will come with its own NIST certificate

https://preciserf.com/shop/ddc545-dual- ... l-coupler/

73,
Bryan W4WMT

What about the poor guys that ordered a 500W 8000DLE MKII way back in August 2022?
Surely, they are not being asked to now go to the back of the queue.

I am suspicious of these new Intel performance cores and efficiency cores. Is there going to be some Windows API that allows applications to specify that certain threads get first dibs on a performance core at thread creation time? Otherwise, our quasi-realtime streaming threads in ChannelMaster may...

My Bodnar drives my Presonus Studio 192 Mobile with no issues.
I think you'll be fine.

For those using the Leo Bodnar GPSDO are you running a 10 MHz bandpass filter to mitigate possible harmonics from the square wave, and If so what make and model of BPF? Not using a BFP with my Bodnar GPSDO here. I'm using the dual output Bodnar with 10Mhz driving the Anan 7000 ref input and 48kHz d...

Are the PreSonus Quantum Series interface units the only ones now left from them that still offer Wordclock reference input?

DL2XY wrote:the SMA XVTR output is for max. 0.5W only.

Hi Walter,

Do you happen to know why the output is only 0.5W? If you look at the schematic, it appears that the output of the 2W driver stage is routed to the SMA socket (when operating in XVTR mode). I've never understood this?!?

73, Bryan W4WMT

I sent you a PM, but you didn't open it.
Would you rather I email instead?
Thanks,
Bryan
W4WMT

Thetis code has been described as a nasty, tangled bowl of spaghetti. I think that is a fair statement as long as you're talking about the Thetis project per se. The WDSP and ChannelMaster projects, on the other hand, are well structured and well documented IMHO. The learning curve is steep, but en...

I remember from TeamSpeak sessions, that Warren NR0V was working on this within the context of ChannelMaster support for the DFC (Direct Fourier Conversion) based Minerva board. The trouble he was having was related to thread scheduling of the CUDA cores, in support of the multi-threaded requirement...

n1gp wrote:I submitted an Issue on Ramdor's github repo for this since Thetis
should be keeping track of the proper SetPK value for P1 or P2.

Another P1 related disaster
Why on earth couldn't we have left it behind when we had the chance?

Is it possible to post screenshots and/or images directly into Private Messages?
TIA, Bryan

I have an ancient, outstanding issue where CM (as opposed to wdsp) hangs on to a handful of threads between every Start() invocation. My comment about AVmm was mostly for ChannelMaster.dll, in particular the audio threads. In my view the audio is #1 priority (literally), behind even the UI responsi...

I use the new AVmm thread priorities if I can, but fall back to less poky threads if these are not available. Hi Steve, Just FYI: Back when we enabled MMCSS in Thetis (version 2.6.9 I believe), Warren NR0V and I carefully chose only the most time-critical DDC, DUC, and audio threads in WDSP & C...

w-u-2-o wrote:If it's doing that then it's probably firmware. I've not seen or heard of that error modality, though. Is this something you've actually seen?

Oh yeah. That's what I meant by "rewind" type sequence errors. I'll post a screen shot of one the next chance I get.

w-u-2-o wrote:That seems like an oblique way of saying that 7000's will no longer be produced.

Sure does!

Right, but what I'm thinking of is the type of sequence error where the sequential numbers jump back (say by 100) and then start over again from that point, counting forward and repeating the sequence of numbers it just ran through. It's hard to imagine how the network stack could do that?!?

Once the new Saturn SDR boards become available and get into common use, I guess we'll finally prove whether or not it was FPGA issues causing all the sequence errors.

The "rewind" style sequence errors seem very hard to blame on the stack. How would such a thing even happen???