|
Post by davy on Feb 29, 2020 9:08:41 GMT
So weekend is here and a few hours spare. Now the basic rpi is set up I have to try the remote software.
This set up will be operating the skywatcher az gti,,,, I have the skywatcher star adventurer and can steal the wedge to use on the az gti. Question,,, will the az gti work from cdc or do I need to add stuff from indi
|
|
|
Post by oldstash on Feb 29, 2020 11:08:52 GMT
Hi Davy, Glad you are having fun - a second PI ? Get the first one working fully first IMO OK get you head around this. 1. Indi provides the Hardware drivers and this is controlled by a piece of normally hidden software called INDISERVER. 2. You as the user decide what your hardware profile is - i.e. what you want loaded and controlled by Indiserver. So for example ,Profile will contain Mount,Focuser and camera. The profile tells Indiserver what drivers to load - hence you can create many Profiles to suit your wims - or in your case the garage full of hardware. 3. Once the Indiserver is started using your profile (dont worry the how just yet) AND you have connected the hardware you have completed what is called the "SERVER" side . Hence the server in INDISERVER. The Hardware connection using your profile is controlled via many settings which are manipulated via Indi Control Settings (Indi Control GUI). So you tell Indiserver to connect to he harde, where the hardware is and and odds and ends such as Scope F/length / Aperture etc The other "side of the equation" from the Server is the Client which has to talk INDI to talk to the Indiserver - FYI these clients do not have to be on the same computer - thats the flexibilty part. So CDC , EKOS/Kstars are examples of clients. Sorry about the above but you need to get this in your mind set. So to answer your question "will AZ GTI work from CDC and do I need suff from Indi" you need to : 1. Set up the Indiserver profile - once only unless you are always changing ports. 2. Make sure your KIT is all connected to the PI. 3. Load CDC and set up an Indi connection via TELESCOPE drop down menu a. Firs select Indi from Telescope set up - Attached screen showing what it should look like b. Assuming (a) done - then connect to INDISERVER by using the GET button (Marked as B) to retrieve the Mount defined by Indiserver (e.g. Sw AZGTI or what ever its called) NOTE if running CDC on the same device as Indiserver then leave item (A) (marked on 2nd screen attached) alone thats fine. Also note you could also call the Indi Control Settings GUI from CDC by pressing button marked as (C) on attached screen print. IF NOTHING Happens then you have probably not "started" Indiserver OR its not on the same PC but for now I am assuming its all on he RPI 4. HINT - if you use Astroberry Web Browser approach you can define and start(and restart) Indiserver,define a profile etc via the side panel menu. I suggest you try and just get CDC working with the Telescope/Camera Simulator profile first!!!!!!!! The above are only hints I am not going to write a manual :-) Plus I most likely have forgotten loads - it looks and is a steep learning curve but then every new is o most people.
|
|
|
Post by davy on Feb 29, 2020 11:30:55 GMT
OK,, have a rough idea of what you mean. Can define a profile, say azgti mobile incorporating say a zwo camera. Then a second profile az gti mobile 2 incorporating a Canon dslr,
|
|
|
Post by davy on Feb 29, 2020 11:43:46 GMT
|
|
|
Post by oldstash on Feb 29, 2020 13:28:13 GMT
OK,, have a rough idea of what you mean. Can define a profile, say azgti mobile incorporating say a zwo camera. Then a second profile az gti mobile 2 incorporating a Canon dslr, Yes exactly and the Astroberry side panel lets you start which ever profile you want to use. The biggest problem Newbies run into is to remember to start INDISERVER AND connect to hardware first. NOTE - If you decide to use Kstars/Ekos instead of CDC/CCDCIEL I think the profiles were not stored in the same place(might have changed now) - so profile created by Ekos not shared with Astroberry and Visa Versa. IMO EKOS/Kstars tie up (like joined twins ) is a pain and a pity as Ekos bit quite good - but thats my opinion
|
|
|
Post by davy on Mar 14, 2020 12:07:26 GMT
back on the project again,,, wee time out lol looked at the link old stash sent and comes up blank,,went on vnc page and it looks like a paid bit of software,, not really wanting to fork out for something I may only get out and about with now and then given the weather. can somebody advise me on this,,,
so swapping over scopes from the sw explorer to the ed80 on the heq5 and will get the astroberry rigged up ready for next stage
|
|
|
Post by oldstash on Mar 14, 2020 16:52:17 GMT
back on the project again,,, wee time out lol looked at the link old stash sent and comes up blank,,went on vnc page and it looks like a paid bit of software,, not really wanting to fork out for something I may only get out and about with now and then given the weather. can somebody advise me on this,,, so swapping over scopes from the sw explorer to the ed80 on the heq5 and will get the astroberry rigged up ready for next stage Do you mean Realvnc link - if so its free as you get realvnc server for free with Raspbian on RPI3/4 no need to download and the viewer is free anyway they just like hiding that fact. Plus its only needed as a backup while you are learning - in he field you would use Browser NOVNC connection. Using NOVNC loaded via Astroberry still uses Realvnc server on the RPI just uses something called Websockets. Hope thats the bit you are refering too?
|
|
|
Post by davy on Mar 14, 2020 19:12:39 GMT
back on the project again,,, wee time out lol looked at the link old stash sent and comes up blank,,went on vnc page and it looks like a paid bit of software,, not really wanting to fork out for something I may only get out and about with now and then given the weather. can somebody advise me on this,,, so swapping over scopes from the sw explorer to the ed80 on the heq5 and will get the astroberry rigged up ready for next stage Do you mean Realvnc link - if so its free as you get realvnc server for free with Raspbian on RPI3/4 no need to download and the viewer is free anyway they just like hiding that fact. Plus its only needed as a backup while you are learning - in he field you would use Browser NOVNC connection. Using NOVNC loaded via Astroberry still uses Realvnc server on the RPI just uses something called Websockets. Hope thats the bit you are refering too? Yeah want to try and remote desktop,, so all is in raspberry,
|
|
|
Post by davy on Mar 14, 2020 19:16:44 GMT
Brain fart,, was the windows side on laptop,, So I need the software on Windows, ( 7..64 bit) π and how do I get it to link to Astroberry
|
|
|
Post by oldstash on Mar 15, 2020 12:02:13 GMT
to get the Realvnc viewer for Windows 7 ( i am typing this on a version before Win 7 but using Opera Browser) go to site from a browser on the Win 7 Laptop as the site will recognise what OS using are using. www.realvnc.com/en/connect/download/viewer/ or I have set up google drive share for the Windows 64 bit stand alone (i.e. doesn't install just check permissions and run !!!!!! ) drive.google.com/open?id=1t3I13xUfQeXmMm-tDJCvgrv9O4ZVPnq2 should work for Win 7 64bit. NOTE you will have to change the filename Extn from xxx to exe to get it to run. The file is only 7mb To connect to Astroberry:- 1. Via most Web browsers type ip address of the RPI - so if using HOTSPOT on RPI for example it is 10.42.0.1 if your RPI is connected via your Phone tethering system you will need the IP address given to the RPI by your Phone . Extract from Github Astroberry ============================ How to use it? It's as simple as this: Start your Raspberry Pi with the flashed microSD card. Connect to an Astroberry Wireless Hotspot (default password is astroberry) Point your browser to astroberry.local or Click Connect button to access Astroberry Server Connect to Astroberry desktop (default password is astroberry) Note 1: If you connect via Hotspot default IP_ADDRESS is 10.42.0.1, if you connect via wire or your home wireless network, IP_ADDRESS will be assigned by your router/access point. =============== 2. Via REALVNC viewer a. Start the viewer and type in the IP address of the RPI - e.g. if using HOTSPOT 10.42.0.1
|
|
|
Post by davy on Mar 15, 2020 13:28:57 GMT
Many thanks to old stash for coaching me through this,, his help and advice has been invaluable. So where am I now Well I have now downloaded the vnc to the laptop,, probiem I had was I thought I had to buy it,, Downloaded no probs,, had problem connecting to pc,, but follow old stash advice,,,, I am doing mine as a portable set up,, so I have connected my phone to laptop via my hotspot,, I found in vnc,, go to menu and click add new connection, typed in my laptop ip address and it brought up a connection in vnc,, double left mouse, and it connected me to my astroberry set up My set up, Astroberry,, USB Bluetooth mini keyboard with touch pad,,, 10in hdmi monitor. Now most will just need this to set up and configure the software at installation.. I'm using mine at mount at first,, and controlling from laptop in the car. Once I'm familiar,, will probably ditch the monitor,, being honest 10in is not bad,, anything smaller,,, forget it,, to small to keep your sanity As we say,, no video or pictures,, it didn't happen 10in monitor Laptop with mirror image
|
|
|
Post by davy on Mar 15, 2020 15:28:59 GMT
So back to Astroberry for dummies timeπ Kit moved over to the heq5 Raspberry connected to mount via hitec Astro eq cable,, And the,, telescope won't connect in cdc, Have remote desktop working OK on laptop. As far as I can tell,, this looks ok So what I can see is,, the software is on telescope simulator,, Drop down arrow does nothing I have tick box for load indi configuration ticked and made no difference Is the indi driver loaded into AstroBerry
|
|
|
Post by davy on Mar 15, 2020 16:30:54 GMT
As mount is on standby,, thought I would look at capture side,, So stuck the zwo asi178 and fired up the oacapture software. Working OK,, it's planetary software,, does what it says it does,, could do with more control settings but will work fine
|
|
|
Post by davy on Mar 15, 2020 17:01:59 GMT
So browsing through stuff,, looking to see what other software was available came across this one Astrodmx www.linux-astro-imaging.uk/linux/astronomy/linux-downloadsDoes usb3 zwo camera's, some Canon dslr,, 600d so I'm interested right away,, screen shot looked interesting,, worth a follow up for guys on mac as it says it will be adding mac at some stage
|
|
|
Post by davy on Mar 15, 2020 18:06:39 GMT
well apart from a record button ? duh,, must be a way to capture...
|
|
|
Post by oldstash on Mar 15, 2020 20:44:42 GMT
Jesus stop jumping from one bit of software to another - worse than Scottish ruby team (we beat this year for a change LOL) and I wont mention football!
Any how - the drop down menu does work but it shows only what Indiserver part has connected - I always do a "GET" first to make sure its found the driver. So if you have the "Telescope simulator connected" thats ALL it will show you in the drop down - daft really but they use the same mechanism for all devices and you can only connect to one mount at a time.
Also note that you have to start the driver from wihin Indi Control GUI first - remember Indiserver connects to the Hardware in your profile first then you connect everything else including CDC.
Astrodmx does work with my Canon 100d and yes you can take images (via DSLR anyway - only one I tested) - its under Control Exposures -"take DSLR photo" button - make sure you select correct dslr output - use RAW for "DSLR output" - once thats working then you can change to JPG if required. There is also a "Capture" button to take a series of images - depending on the camera. Key is to connect to camera via "connect" button and remember it cant be shared with Indi at the same time.
Astrodmx is a bit flaky and nobody seems to answer emails about questions - so good luck with that - guess its new !!!!!
|
|
|
Post by davy on Mar 15, 2020 22:41:02 GMT
Ooch you know me always pushing the boundaries,, keeps a mad scotsman sane. π. So obi one. Sort me out lol. Walk me through bit,, I've deffo missed a bit,, I thought the profile bit was for kstars. So I've made a boo boo on the profile bit,, Luv this,, thank god I'm bald already.
Aye, agree on the astrodmx software, could not find one utube video on it,, did look up the developer,, deffo a woman who knows her way around a computer. Software one to keep an eye on
|
|
|
Post by oldstash on Mar 16, 2020 12:53:25 GMT
:-)
The Profile is used by Indiserver to connect/talk to hardware and talk to other software - hence its called a server. The profile , and there can be many, contains all the info the Indi Hardware drivers and the Software client needs - so what hardware type,which port (e.g. like COM port on Windows), characteristics ,status etc. All this info is held in realtime database which Sofware ,like CDC, can access.
So if your profile AAA say:
1. Mount is EQMOD and is connected (does not mean its started) via port USB0 and is located at Cords XYZ
2. Main camera is Canon connected via USB1 and has details such as UM,pixel size,Resolution etc
3. Guide Camera is ZWO connected via USB2 and has various settings as Canon - there is a lot.
So to use profile AAA you must get INDISERVER to start with profile AAA and then tell Indiserver to "connect" to the hardware - this latter bit can be down by saying "start and connect on loaing Indiserver with Profile AAA.
Now this is he confusing bit (if you are no already going nuts - everyone does to start with :-) ) - How you start Indiserver is one of 3 main ways, they are :-
1. By using EKOS which is inbuilt into Kstars and using "Indisetings" available on he Kstars Menu - Ekos and Indisettings have ICONS on Kstars Menu - roll mouse over to see which is which or use the Kstars Menu's. Starting Ekos gives you the ability to define , edit,Select Profile, delete a profile and then it allows you to start/stop Indinserver with the profile currently selected. If you have said "auto connect/start" Indiserver will start and ry and connect to the hardware in your profile. If you didn't use "auto start" then you need to go into the Indi Settings via Ekos and tell Indiserver to "Connect" (Indiserver should be started by Ekos) to the hardware in your profile. Assuming everything is ok (is it ever) Kstars will then be able to use the Hardware to see and control slewing etc. Ekos will also provide tabs that allow capture,guilding,Platesolving etc - if connect fails of any device do not continue sort the problem and stop / start Ekos again ( it may say Indiserver already running sto and start new Indiserver" say Y. I wont confuse you now but there is a "Web Manager" which is not to be confused with Astroberry Side Menu panel - later :-)
2. Using Astroberry Side menu (only accessed via a Web Browser) - this allows you a simplified (IMHO) solution to create,delete,edit a profile(telescope Icon) defining the Hardware. Assuming you have got a profile Astroberry will allow you to "Start" (stop or restart) Indiserver using that profile via the Side menu (Telescope Icon). To add insult to injury you can use Astroberry profile to to start Indiserver with your profile and then load Kstars/Ekos you will just get a message "Indiserver already running start a new instance" answer N
3. Start Indiserver from what is called "command line" (same as DOS on Windows) - I am not going to expand on this at the moment - for advance use later maybe.
Once Indiserver is running correctly you can start doing some AP this is done again a number of ways I will limit to Kstars or CCDCIEL. You cant do both at the same time.
Now assuming you want CCDCIEL and CDC you MUST make sure Kstars IS NOT RUNNING. Then Start CDC and tell CDC to use Indi and tell it where Indiserver is running (it could be running on any other PC/RPI hence why you need to tell CDC where Indiserver is located). This is done by using IP addressing as per Internet - so 10.42.0.1 or 127.0.0.1 - latter used when CDC is running on the same PC as Indiserver. If all is ok CDC will connect and go "Green" - this indicates CDC is connected to the MOUNT ONLY as thats all it uses. Then use start CCDCIEL and use the device set up to create a CCDCIEL profile - reason you create another profile is that CCDCIEL will talk to INDI and ASCOM at the same time. The later only works if you are running CCDCIEL on a Windows machine - here you can talk to Indi and ASCOM - if CCDCIEL is being run on a RPI then it will be Indi ONLY (for now).
No matter where CCDCIEL is running it needs to know where Indiserver is and again its via the IP address - so again 127.0.0.1 is everything being run on RPI or 10.42.0.1 if running CCDCIEL on Windows and using Wifi Hotspot.
When using Indi most "client software" (e.g. CDC etc) uses a GET command to retrieve the Driver being used (and started/loaded) by Indiserver - so if your Profile (astroberry or Kstars) says EQMOD and its running/connected the "GET" command will show you a list of drivers for that device type - so in the case of Telescopes it will show you "EQMOD" (or telescope simulator) if thats was in your current profile. Obviously main camera's might show a list of more than one .
Hope that helps a "tad" - I did say its a steep learning curve :-) as all new things are
|
|
|
Post by davy on Mar 16, 2020 21:01:06 GMT
I did ask.. Going to need a bottle of vodka bto settle me down now,, and I don't drink. π¬ I'm going to get this working π©
|
|
|
Post by oldstash on Mar 17, 2020 23:58:12 GMT
If I get time and are in a better place at the weekend I might try and organise a Teamviewer session using my indoor RPI3b+ Astroberry to let me walk you thru some of the workflow if that is any good for you. Not really in the mood with "everything" going off at the moment.
|
|