Recently Browsing 0 members
No registered users viewing this page.
Been getting help from old stash, setting up raspberry pi4 4gb for astronomy,, he had the patience of a Saint,
We got there in the end, I used the astroberry operating system put together by radek,, Linux just isn't my thing lol,
The astroberry system has software such as k stars/ekos, cdc/ccdciel, oacapture, hnsky an few more,, I tried combinations of the software and found it wasn't what I wanted,, the concept of remote desktop, from a small,, single board computer did interest me for a portable grab n go kit,, I could sit in my car and keep warm and control my kit via WiFi on a laptop
Came across the lattepanda,, not much bigger than the raspberry pi 4 4gb, but it's operating system is windows 10.
I could have went for the flagship Alpha model,, but the idea was to try the entry level panda and see what could be achieved with it, I bought mine with Windows 10 installed from the pi hut,, £118 and was delivered within two days to Scotland,,
The WiFi ariel is not fitted to the board,, but just a push in fit,, not easy when you have hands like shovels.
Power was supplied via a phone charger b type plug, it takes full size hdmi cable, and I fitted a Bluetooth dingle to use mini keyboard /touch pad to set it up.
This was very easy to do, soon on to downloading Software I wanted to use, CdC, went in no problem, Ascom didn't,, I net frame work was missing,, on the panda windows,, type in,,, enable windows features,, then when next screen appears, tick,, framework box and continue,, windows will search and update the system,, Ascom installed fine after that.
Eqmod installed no problem, installed hitecastro dc focuser, easy again,, backyard eos Pro and sharpcap Pro installed OK.
This all went pretty easily,, testing,,
Got it working my heq5, focuser,, initially tested backyard eos and my Canon 600d,, set up focus control ect.
Installed tight vnc and yet Again easily done,, I now had it connected remotely to my laptop via my smartphone hot-spot.
Absolutely loving it,, so much easier than setting up the raspberry pi.
Next up was testing my zwo asi178 mc on sharpcap Pro,, camera not recognised,, soon pinpointed that the zwo driver was not installed,, downloaded this and the Ascom driver just to be shure I had it,, I also got the asi studio suggested the other day.
Tried this out camera connected no problem and worked on remote desktop
Sharpcap recognised the camera as well,, working great on remote desktop
I installed tight vnc on to my linx 10" Windows tablet,, put in the panda IP address,, I now had a TV plugged into the panda at the mount, a Toshiba laptop and a tablet on remote desktop and both had control over the panda,, absolutely brilliant,, the vnc is also available on android and other os,
This would be great for outreach.
I've only installed software that I want to use,, internal memory I still have 12 gb free.
My next plan is to incorporate this system to my azgti,, problem I found having set up the panda to my laptop via my phone hot-spot,, I could not connect to the azgti mount, it was either,, WiFi or hot spot on the phone,, I tried this using the raspberry pi..
Had a think about it and, I believe the easy solution to my problem is fitting the azgti cable,, I've ordered from FLO, attach this to the panda,, install azgti Ascom driver, then I should be able to control mount with ccdc,,.. Will find out if I'm right in a few days,, should then have a portable kit I can control via remote desktop in my warm car in the winter.
By Del Russel
Thanks for letting me share this site. Right! Neebie. I now have the az gti and for the life of me I can't work out how to communicate with my windows 10 desktop and the mount.
Do I need extra cables to attach the two and if so which ones? Be grateful for any help at all....so frustrating. Shoild add I'm not very computer literate...thanks for understanding...del
I'm making a tentative foray into guided AP, and have got a ToupTek GCMOS01200KPB Colour guide cam from FLO (to use on an ST80 I picked up from the forums).
I can't get PHD2 to recognise the camera, in fact I can't even get the ToupTek software to see the camera. I wonder whether anyone else with experience of this camera, or Windows 10 might be able to help?
I managed to overcome the initial problem of Windows recognising it as a 'USB2.0 Camera' even thought I had 'installed' the DirectShow driver that came with the camera. It seems that running the driver installation program didn't actually install the driver, it just put the necessary files on my hard disk. I then had to do the windows thing of selecting 'update driver', 'have disk', etc. to point at the ToupCam.inf file that had been copied onto my laptop. After this, when I plug in the camera it correctly recognises it in Device Manager correctly as a GCMOS01200KPB camera (now under 'Imaging Devices' in device manager rather than 'Cameras'). The red LED on the camera flashes when it is connected.
This took me about a week to work out, so I was feeling quite pleased with myself - until I tried running any camera software. Running the ToupSky software showed 'no device' under cameras. I installed the ASCOM drivers, and when I run the ASCOM diagnostics it appears to see the driver but cannot connect to the camera.
I'm stumped. Can anyone point me in the right direction?