KStars INDI System Requirements

[Andyb90]

On 16/11/2018 at 11:01, LightBucket said:

Great...glad you got,it sorted...why did you have to load drivers individually as they all come with INdI..??

The EQ dir can,e will work fine...

As for location, if you put that in during the set up wizard it should remember.... certainly don’t need to set up a config file, never heard of that being needed..

I installed the basic indi library with this command

sudo apt-get install libindi1 indi-bin

I don't think it includes any 3rd party drivers so I then installed the zwo and eqmod ones separately.

Connection to my heq5 worked well. I was able to slew to a couple of targets in kstars and track then park the mount.

I've also saved my location now. Think I must not have saved it correctly before.

I installed Astrometry.net today and the index files.

All in all I'm pleased with how the setup and initial tests have gone. I may get chance to try an imaging run tomorrow ?

Andy

[LightBucket]

2 hours ago, Andyb90 said:

I installed the basic indi library with this command

sudo apt-get install libindi1 indi-bin

I don't think it includes any 3rd party drivers so I then installed the zwo and eqmod ones separately.

Connection to my heq5 worked well. I was able to slew to a couple of targets in kstars and track then park the mount.

I've also saved my location now. Think I must not have saved it correctly before.

I installed Astrometry.net today and the index files.

All in all I'm pleased with how the setup and initial tests have gone. I may get chance to try an imaging run tomorrow ?

Andy

Good, I love it and would never go back to windows, an all in one software with solid drivers..

[Andyb90]

I got some clear skies on Sunday, so setup for some testing. Again connections to asi1600 (imaging cam), asi290 (guide cam), EFW and HEQ5 were fine.

I skipped polar alignment as I didn't actually realise there was an assistant in Ekos. Normally I use a Polemaster.

So I slewed to Capella and went straight to alignment. I tried an offline solve to begin with, but that didn't work. So tried online and it worked. I then had a look at the index files in options. It appeared I had some missing that were required, so downloaded them. I also thought it best to download the recommended files too, but got an error after the 3rd download. The error is documented on the INDI forum and adding the missing files manually is provided as a workaround.

Before downloading further files manually I tried the local solve again and it worked this time so I think the previous errors were probably due to missing required index files. I'll continue testing next session to see how I get on.

Next I went to the capture tab to focus the 1600. I used the preview button for that. It took me a while before I realised that I had to mark the stars on the preview image before I could get a HFR value. Once that was sorted focusing was straight forward.

Next up was guiding and this is where I came unstuck. A silly mistake really, but I didn't see it. I had the Guider set to asi290 correctly, but the Via option was set to the 1600. I spent a lot of time trying to figure out why the star wasn't moving during calibration. Then finally realised the Via option should be set to EQ MOD for my setup. Oh dear!

After that calibration worked and guiding was up and running pretty quickly. Unfortunately by this point the wind was starting to pick up quite a lot and I was a bit concerned so decided to pack up. The initial guiding results were pretty good though considering the wind, just under 1 arcsec.

Next session I'll see if I can get an imaging run going and then try to use VNC Viewer on my tablet to remote onto the laptop. I've tested the connection already so hopefully it should work. Will also be trying to Polar Alignment Assistant too.

One gap that I didn't account for is with my Hitec Astro Mount Hub Compact. I normally use it for dew heater control and previously for focuser control, but unfortunately it looks like the software is Windows only. So I'd need another option for dew control.

Also it would be really nice if I could use my Avalon mount with INDI. Looking on the forum I think it may be possible, but need to do some further reading.

I do like KStars too. Its nice to have the planetarium functionality, including features like the DSS Overlay when exploring for targets. I also like the 'Whats Up Tonight' option.

Andy.

 

[LightBucket]

1 hour ago, Andyb90 said:

I got some clear skies on Sunday, so setup for some testing. Again connections to asi1600 (imaging cam), asi290 (guide cam), EFW and HEQ5 were fine.

I skipped polar alignment as I didn't actually realise there was an assistant in Ekos. Normally I use a Polemaster.

So I slewed to Capella and went straight to alignment. I tried an offline solve to begin with, but that didn't work. So tried online and it worked. I then had a look at the index files in options. It appeared I had some missing that were required, so downloaded them. I also thought it best to download the recommended files too, but got an error after the 3rd download. The error is documented on the INDI forum and adding the missing files manually is provided as a workaround.

