Search the Community
Showing results for tags 'windows 7'.
Found 3 results
Hi am posting this in case it helps anyone who has suffered the same problem as myself. In a nutshell: Own a Skywatcher Gti mount for some time now and used with some success, also purchased some time ago Skysafari and wanted to use both, with a problem much reported on the web and so much information out there that it can get a bit confusing and certainly in my case frustrating, after all just want stuff to work! After much experimenting and help from other postings this is what happens when you fire up the Gti. The mount generates its own wireless network and becomes the gateway, its IP address is always 192.168.4.1 you see this when making a connection with the Synscan app/program, its very similar to a normal router that serves you the Internet. Any device that then connects to this network then gets an assigned address one up from this, i.e. 192.168.4.2, .3, etc. However if you run the Safari app and go in to settings you will find it has also been allocated an address which is one up from the device you are using. In my case my Ipad was connected to the wireless network and had been given the address of 192.168.4.3. but when I checked the IP address in the settings page of SkySafari it was 192.168.4.4 ! If you accept this you get the error that the app cannot join the wireless network check your settings etc. If you now manually change that address to the same as the device running the Synscan app in my case .2 it should connect and work. However there is a caveat to this, I tried using an Iphone 4 and an old Ipad and they would not work together no matter what. I got the other error message that I had joined the network but the mount did not recognise the device type I had selected (Skywatcher Synscan Alt Az GoTo) and no amount of changing things would solve it. To get around this I used my trusty Win 7 laptop to run the Synscan program and things worked perfectly so it can be done don't give up! Sorry this is so long but I hope it helps someone out there. So to round off when you fire up the mount it becomes address no 1, any physical device gets the next address 2, any software running on the that device gets the next address 3. When you fire up SkySafari it must have the same address as the one that the SynScan app has got and this can e changed in SkySafari settings. None of this makes any sense to me as I thought software couldn't act in that way but there you are. I hope I have got this right feel free to contact me if things don't work Regards Bill
Hi Just tried out my new (to me) Canon 6D Mk1 at Galloway Star Party and discovered that my Windows 7, 64bit laptop doesn't see the camera when I try to connect it by USB, so I can't control it with BackyardEOS. I've checked the device manager and it just doesn't come up when connected and switched on plus I've tried different USB ports. However, I don't have the same problem when I do the same with my Canon EOS 450D using the same cable with the same laptop. Am I missing something important here? Pretty frustrating given it's the first time I've been out under a sky that good in a long time Thanks in advance, Tom
Hi All I have been using my 'best' laptop with Windows 8.1 to control an EQ5 Pro mount via a USB/Serial converter with a lead directly to the hand controller set to PC Direct Mode. On the same laptop I have installed PHD2 for guiding and BackyardEOS for image capture and a gampepad for ease of 'tweaking' the telescope pointing. I have also installed Cartes du Ciel (CdC) to find and slew to targets. This system has worked flawlessly (other than 'idiot induced' problems) for a number of months now. I was lucky enough to be given another, slightly older, laptop to use so I thought the 'best' laptop could stay in the office and the older laptop could now become the astro imaging laptop. As far as I can see, I have everything configured the same and, on first trials in daylight, everything seemed to be working OK. Could connect to the mount OK, control via gampad OK, PHD2 connected OK etc etc. First 'imaging in anger' night seemed to going well until I noticed that the star trails suddenly appeared to be streaked after successfully capturing a few previous images. PHD2 was still connected but the guide star was way off target (the little green square in PHD) and appeared to be drifting as I watched. CdC (the planetarium software I use) was still connected but the rectangle indicating the camera's field of view was also drifting off target. On looking at the EQMOD window I noticed that tracking was 'off'. "Another idiot induced problem?" I thought. Selected Sidereal Tracking in EQMOD and I heard the motors of the mount start 'whirring' again. Selected target in CdC and slewed the 'scope back to the target. Selected guide star again in PHD and guiding started OK (I could hear the motor 'tones' changing as they received correction signals from PHD. Back on track - so I thought! After a short while, the problem occurred again - Sidereal tracking was shown as being turned off in EQMOD. These are only differences between the successful setup and the rogue version; Working System 2.4ghz processor, Windows 8.1 Failing system 2.2ghz processor, Windows 7 Has anyone else had this problem? Any suggestions as to what could be causing this problem would be greatly appreciated. Thanks Richard