- #Planeplotter vnc how to#
- #Planeplotter vnc install#
- #Planeplotter vnc Pc#
- #Planeplotter vnc windows#
Surely you're not saying turn off all logging. Interesting that you say turn off logging and voice decoding in JAERO. Hopefully I spread the work over the two machines. I moved Firefox over to the Linux machine as well as SDRRx. Then with the other apps I'm running it pushes the CPU into 100%. Between the two they eat up over 30% CPU, then Firefox eats over 30% and SDRRx eats up 20+%. SDRUno is made up of two main process: SDRPlay_apiservices and SDRUno Application Software. I use SDRUno for decoding ADSB with their version of Dump1090.
SDRRx only works with RTL-SDR dongles currently. I use SDRRx being driven by a V3 SDR Blog dongle. First, I don't use SDRUno for Sat ACARS (SDRRx/JAERO). My win7 machine is kind of the hub for everything I have going on.
#Planeplotter vnc Pc#
I'm sure they will be much happier working on the same PC with noĪs usual, there's always more to the story. I'll circle backĪfter I get my 10 JAEROs set up on the Linux machine and working with Thanks for listening to my ramblings and stumbles. Realistically I'm only postponing the inevitable.
#Planeplotter vnc windows#
Then I can get it off of the windows machine. I can't wait until they come out with their I'm now installing JAERO on the Linux box. Idea that I don't understand all I know about this subject. Trying to get SDRx (on Linux) to talk to JAERO (on windows) raised the To get a remote (Linux) machine to send data to a Windows machine? I'veĬreated a few Win7 firewall rules but usually its to get Windows to send Impression that JAERO was only a windows app. I went back and took another look at JAERO. > So what did you guys have to do to get your RPi to talk to On Sun, at 9:07 AM Mike wrote: On 10:23 AM, Mike wrote: I'm sure they will be much happier working on the same PC with no firewall rules to deal with. I'll circle back after I get my 10 JAEROs set up on the Linux machine and working with SDRRx. With all the stuff I'm doing I need a more powerful machine. The i3 is just too wimpy in this day and age's apps. But, realistically I'm only postponing the inevitable. I can't wait until they come out with their Linux version. The other big CPU hog on the windows machine is SDRUno. But my stumble with trying to get SDRx (on Linux) to talk to JAERO (on windows) raised the idea that I don't understand all I know about this subject.
#Planeplotter vnc how to#
But the question remains, how to get a remote (Linux) machine to send data to a Windows machine? I've created a few Win7 firewall rules but usually its to get Windows to send to a Linux box. On further investigation I see there is a Linux version :-O *Doh!* I was mistakenly under the impression that JAERO was only a windows app. So what did you guys have to do to get your RPi to talk to your JAERO machine?I went back and took another look at JAERO. So what did you guys have to do to get your RPi to talk to your JAERO machine? It doesn't id the app does it? When you guys run SDRx on RPis don't you have to do something to allow the RPi to get to the port that JAERO is expecting the data to come in on, on your Windows machine? I even setup a rule for it on the Linux machine's firewall but it didn't change anything. Do you actually have to tell the rule the path that SDRReceiver is installed in coming from the remote address? I would think all you're doing is letting the Windows box know the Linux box wants to send data to it on port 6003. Under the Programs and Services tab it points to the SDRReceiver.exe on the windows box.
#Planeplotter vnc install#
I checked the existing rule that was created when I ran it from the install on Windows initially. I tried creating an inbound firewall rule on the Win7 machine. The 'provided URL' being the Windows address. I got it setup and when I ran SDRRx I got an error message saying that "ZeroMQ could not bind to socket on provided URL.". So, I decided to move one of the big CPU consumers off to my Linux box. With SDRReceiver and 10 instances of JAERO I was running my poor i3 around 100% all the time.
0 kommentar(er)
