<Key>chkRX2StepAtt</Key>
<Value>True</Value>
</Options>
<Options>
<Key>udHermesStepAttenuatorData</Key>
<Value>0</Value>
</Options>
<Options>
<Key>chkHermesStepAttenuator</Key>
<Value>True</Value>
Thank you Pavel,
that does show a step attenuator control for RX2 as well.
This way both base lines are independent.
Before both were controlled by the step attenuator of RX1.
But… it has to be “ANAN 100D” or so

- 61step_cq.png (5.93 KiB) 13759 mal betrachtet
The attenuator for RX1 goes 0..31 and 2..31 plus hidden 0+0dB and 10+20dB
61 different steps displayed / 5 different values are accessible 2, 4, 6 & b00 or b11

- chkRX2StepAtt_cq.png (7.07 KiB) 13759 mal betrachtet
The step attenuator for RX2 goes 0..31
31 different steps displayed / 4 different values are transferred 0, 14, 22, 30
As long as PCA92555s at 0x20..0x23 are active the Arduino at 0x40 is not served.
The Arduino would do most of the trick, but I’m afraid the rest of it is too special for third party PC, tablet, and smart phone software.
I didn’t succeed to activate the 12 Bit of the DC2PD pre-amps(s) at 0x60-0x61 yet.
How would that work and what does the control look like ?
Best regards
Werner
P.S.
Ich denke steuerbare, variable RX Abschwächer sind die Voraussetzung für „Auto Attenuate“ bei PureSignal.
Noch bin ich sehr weit entfernt vom Sendebetrieb, ich höre viel zu und oft ist das Thema:
Signalrückführung ( zum RX2 beim RedPitaya ). Oft klingt es wie endlose Stapel von sündhaft teuren SMA Abschwächern, kleinen Dosen mit Potentiometern, Rätselraten um Pegel und „Sampler“.
Manchmal klingt es wie mangelhafte Isolation zwischen den Eingängen IN1 und IN2,
ebenso oft wie mangelhafte Einstrahlfestigkeit direkt in den ungeschirmten RedPitaya.
Jetzt habe ich leicht Reden, rein theoretisch …
I believe controllable, variable RX attenuators are essential for the „Auto Attenuate“ function of PureSignal.
I’m light years away from transmitting with a RedPitaya, but I listen to many QSOs about signal feed back ( to RX2 for RedPitaya ).
Mysteries about signal level, stacks of attenuators and potentiometers.
Often it feels like insufficient cross talk IN1 <> IN2, quiet as often like direct reception of unscreened RedPitayas,
bypassing all the expensive SMA attenuators. But that’s all theory …
Google “auto attenuate puresignal” liefert eigentlich die Erklärung, für Hardware die wir nicht haben.
The default with ANANs and others … ?
P.S.P.S.
Ich habe den DAC0 gefunden. Es geht wenn außer ihm nur noch die AudioCodec Platine auf dem I²C Bus anwesend ist.
Andere Adressen dürfen scheinbar nicht antworten. DAC1 bleibt verschollen.
I did find the DAC0. It looks like no other address but the audio codec board is allowed to answer / be present.
DAC1 still doesn't happen ..
It does not matter if Hermes or ANAN or ...
A week later ..
P.S. P.S. P.S.
Meanwhile I would favour the Arduino Sketch of G8NJJ.
It has got the fewest things I don't seem to understand.
May be I've got some kind of an idea how
HPSDR<>RedPitaya's HPSDR compatible transceiver software<>hardware connected to the RedPitaya is communicating ...
The G8NJJ project is documented very well and for sure it is done very well ...
but I will start with a light version, using his protocol for the standard functions.
It contains anything like all others plus offers endless possibilities.
To start with is fine, to change to is hard.
It counts as well 0..61 in disjunctive steps.
A bug in HPSDR? A bug in the skin definition? There is more than 5 bits ? C0=0x14 HPSDR packet is 8 bit RX1 attenuation ?
It does treat the "Step Attenuator" for RX2 properly.
... but it looses the value after transmitting. Either two times #6 with first value OK. Or just one time and wrong.
Not synchronized with the skin and base line anymore.