From my experimenting, (4 reloads of beta version 5) yes to your question below. You are unlikely to get anywhere until you run it. You can kill direwolf immediately as directed, then set up fldigi

See text below for my response to Basil's response. Gayland KG7GCF So I un-commented the "dtparam=audio=on" line in the draws://boot/config.txt file, saved the file, and rebooted. I then used the

If you have one of our beta images, you can quickly upgrade. From a terminal perform the following: cd /tmp wget https://s3.amazonaws.com/js8call/0.11.0/js8call_0.11.0-devel_armhf.deb sudo apt-get

Hi Gayland, Thank you for testing the DRAWS board. This email only addresses your audio problem. First uncommenting the dtparam=audio=on line in the /boot/config.txt should not cause your system to

Basil, Thanks for the quick response. I understand setting of PCM and LO Driver Gain. If I started with PCM at zero, I could not turn LO Drive down far enough to prevent the IC-7000 doing the

Hi Jack, Thanks for the console output. Your PCM /LO Driver Gain settings seem off to me. Those are the 2 controls for setting DAC output (deviation). The PCM control is the digital output setting &

Basil, That test got me part of the way there. DRAWS was apparently overdriving the audio front end of the IC-7000, hence the flashing TX led. I did not know it did that! The *showudrc.sh* output is

I haven't the sophisticated knowledge of how the DRAWS & UDRC perform their magic but I have the following observations. Out of the box, the DRAWS would not work with my Yaesu 857D when running

In general for debugging problems: Send output of: ~/bin/showudrc.sh ~/n7nix/debug/alsa-show.sh Use the following instructions for measure_deviate.sh to verify PTT & transmit

These CR1220s work well in mine: https://flic.kr/p/2dEEz8v 73!! David (KG5EIU)

Yes. Exactly what I was going to do. Just want to make sure that is sufficient to solve Gayland's problem. /Basil

Basil, John, All, Initially, Beta 5 seemed to work out of the box but I ran into some DRAWS audio and keying strangeness that is baffling me after 3 tries at installing from newly flashed microSD

Battery is CR1220 NON RECHARGEABLE

If not already present adding in n7nix install core script could be usefull to perform initial system time adjustment when GPS is not yet switched. This is my case for I did’not put any antenna

I did not install a battery yet in my DRAWS hat. None of the button batteries I have in stock fits into the case. Could someone give me a model reference or number. Bernard

From some google-fu: Note that the chrony service does not change the time. The often misconception is that the chrony service is setting the time to the one given by the NTP server. This is

Not to sound too dogmatic but text editors are personal and I've had this discussion a few too many times already. Put whatever editor you want on your installation but it most likely will not be in

I just loaded beta5 and going through it, I'll make a list here of suggested apps for the final image (or at least that people should consider installing) - geany: great little text editor, multiple

I believe it ran for a few hours without the update, in fact I was surprised when I finally noticed that the date and time were so off. I did not do anything with chrony nor the gps other than

My experience is that it can sometimes take 10 minutes for chronyd to sync. /Basil