Hi all, I'm using SDR Console v3.0.23, PC with i7 CPU, 16GB Ram and the Pluto is connected to my local GBit network via USB-Ethernet adapter. While there is no issue when the Pluto is connected via US

#pluto

Hello Jayson, Thank you for sharing your experience and for your hints. I understood that transmitting is working for you at lower bandwidth despite using a 100 MBit/s network adapter. I concluded tha

#pluto

Meanwhile, I got TX working with the Netgear switch as well. The assumption of a flowcontrol issue showed to be right, that old Netgear switch (GS105E) has IEEE 802.3x flowcontrol disabled by default.

#pluto

I've seen that some OMs directly connected an LVT-354T to the GPOs. Probably works, but I would not feed comfortable with connecting a diode directly to an logic output port without current limiting.

#pluto

The Si5351a works quite well if you use integer divisors, but do not expect any miracles from a $1 chip. As soon as you use fractional-N divisors, spurs show up on the output signal. I did play around

#pluto

Automatic gain selection seems to mask an issue, as there is a channel attribute write error visible in the log on each start of the device. 10:34:20.650: Radio PlutoSDR> SetRXGain, RX Frequency 73974

Thank you Simon for fixing the RIT activate/deactivate issue. Playing with the RIT, I observe two issues, not sure if this is the intended behavior? First, the RIT setting doesn't seem to match the ac

Hi Sigi, Strange, I do not see a 4:3 factor, but a more or less exact 2:1 factor. Setting RIT to max (99.999 kHz) leads to ~50kHz shift. Sorry for posting already known issues, but as there is no know

see screenshots :) So you used a different approach by looking at the beacon sync view while I looked at the main spectrum display, not knowing if the issue affects the beacon view and the main view i

Good catch! The funny fact is that with the bandwidth set to 2.1MHz or higher, the issue is no longer visible: the RIT works as expected and the beacon view does not change when engaging the RIT. So t

Hi, With Pluto RX-Gain set to 'Manual' (default gain 50dB, visual gain -30dB), the initialization seems to fail from time to time when starting the radio (either after program start or after stopping

#adalmpluto

After some more testing, the issue seems to be related to the visual gain setting at first start. After setting the visual gain to 0dB (and slightly adjusting the low dispaly levels), I do no longer s

#adalmpluto

Just adding that the issue is still there on first start of the radio after powering on the Pluto and visual gain set to 0dB . I have to touch the hardware gain setting to get the display back to norm

#adalmpluto

Hello jdow, I completely agree with your writing. This occurs when the original requirements did not stipulate design for maintainability and if change management is not strictly handled. However I do

#adalmpluto

Hi Nils, As long as my LAN problems persisted, I experienced some waterfall freezes as well, but they were temporary and did not last more than a few seconds. They were always mapped to pairs of entri

#pluto

Hi Nils, As LAN mode is realized by a USB-to-LAN adapter, LAN mode is affected as well. AD discusses the problem that is assumed to be fixed by the "ground mod" on their wiki-page in section Why do a

#pluto

Hi Nils, Your logfile does not show obvious hints apart from the "not ready" message. From what I've seen so far, I would also suggest to do the "ground mod", eihter by replacing R88 as suugested by A

#pluto

Hello Simon, There is no big difference between build 2319 from 17:54 and build 2319 from 06:11 (two releases with the same build number ?). The beacon sync is not as stable as it was with release 3.0

Hi Simon, Thank you for fixing the issue. With build 2320 the beacon sync is as stable as it was with V3.0.28. 73 Jean DJ0VL

Sigi, I guess you are mainly seeing the short time (in)stability of your TXCO and not the (in)stability of the beacon sync loop, double-check with beacon sync disabled. With an decent OCXO based refer