StevieDvd

If that has a 3/8" thread then yes. If you are referring to an EQ5 tripod then you would need an adapter.

19 hours ago, uk_friendly_fire said:

What version of Windows are you using to connect to your target PC. I think you can only do it with the Pro version.

If that's what you have just Google on Utube as I've seen an informative one in the past on setting up the credentials 

If the target is a Windows machine it needs Windows Pro (with remote server running). The connecting PC does not need to the Pro version

3 hours ago, Saganite said:

This Lyra Optic 102mm f11 was collected a week ago but had first light last night.  

A telescope for all ages:

The actual scope you have, but now in hands of a more skilled user. 🙂

Have you left the ASIAir+ dc power  ports for the dew straps at full?   If you set them as Dew power they have a variable setting to reduce the heat/power consumption.

The ASIAir will continue to run if you disconnect your phone/tablet so I expect the power ports would still run even if you have no Wi-Fi.  Though exceeding current draw, albeit briefly can have odd effects. Whatever you have connected there is only 6A to share between all power/usb ports.

1 hour ago, Grumman said:

Hello all, I have a SkyWatcher EQ3-2 mount and I am using the handset with the relay firmware to connect to my PC via an RS232 to USB cable and control the mount. 
I have seen online that there is a EQ direct USB cable.

1. Does this replace the handset and connects straight from PC to control module?

2. Does it work with SkyWatcher EQ3-2 controller?

 

Regards,

Thanasis 