Before downloading further files manually I tried the local solve again and it worked this time so I think the previous errors were probably due to missing required index files. I'll continue testing next session to see how I get on.

Next I went to the capture tab to focus the 1600. I used the preview button for that. It took me a while before I realised that I had to mark the stars on the preview image before I could get a HFR value. Once that was sorted focusing was straight forward.

Next up was guiding and this is where I came unstuck. A silly mistake really, but I didn't see it. I had the Guider set to asi290 correctly, but the Via option was set to the 1600. I spent a lot of time trying to figure out why the star wasn't moving during calibration. Then finally realised the Via option should be set to EQ MOD for my setup. Oh dear!

After that calibration worked and guiding was up and running pretty quickly. Unfortunately by this point the wind was starting to pick up quite a lot and I was a bit concerned so decided to pack up. The initial guiding results were pretty good though considering the wind, just under 1 arcsec.

Next session I'll see if I can get an imaging run going and then try to use VNC Viewer on my tablet to remote onto the laptop. I've tested the connection already so hopefully it should work. Will also be trying to Polar Alignment Assistant too.

One gap that I didn't account for is with my Hitec Astro Mount Hub Compact. I normally use it for dew heater control and previously for focuser control, but unfortunately it looks like the software is Windows only. So I'd need another option for dew control.

Also it would be really nice if I could use my Avalon mount with INDI. Looking on the forum I think it may be possible, but need to do some further reading.

I do like KStars too. Its nice to have the planetarium functionality, including features like the DSS Overlay when exploring for targets. I also like the 'Whats Up Tonight' option.

Andy.

 

Great, glad you had a decent first light with the software...you will love it, far better than any windows software I have used, and getting better all the time, due to constant support..

I have the Pegasus ultimate power box and there is a driver now available for that in INdI...(indigo driver) although it has taken a while, but seems to work well..have a word with Jasem (AKA Knro on the INdI forum ) and he may well write a driver for the Hitecastro unit, although may be a while as I guess he is very busy.

[kens]

7 hours ago, Andyb90 said:

Also it would be really nice if I could use my Avalon mount with INDI. Looking on the forum I think it may be possible, but need to do some further reading.

The Avalon driver is under development. You would need to build the driver from source. You can find a link to the source code on the Indi forum at https://indilib.org/forum/mounts/2411-avalon-mzero-stargo-with-lx200-protocol.html You also need to edit the drivers.xml file

I use it all the time now with no issues and any problems I can help out.

[Andyb90]

38 minutes ago, kens said:

The Avalon driver is under development. You would need to build the driver from source. You can find a link to the source code on the Indi forum at https://indilib.org/forum/mounts/2411-avalon-mzero-stargo-with-lx200-protocol.html You also need to edit the drivers.xml file

I use it all the time now with no issues and any problems I can help out.

That's great. I'm wondering if it's best to create a new thread on the INDI forum Mount's section as I have some beginner questions about building and installing the driver. Rather than post into the above thread.

Andy.

[kens]

Should be ok to post in that thread unless you have more general questions about Indi. 

[Andyb90]

40 minutes ago, kens said:

Should be ok to post in that thread unless you have more general questions about Indi. 

I posted a new thread as I have some beginner questions about compiling and installing the driver. This one:

https://www.indilib.org/forum/mounts/4193-avalon-driver-setup.html

Andy.

[giorgio_ne]

In my opinion, the best way to use and appreciate INDI is through an OTA mounted Raspberry Pi and a remote laptop or desktop running a separate instance of KStars.

Although my Pi has the full INDI/Kstars combination installed on it, I use it only to manage the hardware connected to it and to guide the mount.

I run any INDI client software on my laptop or desktop. I don’t bother using VNC or any other Remote Desktop software for two reasons: performance first. Second, KStars is available also for Windows and Mac OS and only needs to be configured with the network name or IP address of the Pi sitting on the telescope to manage it as if it was directly connected to it.

Astroberry or Stellarmate OSs can be easily burned on an SD card and deployed on a raspberry Pi in a few minutes!

Kstars for Windows, Linux or Mac OS can be downloaded from its website.

Last but not least INDI has a Skysafari plugin that allows me to use Skysafari on my iPad to select targets and slew the mount. As I do so, it’s amazing to see the scope position being updated in real-time on KStars on the laptop.

