Bryan, That’s the problem! Most of the critical lines are missing in that file. Mine reads: chip "ads1015-*" label in3 "User ADC Differential“ label in4 "+12V" label in6 "User ADC 1" label in7 "User A

#sensors #adc

Bryan and John, Essentially the same as yours Bryan! The one line different says: in5: +2.50 V Same as on the Dashboard. The very first thing I did when I re-checked it just now was to update the DRAW

#sensors #adc

Bryan, That’s very interesting! Here is what the new board I just received is reporting: I see “in5: +2.50V” not “+5V: +5.06V” on that top line. Maybe I need to run an update of code here? Jack – KD4I

#sensors #adc

Great! I missed that he was building. Best success to him! -Jack

#sensors #adc

Bryan, Quick Question on that: Has John implemented this in the DRAWS Manager? Does not appear to be the case. At the bottom of current version, the status bar says: Digital Radio Amateur Work Station

#sensors #adc

John and John, Have the 7300 here and have been using it for several years (yes – early adopter). Everything available over USB depending on rig settings and mode of operation are: Audio Out (analog),

Hi Basil, Well, I finally got a chance to do a "multiswap" to see what hardware is working and what is not with this DRAWS system. Previously determined that the GPS antenna we have discussed was bad

#draws

Basil, The saga continues. It also turns out that the original GPS/LNA antenna had gone bad along with the Pi3B+. It was working before the RPi started into the overheating problem. So what ever start

#draws

Hi Basil, Good news/bad news story: DRAWS hat appears to be OK, the Pi3B+ is a sick puppy. Silver lining: discovered just how fast everything DRAWS seems to respond with a Pi4. That may be the replace

#draws

Hmmm... and Pi was feeding the DRAWS card, not visa-versa... but that should not be causing the CPU to overheat! -Jack

#draws

Ok.... now, I did not notice that set of TEMP lines in the output because I was so focused on the sound device/ALSA and GPS lines. I have heatsinks on the Pi. I have not heard that lack of ventilation

#draws

Hi Basil, Just when I thought everything was pretty stable, I started to get protests from xastir that my GPS wasn't behaving. Dropped out of xastir and ran gpsmon only receive a blank stare... Unfort

#draws

Very Good. Was able to install what I needed. That fixed it. Not sure what I did to cause the file corruption, but dpkg behaves itself now. Back to "prime time". Much obliged.

OK... that seemed to do something: Console output: pi@kd4izdraws2:~ $ dpkg -l "rpi-eeprom*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWa

Ran the commands and here is the console output: pi@kd4izdraws2:~ $ sudo su root@kd4izdraws2:/home/pi# dpkg -l "rpi-eeprom" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpac

Basil... Will do as you suggest momentarily. Sorry for the confusion. I am not running synaptic because it never was successfully installed. I have been strictly using the apt-get commands you suggest

Hi Basil, I ran your script sequence from the previous note- sudo su apt-get update apt-get install --fix-missing apt-get dist-upgrade As requested, here is the console output from that session: pi@kd

Thanks Basil, It worked. But when I went to wrap things up for my style of operating with raspbian LINUX, I tried to install synaptic and xscreensaver. Both attempts started by retrieving and failed a

Did not exactly follow that but did "some". My error was "xastir: error while loading shared libraries: libgeotiff.so.2: cannot open shared object file: No such file or directory" so I'll back up unle

I have a 2nd DRAWS unit I use for porta/mobile activities and an SD card that already has the “virgin” image on it. I will give it a try this afternoon and record the results. More to come. Best