Yes it replaces the handset and needs a USB driver on your PC and the appropriate Astro software (Ascom etc). The handset needs a different type of cable to connect it (it's there for firmware updates & PC direct mode).

26 minutes ago, Geoff Lister said:

Many thanks. But is this information made available on the ZWO or Dwarflab web sites, or in the advertising info on the web sites of their major UK retail outlets? The less-inquisitive are likely to have placed their £500+ order, and probably be unboxing, before locating and downloading the app.

Geoff

To be frank I have not checked 🙄

Dwarf app requires Android 5.0 and up,  and Seestar requires Android 8.0 and up.

The info is on the app information on Play Store if you click on the arrow next to the 'About this app' section. 

It's not just down rather it's suspended. The person behind has been asked to cease using certain software and is looking for an alternate to do the same service.

As a user of the same software behind astrocooker I was surprised it was actually allowed to do what it did. Your best bet for a similar processing (free) is to have a look at Siril. The developer behind astrocooker has said he will try making a similar web system based on Siril (if that's allowed),

In the early 90s IBM and Microsoft were doing a joint development of an operating system called OS/2 Warp.  There were differences in opinion on the direction of the OS and the user base/equipment.  I was told by an IBM rep that they had wanted to restrict the drivers to approved ones as the hardware would affect the reliability of the OS. Microsoft wanted it left open so more vendors would provide the hardware and peripherals and market prices would keep the costs down.

We all know that Apple had the IBM idea for Macs, hence the reputation for reliability as the OS was tested against a much more limited set of hardware than WIndows allows. I guess that ZWO have the same opinion, in that the variety of hardware that can connect to an ASIAir would lead to increased support issues, that could be down to other manufacturers hardware and not the ASIAir itself.

I had an OS/2 Warp system running at work (freebie and free support) as we had ties to IBM and Microsoft.  It was a stable system but onerous to setup new hardware and not masse audience friendly. In the end Microsoft took the work they had done and used it for Windows NT.

Managed to take advantage of clear skies to grab a solar image or two with the Seestar

Straight from the Seestar as a video and stacked in ASIVideoStack on the left and post-processed on the right.

Not too shabby for a quick 2 minute video.

The Seestar only saves to the main unit if you select RAW when shooting. I found that out taking solar video and only had an mp4 on my iphone. As most stacking software needs avi or ser files it's a pain getting it converted. I asked ZWO if they could allow us to choose the format and that's when they told me to select RAW to save the avi to the main unit.

Can't help with the jpeg format.

Are you connecting the Android phone to the same hotspot as the asiair?

I'm not sure exactly why you think the ASIAir does not save files for post processing, as it's quite popular with astro imagers like myself.  Perhaps it's down to the EAA definitions on CN.

Astro imaging sessions on the ASIAir can be viewed as they stack,  sort of EAA in my opinion. The fits files (lights) are saved to the ASIAir for further processing and via the planning section you can do the darks and flats the same way and download them all for post processing.

There is an EAF focus motor for the bigger Celestron scopes which may fit the Nexstar but you'd need too check the dimensions of the bracket and the fitting holes.

Was it the selection of the files in the gaia process selector that resolved it?

I've added a couple of images in case of anyone doing a search later. 

I'm no expert but this is my setup

1. Note location of the downloaded xpsd files
2. Open the Gaia process (find under <All processes>)

1. Click on the wrench

1. Select Data Release for the files you downloaded
2. Use the Select button to find the files
3. Once all selected close the process
4. Before using make sure your image has been solved (I use script/image analysis/image solver)
5. Then use the SPCC

HTH

Steve

Hmm, it seems to show a focal length of 335mm so possible a smart telescope.

14 hours ago, PeterC65 said:

Well ...

After uninstalling and re-installing various Prolific drivers, I'm now back on v5.2.6.0, which is the latest version and the one I've been using all along, and SynScan Pro is connecting successfully to the mount. I have no idea what I've done to make this work!

 

I believe you have removed the incorrectly selected driver version and loaded a working one (perhaps with built in 'pipe cleaner').😉

In any case glad to hear it works now.

Reading your explanation of the pipe cleaning I think your conclusion that it is resetting (cleaning) is possibly wrong.  In software terms it's more likely that ASCOM starts or loads a process when it searches for a com port and then SynScan app works as that process is already running. If you start SynScan first then it does not see the process or start it itself.

This could be due to the way you start or installed software, such as one has admin rights and the other does not.

Or after a quick google for your issue I found this old thread on SGL which may be worth a look.  It appeared that the driver linked to the serial port was using a previous installed version. When fixed SynScan did open the port on start up.

I would not expect to have both the mount usb and handset connected and have them both working seamlessly together. Just one or the other is probably best practise. 

The handset and the Synscan app will have an option to set whether the mount is being used in EQ or AZ mode 

The drivers are obtainable from https://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 by checking the version f the chip - there is a program in that page you can download to check yours. Hopefully a later driver will support both your eqmod cable chip and the one in the mount.

Prolific chips tend to change the com port numbers rather than re-using the same one previously assigned to that serial cable. So are you trying all this with the correct com port for the cable being used?  You need to have a different baud rate and make sure the com port in ascom is correct for the serial connection being used, they are not always the same.

Not used on that specific mount but have used the USB port on other Skywatcher mounts.  Yes, they are a built in replacement for the handset and allow usage as per the manual you have quoted.

The usual suspect is the driver for the chipset used by Skywatcher missing from your PC. It's likely a Prolific one, whereas the USB serial lead connecting via the handset is FTDI.

Plug a USB printer type cable into the mount and PC then switch on and see what appears in the devices manager and if a com port number is allocated. Or if the device is unassigned and needs the driver to be installed. The Skywatcher page for your mount should tell you which driver is needed.

It's a little tricky using the FLO pictures but it appears to show that the blue is not connected on one end. So perhaps that's correct for your cable too.

But your pictures seem to show the yellow wire is possibly loose on one connector.

If you have a multi-meter with continuity setting you can check each coloured wire is making a connection each end. You'd need a small probe to touch each of the gold pins in the connectors.

You can use a makeshift tester with a torch, some wire, a peg and some tape.  There are plenty of YouTube videos to show this rather than me do a text explanation here.

If the yellow wire is not making a good connection you can fix it using the method described above using a jewellers size screwdriver.

HTH

Steve

There has been a release of the Dwarf app and a firmware update today, a bit piecemeal as not everyone was seeing the updates on Google Play and the Apple Appstore - based on comments on Facebook.

Android Version is now V2.0.0 B70

iOS is now V2.0.0 B18

Firmware version V2.0.06

iOS curves tool is still not as functional as the Android version, and in my opinion these updates are probably still Beta versions based on the version numbers.

As I'm not beta testing these now they have been released I can say that the curves on Android seems functional, except for the save option.  On iOS it still needs work on the curves. With little chance to test 'astro mode' due to lack of clear skies I can't say if the curves issues are useable to an acceptable degree on either OS. I raised the curves issue for iOS back in November, together with a host of inconsistencies between the user interfaces of Android & iOS (most of which I am pleased to see have been fixed).

But if you've been waiting for the updated catalogue of objects and the option to do 1x1 binning (4k) versus the 2x2 (2k)  and a better UI then you can update without worrying about buggy beta releases.

3 hours ago, nicoscy said:

Station mode works in 2.4 only. First switch to 2.4 and then you can switch on station mode and connect to your home network.

No. It works 2.4 & 5 on the Seestar. The Asiair is 2.4 only.

There are several of us on SGL using it on 5GHz

44 minutes ago, trailer said:

I’m pretty sure Station mode only works on the 2.4G frequency.

My initial setup was in 5GHz when I activated Station mode, I later reset by switching to 2.4GHz before switching back.  Have you seen anything suggesting it only works in 2.4GHz? That would mean it switches frequency automatically when using Station mode.