In the attached image is one of my setups: FSQ-106, EM-200, Qsi 690 wsg8, Lodestar X2, SestoSenso focuser, Raspberry Pi 3b+

The Rigrunner power socket also has two USB ports delivering 5amps each. I use one of them to power the Pi. I do not need to use a powered USB hub!

Edited December 1, 2018 by giorgio_ne
Attached image

[LightBucket]

1 hour ago, giorgio_ne said:

In my opinion, the best way to use and appreciate INDI is through an OTA mounted Raspberry Pi and a remote laptop or desktop running a separate instance of KStars.

Although my Pi has the full INDI/Kstars combination installed on it, I use it only to manage the hardware connected to it and to guide the mount.

I run any INDI client software on my laptop or desktop. I don’t bother using VNC or any other Remote Desktop software for two reasons: performance first. Second, KStars is available also for Windows and Mac OS and only needs to be configured with the network name or IP address of the Pi sitting on the telescope to manage it as if it was directly connected to it.

Astroberry or Stellarmate OSs can be easily burned on an SD card and deployed on a raspberry Pi in a few minutes!

Kstars for Windows, Linux or Mac OS can be downloaded from its website.

Last but not least INDI has a Skysafari plugin that allows me to use Skysafari on my iPad to select targets and slew the mount. As I do so, it’s amazing to see the scope position being updated in real-time on KStars on the laptop.

In the attached image is one of my setups: FSQ-106, EM-200, Qsi 690 wsg8, Lodestar X2, SestoSenso focuser, Raspberry Pi 3b+

The Rigrunner power socket also has two USB ports delivering 5amps each. I use one of them to power the Pi. I do not need to use a powered USB hub!

Totally agree with all of the above, and exactly how I run my set up..  

[sloz1664]

Great set-up Giorgio. I would love to move to say an Ubuntu controlled system. could this extend to a twin scope system. driving two ccd cameras, filterwheels, autofocusers and one mount.

Steve

[stash_old]

1 hour ago, giorgio_ne said:

Last but not least INDI has a Skysafari plugin that allows me to use Skysafari on my iPad to select targets and slew the mount. As I do so, it’s amazing to see the scope position being updated in real-time on KStars on the laptop.

