I love VARA, so much so that I paid for the HF version. When I like something I have no problem supporting its development. I would so like to see it ported into Pat! Sure wish the developers could see the value that the RPi ham community could afford them. Sigh.
Jay
73 de N0SR?

To reach the logger use 127.0.0.1/log or Pi.ip.address/log if on a network. If connecting to the pi via hotspot, 10.10.10.10/log
--

Trying to run the FD Logger program I've run into a problem.
Entering 127.0.0.1 into the browser I get the Jason's emergency email server rather than the logger.
It seems I should be able to enter a port number and get to the logger; lacking that, how do I disable the Emergency Email Server I apparently installed?

I’m no Linux expert, but what does the contents of your /etc/wpa_supplicant/wpa_supplicant.conf file look like?

DO NOT forget to erase the contents of the “psk” lines before you post. I’d imagine you don’t want us all to see what your network passwords are. But with my limited knowledge, I’d guess you have a conflict in that file that is causing issues.

—Mitch, N7USU

If you installed log viewer, you can use it to delete the log. Otherwise, look for a file in the Documents directory called mylog.txt. Don't delete the file itself or Conky may fail to start. Instead, open the file and delete the content and then save the empty file.
--

Unfortunately Vara only releases for Windows. The developer is charging $$ for Vara unless you want throttled speed. I heard that John Wiseman offered to port it to Linux and the developer declined but I can't find where I read that. John is the same one that brought ARDOP to the pi. I suspect Winmor may be phased out in the future but I suspect ARDOP will be around much longer.
--

On Thu, Jun 25, 2020 at 07:51 PM, Bill Dornbush wrote:

Jason KM4ACK,
After working with Build-a-Pi for a while, it appears to me that things are built to work with specific hardware that you have and tested this with.
It would really help to have a list of what that hardware is so I would know if I had different hardware, where I might run into problems.

It's not intended to only be used with certain hardware. I do my best to make sure that isn't the case. I am limited to what hardware I own that I can test with. I have a list of recommended accessories on my FAQ page There's a link at the top.

Thank you for documenting the changes needed to make this particular GPS work. I have opened an issue to see if I can support this type of GPS in the future.
?
--

开云体育

Must be a RPi issue. I left HotSpot disabled overnight and when I got up this morning it had gone back to the double arrows. Not sure what the issue is.

Is VARA currently supported for the RPi or on the project map? ? Eventually ARDOP and WINDMORE is to be phased out.

I just finished building the QRP Guys?40/30/20m DSB Digital Transceiver II Kit. I also bought and assembled the SI5351A 160-17m VFO kit. I may do the initial power up testing tonight. I don't like to do things like that at the end of the day but I kind of want to see it powered up.The VFO doesn't require that I use a frequency counter to set it but it's better to use it and, of course, my counter is on the workbench at home (I'm working out of town right now). I can use the o'scope to get me by for now. It was easy to build however the VFOP does require a little bit of SMD soldering. I have done enough SMD work that it was not a big deal to solder the SI5351A on the board. You'll need to wind toroids, again, not much to that. They say it's a 3 out of 5 build difficulty. I think it was a 1 out of 5. If you don't build a lot of kits, don't know how to wind toroids, or can't do SMD soldering (only 1 piece on the VFO board) then it's probably a 3.

It uses VOX keying. There is no CAT control. I think, if it works, it'll be a real nice add to the Raspberry Pi portable ops kit. I just realized that I didn't mention that its an FT8 transceiver :) Imagine running a PI and a little FT8 rig that fits in the palm of your hand together. It weighs about 32oz and it draws about 350mA when transmitting according to their site. At 3 band modules at 1oz apiece and it still doesn't weigh much. Other specs from the website:?

The transceiver output remains the same at an approximate 2.5 watts on 40m, over 1.5 watts on 30m, and over 1 watt on 20m. The receiver sensitivity was measured at .4uV (-115dBm).?

73
NE5U?

Mike

I think it worked but the log listing in Conky still shows the grid square errors. It didn't add any so I am pretty sure they are stale. How can I delete the log?

May have spoken too soon. I ran Build a pi to check for updates and many things hamlib, fl suite etc said needs update. And then I noticed the double arrow again on my wifi.

Seems to be holding so far. It has been very stable for me until this issue.

Thanks for the info.
I will give it a try for my usb-Prolific_Technology_Inc._USB-GPS.

NOW, RFI "issue" using the "standard" GPS with my stacked (open) RPi. I think the same problem will happen with plastic cases. Not a build-a-pi V3 issue...

I re-mounted a RPi into a metal case with a heat sink and small fan and the GPS works... You, decide... It would not work before, window or not (open case). I have a metal case with plastic top/bottom that had problems, too.
It runs about 10C hotter, though.

73, steve WB3LGC

Jason KM4ACK,
After working with Build-a-Pi for a while, it appears to me that things are built to work with specific hardware that you have and tested this with.
It would really help to have a list of what that hardware is so I would know if I had different hardware, where I might run into problems.
--
--Bill AA6BD

I ran
$ sudo systemctl start gpsd
and?
$?systemctl is-active gpsd
now reports active
But?
$ ruby ~/bin/conky/get-grid
still shows an error
--
--Bill AA6BD

systemctl is-active gpsd
says inactive.? What is the magic to activate it?

$ cgps
shows that it can pick up a signal so something is working.

--
--Bill AA6BD

I don't think it is an RFI issue, but I always position my GPS near a window so it is away from my Pi.

I tried a bunch of things before it worked but I will try to detail the steps as best I can.
I installed minicom and used it to verify that the GPS was working.

$ sudo apt-get install minicom

$ minicom -b 4800 -o -D /dev/ttyUSB0

My best source of info was?

$ ls -la /dev/serial/by-id

lrwxrwxrwx 1 root root 13 Jun 24 14:10 usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0 -> ../../ttyUSB0

Note: usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0

$ sudo nano /lib/systemd/system/gpsd.socket
????????? --
????????? #Find the line
????????? ListenStream=127.0.0.1:2947

change it to

? ? ? ? ? ListenStream=0.0.0.0:2947

?

$ sudo nano /etc/default/gpsd
make a few more changes,

1. Find the line that says USBAUTO.? This setting will let gpsd interogate any new USB devices to see
????? if they are GPS receivers or not.? I generally *never* recommend auto anything as it can interfer
????? with other programs.? I recommend to make the line read:

USBAUTO="false"

2. Find the line that says "DEVICES="" and update it to reflect your proper device-by-id serial port.? In my case:

?

DEVICES="/dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0"

Then it worked as demostrated by?
$ cgps
and?
$ gpsmon

--
--Bill AA6BD

On Thu, Jun 25, 2020 at 03:26 PM, Bill Dornbush wrote:

I am not sure how to proceed from here.? Ideas?

Sorry Bill. I am not going to be much help as I don't have that GPS unit to test with. It looks like the ruby script isn't working with that GPS model. Is GPSD running? Try running
systemctl is-active gpsd
and see what it returns? It should show active.
--