No, problem. Been there, done that and am still there more often than I care to admit. Gayland KG7GCF

#drawsmanager

Charlie, I believe, John is asking you to run "which node" and "which npm" commands, which is a program that tells you if these programs are installed. Gayland KG7GCF

#drawsmanager

No John, I keep my eyes open and you guys haven't said anything about it that tells me that it is ready to ship and my need has never been urgent. I know the people at nw digital radio are good folk a

I ordered a case too. Months ago, it's kinda moot though as I've abandoned the draws and udrcs for a solution that has proven more successful for me. Would still like the case or at least to have my m

On your pi under Raspberry Menu/Accessories/SD Card Copier assuming that you've managed to pickup a usb sd card reader/writer when you've either purchased and SD card or bought one ( a very useful ite

I believe you want make sure you use the power input on the DRAWS and not the Pi itself. Gayland KG7GCF

#12vsupply

Ditto. Gayland KG7GCF

Basil, are there any ways to know when Anna's patches will be in place so that we can do upgrades? Gayland KG7GCF

I seem to be getting the same error when I perform a sudo apt-get upgrade on my DRAWS Beta 13 install based on a quick comparison of the make.log noted above. I'd be a tad more confident if I knew eno

Attempted to launch flmsg from menu and got nothing. Launch from terminal yields following error: "Flmsg: error while loading shared libraries: libjpeg.so.9: cannot open shared object file: No such fi

Honestly, haven't used rig control yet. I tried once or twice but never made much progress and my particular emcomm use doesn't really demand rig control. As for a cable, I believe a usb cable to the

I've been using a straight thru 6pin mini din <-> 6 pin mini din between my yaesu ft857d and UDRC/DRAWS for some time now without cutting any pins afaik. The only issue that I have with this is that w

I suspect Basil has it correct. I experienced similar conditions the write cycles take longer than one expects and concluding with a sync command will help insure that all write buffers have been writ

I suspect that the amount of increase needed was far below what Basil threw out. I went with 512 and even at the time was thinking that it was probably excessive. Like I said, I suspect that 256 MB wo

#fldigi

I just did a build on the latest stretch raspbian of the a current version of fldigi. It was necessary to increase the swap space on the current system to get a successful build. The default swap appe

#fldigi

Yep. Haven't seen any evidence of a pattern or cause though. It happen's sometimes when the system idles unattended and other times while I am using it. My suspicion is either a memory leak somewhere

#draws #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 menu

#betaimage #setup #draws

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 fldigi

#betaimage #setup #draws

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 install

#ntp #chrony #ntpd

FYI, I installed a battery before I first powered up the DRAWS but the time did not update even with a network connection and the gps antenna installed. I ended up setting it manually using the date c

#ntp #chrony #ntpd