Why use Skysafari when Kstars does all that Skysafari does - not a criticism but a question because I have been asking why Ekos is not totally separate (you can't run Ekos without Kstars on any O/S) especially as Indilib allows CDC and other planetarium software to connect/control.  Is it because your mount is mobile ?

Plus your picture doesn't show any power wires connecting to the PI - I understand you run from the Rigrunner but cant see the cables ?

Doesn't effect me as I run a DSLR but others have said that the RPI (even the RPI3 which split USB/Ethernet Bus) is just not faster enough with CCD's (frame rate) hence many have gone Rock64,Intel Stick etc . What's your experience ?

I have never found a problem with RealVNC server on the RPI's only the network connection ,especially the Wifi weakness so what do you mean by "Performance" ? Again not criticism just interested ?

It does make me laugh that your great set up relies on a £34 device - totally out of proportion to the rest of the kit - but it works LOL

[stash_old]

5 minutes ago, sloz1664 said:

Great set-up Giorgio. I would love to move to say an Ubuntu controlled system. could this extend to a twin scope system. driving two ccd cameras, filterwheels, autofocusers and one mount.

Steve

Simple answer is yes but not ,i would suggest ,on a single RPI (but you can run multiple RPI's or other SBC thats Indi inbuilt speciality) especially if you want to image at the same time. Go over to the Indi forum there are users who run that sort of set up - they dont bite ?

[sloz1664]

2 minutes ago, stash_old said:

Simple answer is yes but not ,i would suggest ,on a single RPI (but you can run multiple RPI's or other SBC thats Indi inbuilt speciality) especially if you want to image at the same time. Go over to the Indi forum there are users who run that sort of set up - they dont bite ?

? ? ?

[LightBucket]

1 hour ago, stash_old said:

Why use Skysafari when Kstars does all that Skysafari does - not a criticism but a question because I have been asking why Ekos is not totally separate (you can't run Ekos without Kstars on any O/S) especially as Indilib allows CDC and other planetarium software to connect/control.  Is it because your mount is mobile ?

Plus your picture doesn't show any power wires connecting to the PI - I understand you run from the Rigrunner but cant see the cables ?

Doesn't effect me as I run a DSLR but others have said that the RPI (even the RPI3 which split USB/Ethernet Bus) is just not faster enough with CCD's (frame rate) hence many have gone Rock64,Intel Stick etc . What's your experience ?

I have never found a problem with RealVNC server on the RPI's only the network connection ,especially the Wifi weakness so what do you mean by "Performance" ? Again not criticism just interested ?

It does make me laugh that your great set up relies on a £34 device - totally out of proportion to the rest of the kit - but it works LOL

Using skysafari, is really useful if you need to go out to the mount, and slew to an object as you can see in real time...

The rpi is more than fast enough when used this way as it’s onlt a server, there is no power Hungary software running on it, that’s all done form ones laptop or PC indoors..

I found that the noVNC is superb, I have never had a problem with connection or with any dropouts, it just works..never tried RealVNC though..

[stash_old]

3 hours ago, LightBucket said:

Using skysafari, is really useful if you need to go out to the mount, and slew to an object as you can see in real time...

The rpi is more than fast enough when used this way as it’s onlt a server, there is no power Hungary software running on it, that’s all done form ones laptop or PC indoors..

I found that the noVNC is superb, I have never had a problem with connection or with any dropouts, it just works..never tried RealVNC though..

Hi @light bucket I was really asking why giorgio was using Skysafari and not just Kstars - i was expecting the same answer from him - just being nosey ?

I too use Skysafari ,on my really old Sony xperia phone ,when using my Indi Grab and Go set up but very rarely when back at base - just use Kstars/RealVNC from nice warm man cave !!!! Never had performance issues,hence the question, except networking which had nothing to do with Remote working it was RPI3 (not 3+) weak 2.4ghz signal which I cured. Even have used remote desktop when using RPI Zero W using std Raspbian with Indiserver installed to control DSLR/mount with no performance problems as I disconnect after starting my scripts the Realvnc goes to sleep - yes I could use SH or Web service but too lazy to set up  ?

However the CCD performance does intrigue me as some say its too slow while others seem to be quite happy (or dont say anything) - hence that question using his lovely QSI CCD (drooling ? ) CCD - wondered what the performance was like on a RPI3/USB2 set up. 

:-) 

[LightBucket]

1 hour ago, stash_old said:

Hi @light bucket I was really asking why giorgio was using Skysafari and not just Kstars - i was expecting the same answer from him - just being nosey ?

I too use Skysafari ,on my really old Sony xperia phone ,when using my Indi Grab and Go set up but very rarely when back at base - just use Kstars/RealVNC from nice warm man cave !!!! Never had performance issues,hence the question, except networking which had nothing to do with Remote working it was RPI3 (not 3+) weak 2.4ghz signal which I cured. Even have used remote desktop when using RPI Zero W using std Raspbian with Indiserver installed to control DSLR/mount with no performance problems as I disconnect after starting my scripts the Realvnc goes to sleep - yes I could use SH or Web service but too lazy to set up  ?

However the CCD performance does intrigue me as some say its too slow while others seem to be quite happy (or dont say anything) - hence that question using his lovely QSI CCD (drooling ? ) CCD - wondered what the performance was like on a RPI3/USB2 set up. 

?

Yes, sorry to but in...

Well i use two Starlight Xpress Cameras, My OSC is an SXVR M25c which runs really well, and my mono is an SX H18 which has the popular mono KAF 8300 sensor and agin it runs really well, plus a lodestar autoguider..

They are the only Cameras I Have used on my rpi3b..

Also just been trying out using teamviewer host on the rpi but find noVNC much better, what is the difference between RealVNC and noVNC...??

Edited December 1, 2018 by LightBucket

[stash_old]

11 minutes ago, LightBucket said:

Yes, sorry to but in...

no problem ?

12 minutes ago, LightBucket said:

Also just been trying out using teamviewer host on the rpi but find noVNC much better, what is the difference between RealVNC and noVNC...??

As RPI has a deal wih Realvnc you are allowed to install realvnc on any o/s on RPI (as far as I know) so I use it on Stretch and Ubuntu mate with no problems.

You cant reinvent the wheel so really the only difference is Realvnc Server runs as a "service" on RPI while if i read Novnc the latter is just a Client and connects to any remote desktop server as it runs I guess like TeamViewer via Web sockets and HTML. So where I need to use any VNC client (realvnc,tightvnc etc) I have to install it first on the client end - NoVNC just uses existing HTML Web Browser saves installing a client.

Realvnc has been around 20yrs but of late have started to charge for none cloud connecing software (Clients are free) excep RPI which as I say have a deal on the server lic.

RealVnc is very fast (haven't run against with Novnc) and you can transfer file between client and server through its own protocol - sometimes useful.

29 minutes ago, LightBucket said:

Well i use two Starlight Xpress Cameras, My OSC is an SXVR M25c which runs really well, and my mono is an SX H18 which has the popular mono KAF 8300 sensor and agin it runs really well, plus a lodestar autoguider..

What sort of Frame rates are you getting on your CCD's and what are you storing you frames on (local or remote)

 

Sorry Andyb90 for hyjacking thread but it is connected to "requirements" - let us know if you object

[giorgio_ne]

7 hours ago, stash_old said:

Why use Skysafari when Kstars does all that Skysafari does - not a criticism but a question because I have been asking why Ekos is not totally separate (you can't run Ekos without Kstars on any O/S) especially as Indilib allows CDC and other planetarium software to connect/control.  Is it because your mount is mobile ?

I don’t use Skysafari as my main planetarium software over KStars, but it is really handy in some situations when I’m near to the scope and I quickly need to sass out what targets are within my visible horizon.

7 hours ago, stash_old said:

Plus your picture doesn't show any power wires connecting to the PI - I understand you run from the Rigrunner but cant see the cables ?

I’m a bit of a cable freak... All my usb cables are good quality Lindy cables specifically sized for a particular configuration (I have other scopes, CCD, DSLRs and focusers). They directly attach to the Pi. Power cables are also appropriately sized. I use plenty of Velcro cable ties to minimise cable drag. I’m trying to get rid of the mount usb to serial cable by using a Bluetooth to serial adapter but I still haven’t figured out the correct cabling and serial protocols for my mount...

7 hours ago, stash_old said:

Doesn't effect me as I run a DSLR but others have said that the RPI (even the RPI3 which split USB/Ethernet Bus) is just not faster enough with CCD's (frame rate) hence many have gone Rock64,Intel Stick etc . What's your experience ?

I don’t do planetary, solar or lucky imaging with this setup. For solar imaging I use a different configuration based on a Win10 Intel NUC. Focusing might take longer but I’m not bothered.

7 hours ago, stash_old said:

I have never found a problem with RealVNC server on the RPI's only the network connection ,especially the Wifi weakness so what do you mean by "Performance" ? Again not criticism just interested ?

I use WiFi plus, in my opinion KStars feels a bit sluggish when running on the Pi. Plate solving is also much faster when delegated to the instance of KStars on the laptop (I downloaded the appropriate index files).

7 hours ago, stash_old said:

It does make me laugh that your great set up relies on a £34 device - totally out of proportion to the rest of the kit - but it works LOL

That’s so true, but I also think the client/server architecture of INDI is so much more efficient if compared to ASCOM and the whims of MS Windows. Once the INDI drivers are properly configured, the Raspberry Pi behaves reliably just like an appliance. I took particular care in choosing an aluminium Pi case and attaching a vixen mini dovetail to it.

[LightBucket]

1 hour ago, stash_old said:

no problem ?

As RPI has a deal wih Realvnc you are allowed to install realvnc on any o/s on RPI (as far as I know) so I use it on Stretch and Ubuntu mate with no problems.

You cant reinvent the wheel so really the only difference is Realvnc Server runs as a "service" on RPI while if i read Novnc the latter is just a Client and connects to any remote desktop server as it runs I guess like TeamViewer via Web sockets and HTML. So where I need to use any VNC client (realvnc,tightvnc etc) I have to install it first on the client end - NoVNC just uses existing HTML Web Browser saves installing a client.

Realvnc has been around 20yrs but of late have started to charge for none cloud connecing software (Clients are free) excep RPI which as I say have a deal on the server lic.

RealVnc is very fast (haven't run against with Novnc) and you can transfer file between client and server through its own protocol - sometimes useful.

What sort of Frame rates are you getting on your CCD's and what are you storing you frames on (local or remote)

 

Sorry Andyb90 for hyjacking thread but it is connected to "requirements" - let us know if you object

 

Well as for frame rates, my cameras are for long exposures, so frame rates don’t come into it...I don’t use it for planetary imaging on,y deep sky...

noVNC runs from the web browser..! So would RealVNC be faster..??

I store images on my client machine..

[stash_old]

17 hours ago, giorgio_ne said:

I use WiFi plus, in my opinion KStars feels a bit sluggish when running on the Pi. Plate solving is also much faster when delegated to the instance of KStars on the laptop (I downloaded the appropriate index files).

Sorry I must have misunderstood I thought you were saying Realvnc was sluggish not that running Kstars/Platesolving is slowing the RPI - totally agree I too do Kstars/Platesolving on another device for that reason.

Cables - that lovely subject LOL ?

[stash_old]

17 hours ago, LightBucket said:

noVNC runs from the web browser..! So would RealVNC be faster..??

To be honest cant say as I haven't used NoVnc. But really we are talking about the client end (The Viewer) and I would expect Realvnc viewer to work well with Realvnc server but who knows. ?

I ask about frame rates as on my other set up I do EAA which depends on either very fast scopes ( < F4 ) and/or very high frame rates for fast real time stacking.

 

[RonKramer]

I just switched to this.  I put linux on my nuc and desktop. There are pains...  my IP cameras would not work from linux nor my TV feed. After trying info and kstars on NUC then dekstop - I have found the best solution.  A PI computer 38.00 and a 10.00 case.  I added the stellarmate linux OS. (49) and well worth it.  The PI had all my gear plugged into it. 
nexdome
snapcap
Foxlynx 1 and 2 focusers
Pyxis rotator
1600 camera
SX lodestar camera
ASI EFW
AP mount
Cloudwatcher
I'm probably missing something. I plugged all this into the PI.  I plug the PI into my lan on my mesh router 300 ft away from my house. 
I went back to running windows in the house on the desktop.  (dispite LOVING the dark scheme on Linux = (    to many issues).
I run Kstars/Ekos on my PC windows10.  I can teamviewer into the PI to tweak it if needed. (updates). 
I am running all the PROCESSING intensive programs on my win10 desktop.  (this eliminated the crashing from a 1gb PI).
PI does all the IO for the devices.  And it's realtime.  ALL my my devices were easily covered/included in the INDI driver package install.
I have a few minor issues yet, but I'm still in my first week of this huge transition from SGP and the 8 other apps that were required!

MY only complaint - the  UI  of EKOS need work, but Jasem has shown a lot of interest in suggestions. The first issue I had he fixed over night!

this has been a awesome change over... there is a learning curve but the benifets will be worth it. 


 

[RonKramer]

On 02/12/2018 at 06:45, stash_old said:

Sorry I must have misunderstood I thought you were saying Realvnc was sluggish not that running Kstars/Platesolving is slowing the RPI - totally agree I too do Kstars/Platesolving on another device for that reason.

Cables - that lovely subject LOL ?

YES the PI lags - so the solution for me was to run on windows - and use the PI only for a webserver.  NO LAG -fewer crashes. My PC in the house does all the work... the PI is free to do the IO.  I did all the other iterations... (kstars on my dome Nuc (port problems) Kstars on the PI (lag problems) so run everything on windows and connect to the PI's webserver.  CLEAN - AND FAST. 

 

[stash_old]

17 hours ago, RonKramer said:

and use the PI only for a webserver

Sorry dont understand that statement - do you mean just run Indiserver (this is NOT a web server) on RPI(s) acting as the Device server and Kstars/Ekos "client" on  Windows- plus use a browser to start Indiserver on the PI ?

And how much in terms of cost is your "in house PC" compared to the PI - you buy a Mini or you buy a Ferrari they are both cars but that's were the comparison ends.

As you use the Indilib forum I think many would have already pointed out they use higher powered/cost PI equivalents which work far better with little or no lag - plus less cables(off mount) - normally only power  if they opt for Wireless(some dont for valid reasons!).

In your situation you didn't need Stellarmate at all just the PI (even just a Non GUI headless server - e.g. Ubuntu 18.04 or even Stretch server) and basic Indilib. This gives the best PI performance as no "GUI luggage". No need even for a Web Browser really but except it maybe easier for you - "Cleaner" as you say.

Good luck with your set up and Clear Skies ?