- Sep 6, 2016
- Reaction score
For longer distances, yes, vertical orientation is better. However, a dipole antenna will having trouble picking up a source in the direction the antenna is pointing. 20+ miles of range is enough for me, and I'd rather be sure that a plane above me is being picked up reliably.Just a note for those that might be playing with the PCB antenna shown in Post #3 of the locked build thread.
Although @johnboy00 reports good luck with this laying flat on the rear deck, I think this antenna really wants to be positioned vertically. Testing yesterday with a laptop in my 4Runner in the driveway, I had much better luck positioned vertically on one of the rear cargo windows vs when laying flat on the molding of the same window.
I will also be testing a roof mount antenna once it arrives to see if the potential improved reception is worth the hassle. Looking at aircraft tracks here in New England the speed enforcement aircraft is always within 2nm of the road, but I am concerned given the low flight level of the plane (typically <FL2500) and the need for detection *in front* of the vehicle, that placement in the rear window/deck may be suboptimal. More to come...
This in-car receiver replaces external servers as a data source, so any other apps would need to support pulling data from it directly.Gotcha, i was looking through the code and didnt see where it routed the info to JBV1.
I use HR more than JBV1 so id needs to figure out if this could be used for his servers as well.
Are you starting JBV1 *after* the hotspot is created and the Pi is connected to it? That seems to be most reliable for me. I hope to be able to work on it more soon, since there's definitely room for improvement when the hotspot is on the JBV1 device.I finally had a chance to put this build together yesterday (thanks again for the brilliant instructions!).
I'm having a hell of a time getting JBV1 to detect the Pi when its connected to the phone's mobile hotspot. I can confirm that the Pi is indeed connected and that I can open up the http://<IP_ADDRESS>:8080 page on the phone's browser. The app just never connects to the Pi. Pixel 5 on Android 11, FWIW.
Works brilliantly when both are connected to my home WiFi though. I think tonight I'll test with the phone and Pi connected to another phone's hotspot to see if that makes a difference.
Any other ideas of things I could check/try short of getting a dedicated hotspot for the car?
Hmm, that could be a factor. I was using Tasker to automate enabling the hotspot when I launched JBV1. I'll test again with manually enabling the hotspot, confirming the Pi is connected, and then launching JBV1 to see if that helps. Thanks!Are you starting JBV1 *after* the hotspot is created and the Pi is connected to it? That seems to be most reliable for me. I hope to be able to work on it more soon, since there's definitely room for improvement when the hotspot is on the JBV1 device.
wlan0 only.I noticed that JBV1 now it allows specifying the Carputer's MAC address.
I'm curious, does JBV1 only search wlan0 for the Carputer MAC address? Or does it search all interfaces, such as bt-pan?
I was trying to see if it would be viable to use a bluetooth tethering (with the JBV1 phone sharing) to my carputer while using wifi tethering (with my main phone) sharing internet to my JBV1 phone.
The idea being that my "car" could boot up my JVB1 phone and Carputer and they could connect to each other over BT without relying on my main phone to be there to bridge the two.
It seems like it should work, when I manually initiate the connections my JBV1 phone can access both the internet and my carputer SkyAware page, but JBV1 can't seem to find the Carputer on bt-pan even if I specify the MAC, so I'm not sure what's missing.