887 replies to this topic

[Jerry Hubbell]

Hello, i'm an owner of a new iexos-100 and my previous tracker experience is with another budget friendly piece of work called star adventurer mini (wifi).

Now, i'm not going into detail here, since it requires it's own review video to cover all the issues i've had to deal with and still not produce any usable images, where mini has none of this.. but i've ended up where I'm trying to get the mount driven by wired connection over USB.

 

I have installed the ascom platform, the ascom drivers, tried with both 32bit and 64bit and cant find any information in the web about the error i'm getting.

Let us skip the POTH hub part etc, just connecting with the diagnostic tool also gets me to the same error. I will write the message out and insert an image. Writing it out so that in the future the searches would maybe lead to answers for others who suffer similar issue. I tested it with two diffrent windows 10 computers. Same error.

 

I'm hoping it's user error and someone can tell me where do I go wrong?

Since I can get the driver to talk to the mount over usb, i'm guessing the "serial" connection is also using the same usb? Since my iexos-100 came with totally wrong manual i had to find the one in homepage and this refers the port as mini-usb and the otherone called autoguider port. The "dongle" "legacy" autoguider port as much as i gather is used for some old style driving and isnt recommended for pc control?

Anyway, should my ascom driver connection over usb to com port 3 where the mini-usb connection runs, make the ascom connection with iexos-100?

 

error i'm getting is: System.Runtime.InteropServices.COMException (0x80040402): Timed out waiting for received data

 

iexos-100-ascom1.png

 

iexos-100-ascom2.png

 

The manual states: NOTE: For wired ASCOM or Firmware upgrade, you will need a Serial/USB to Mini-USB cable (not included).

It's just an USB mini cable.. why call it serial/usb to mini usb? Is there some funny logic going on and same port can be talked to in two different ways? 

I just plug in usb cable and it talk to pc.. atleast it can retrieve profile info and other stuff I can set from driver, and it appears as connected in device manager to com 3, or isnt it actually and you need more than a usb cable? Am I seeing just my pc side driver settings? (then what is the thing in com3 that appears when i plug the cable in)

 

Thanks you in advance for your time and advice.

Hi Gelisob,

 

I am sorry you are having problems with your iEXOS 100 PMC-Eight connection. I think the problem you are experiencing is because you have failed to switch the PMC-Eight communications mode from WiFi to Serial.  Please correct me if you have completed the following successfully. The iEXOS 100 PMC-Eight mount has an FTDI USB to Serial converter chip which will show up as a com port on your host device (PC). It looks like yours is assigned to com 3. This is normal, but the controller itself needs to be commanded to use that serial port when using the ASCOM driver.

 

If you look in the iEXOS 100 PMC-Eight manual (which I think you have found, here is the link:  https://cdn.shopify....arch2019.pdf?72) on page 15 you will find the following:

 

Wired Operation

Although it is designed to be operated wirelessly, the PMC-Eight can be attached directly to your Windows device. To do this, you will need a cable that has a Mini-USB Type B connector on one end and a Serial/USB Type A connector on the other end that is compatible to the port connections on your chosen device. This cable is not included with the PMC-Eight.

 

NOTE: The ASCOM driver supports Wired and Wireless Operation. The ExploreStars Application only supports Wireless Operation. You will have to use the ExploreStars PMC-Eight ASCOM Driver if you want to use the Mini-USB Port. Explore Scientific PMC-Eight® Application Note PMC8-AN003: Switching Between the WiFi Interface and the Serial  Interface on the iEXOS 100 Mount Controller for more information.

 

You need to switch the default communications port to the desired configuration using the procedures in Application Note PMC8-AN003 listed above.

Here is the link to the application note:  http://02d3287.netso...AN003_rev01.pdf

 

There is an easier way though... 

On the PMC-Eight Groups.io support forum you will find the PMC-Eight Configuration Manager program that will allow you to easily switch the communications mode from WiFi to Serial and back again. Here is the link for the program:  

 

https://espmc-eight....tionManager.zip

 

Hopefully this will get you going.

Edited by Jerry Hubbell, 24 April 2019 - 06:54 PM.

[Gelisob]

Hi Gelisob,

 

I am sorry you are having problems with your iEXOS 100 PMC-Eight connection. I think the problem you are experiencing is because you have failed to switch the PMC-Eight communications mode from WiFi to Serial.  Please correct me if you have completed the following successfully. The iEXOS 100 PMC-Eight mount has an FTDI USB to Serial converter chip which will show up as a com port on your host device (PC). It looks like yours is assigned to com 3. This is normal, but the controller itself needs to be commanded to use that serial port when using the ASCOM driver.

 

If you look in the iEXOS 100 PMC-Eight manual (which I think you have found, here is the link:  https://cdn.shopify....arch2019.pdf?72) on page 15 you will find the following:

 

Wired Operation

Although it is designed to be operated wirelessly, the PMC-Eight can be attached directly to your Windows device. To do this, you will need a cable that has a Mini-USB Type B connector on one end and a Serial/USB Type A connector on the other end that is compatible to the port connections on your chosen device. This cable is not included with the PMC-Eight.

 

NOTE: The ASCOM driver supports Wired and Wireless Operation. The ExploreStars Application only supports Wireless Operation. You will have to use the ExploreStars PMC-Eight ASCOM Driver if you want to use the Mini-USB Port. Explore Scientific PMC-Eight® Application Note PMC8-AN003: Switching Between the WiFi Interface and the Serial  Interface on the iEXOS 100 Mount Controller for more information.

 

You need to switch the default communications port to the desired configuration using the procedures in Application Note PMC8-AN003 listed above.

Here is the link to the application note:  http://02d3287.netso...AN003_rev01.pdf

 

There is an easier way though... 

On the PMC-Eight Groups.io support forum you will find the PMC-Eight Configuration Manager program that will allow you to easily switch the communications mode from WiFi to Serial and back again. Here is the link for the program:  

 

https://espmc-eight....tionManager.zip

 

Hopefully this will get you going.

Thank you Jerry, this explains my problem with wired connection. I will give the manager a try.

Also if there will be revision to the manual, I would recommend simplifying some of the description, it can make unnecessary confusion. 

For example, "you will need a cable that has a Mini-USB Type B connector on one end and a Serial/USB Type A connector on the other end"

can be replaced with "you will need Mini-usb cable".
If user doesnt know what kind of usb port they have or cant understand by looking at the thing, if they need plug or socket, they should not be operating the device. Or they can just get even more confused in the shop if they ask for usb serial with this and that end and the shop worker will be like ****, I have just usb data cable with these connections, not usb serial.. 

Just a thought. I would consider myself somewhat experienced user and if i get confused, it will be even harder for less experienced person.

 

 

 

NOTE: The ASCOM driver supports Wired and Wireless Operation. The ExploreStars Application only supports Wireless Operation. You will have to use the ExploreStars PMC-Eight ASCOM Driver if you want to use the Mini-USB Port. Explore Scientific PMC-Eight® Application Note PMC8-AN003: Switching Between the WiFi Interface and the Serial  Interface on the iEXOS 100 Mount Controller for more information.

 

You need to switch the default communications port to the desired configuration using the procedures in Application Note PMC8-AN003 listed above.

Here is the link to the applicati..

And all that could be instead:

NOTE: For third party applications and wired connection (ASCOM driver for example) you will need to change the USB port Data connection mode. This requires extra steps that are described with more detail in ...

Alternatively, there is now a configuration manager for simpler method to switch communication modes.

 

Oh and I tried this manager link.. this gives an error at first and after I log in, another error, I'll go now and try to figure out that new site and navigation to get to the file, ugh.. maybe put it somewhere where there is working direct link huh? (test in incognito mode)

[Jerry Hubbell]

Thank you Jerry, this explains my problem with wired connection. I will give the manager a try.

Also if there will be revision to the manual, I would recommend simplifying some of the description, it can make unnecessary confusion. 

For example, "you will need a cable that has a Mini-USB Type B connector on one end and a Serial/USB Type A connector on the other end"

can be replaced with "you will need Mini-usb cable".
If user doesnt know what kind of usb port they have or cant understand by looking at the thing, if they need plug or socket, they should not be operating the device. Or they can just get even more confused in the shop if they ask for usb serial with this and that end and the shop worker will be like ****, I have just usb data cable with these connections, not usb serial.. 

Just a thought. I would consider myself somewhat experienced user and if i get confused, it will be even harder for less experienced person.

 

And all that could be instead:

NOTE: For third party applications and wired connection (ASCOM driver for example) you will need to change the USB port Data connection mode. This requires extra steps that are described with more detail in ...

Alternatively, there is now a configuration manager for simpler method to switch communication modes.

 

Oh and I tried this manager link.. this gives an error at first and after I log in, another error, I'll go now and try to figure out that new site and navigation to get to the file, ugh.. maybe put it somewhere where there is working direct link huh? (test in incognito mode)

sorry1.png

sorry2.png

The PMC-Eight Configuration Manager was developed under our OpenGOTO Community open-source software initiative by one of our customers, Chris Moses. It is only available to those that are members of the PMC-Eight groups.io forum for download from there. This is part of the User Contribution folder on the MAIN subgroup.  I think you would want to join the forum as it is Explore Scientifics customer support forum. Even though I answer questions on CloudyNights, I am restricted in my postings here so this is not our main support outlet. Once you join the Groups.io forum, then you will have access to the configuration manager program

[Gelisob]

The PMC-Eight Configuration Manager was developed under our OpenGOTO Community open-source software initiative by one of our customers, Chris Moses. It is only available to those that are members of the PMC-Eight groups.io forum for download from there. This is part of the User Contribution folder on the MAIN subgroup.  I think you would want to join the forum as it is Explore Scientifics customer support forum. Even though I answer questions on CloudyNights, I am restricted in my postings here so this is not our main support outlet. Once you join the Groups.io forum, then you will have access to the configuration manager program

Okay, I figured it out. It was just not very standard forum kind of system, yet another fancy system to figure out. So if anyone else stumbles upon it, you first click the link and dont get anythong, you need to log in (i used google account button), then you click the link again and you get thrown to some "main" section of a thing, when you scroll down there is a button to subscribe/join a group, after this you can now click the link again and then it downloads.

 

Thank you Jerry for the link, I managed to switch modes and get wired connection running.

I have one more question that I wasnt able to figure out from internet and searching topics in the groups.io.

I'm trying to figure out what kind of stellarium-ish program I can use with the computer that also gives alignment options.

I was looking at EQmod and hoped that works over ascom because guides do talk about it and say that it should directly connect to mounts over ascom driver, but I seem to have problem connecting it directly, getting the "Connection timeout" info from eqmod. And I dont see eqmod having the option to bounce it through POH hub system.. only com-port selection in connection settings.

 

Is there a trick to get EQmod working with iexos system or does anyone know good alternative for alignment routine when wired? (no guide camera)

EQmod alignment - https://www.youtube....h?v=f1rVx8_17dc

[Jerry Hubbell]

Okay, I figured it out. It was just not very standard forum kind of system, yet another fancy system to figure out. So if anyone else stumbles upon it, you first click the link and dont get anythong, you need to log in (i used google account button), then you click the link again and you get thrown to some "main" section of a thing, when you scroll down there is a button to subscribe/join a group, after this you can now click the link again and then it downloads.

 

Thank you Jerry for the link, I managed to switch modes and get wired connection running.

I have one more question that I wasnt able to figure out from internet and searching topics in the groups.io.

I'm trying to figure out what kind of stellarium-ish program I can use with the computer that also gives alignment options.

I was looking at EQmod and hoped that works over ascom because guides do talk about it and say that it should directly connect to mounts over ascom driver, but I seem to have problem connecting it directly, getting the "Connection timeout" info from eqmod. And I dont see eqmod having the option to bounce it through POH hub system.. only com-port selection in connection settings.

 

Is there a trick to get EQmod working with iexos system or does anyone know good alternative for alignment routine when wired? (no guide camera)

EQmod alignment - https://www.youtube....h?v=f1rVx8_17dc

Hi Gelisob,

 

It sounds like you are new to ASCOM. First, EQMOD is an open-source ASCOM driver that is only for Synta mount systems, basically the Skywatcher and Orion EQ6, EQ5 and other mounts. It works as a local server and also has some added features that are not standard ASCOM compliant. These enhancements include a multi-star alignment system.  One of the ASCOM Standard API assumptions is that the mount is "physically polar aligned". There is no ASCOM standard API for polar alignment functions. The PMC-Eight ASCOM driver does not include any polar alignment functions which is typically done in the ASCOM client applications if it is available at all.  

 

To get a good physical polar alignment a lot of people either use the program SharpCap or purchase the QHY Polemaster.  These only work if you can see Polaris. If you can't see Polaris, you need to use the Declination Drift alignment method to get a physical alignment. 

 

I use Cartes du Ciel as our planetarium program in our observatory and MaxIm DL to control our equipment. Most astronomy programs out there can use ASCOM drivers.

 

Hope this answers your questions. The PMC-Eight groups.io forum has some threads on polar alignment, so you might search for that to get some more detail on what others are doing.

[sergtert]

Even though you hear this small amount of variation in your mount, you should examine the performance as designed and constructed. The overall motion of the mount should match that shown by others and for astrophotography, the performance when auto-guiding is what matters. I noticed that you are located in Russia. If you don't mind me asking, what dealer did you purchase your mount from?

 

 

Please see this post I made earlier in this thread showing the PHD2 guide logs that demonstrates the performance of the mount when not guiding and when guiding. 

 

https://www.cloudyni...-399/?p=9171012

 

I would like to see your PHD2 guide logs to troubleshoot your issue if you in fact think that this tiny variation in rate is making a large contribution to your guiding error that is not shown in the data provided by my earlier post linked above.  We have several iEXOS 100 PMC-Eight customers, most notably Jim Johnston who have been able to use this mount for long exposure narrow-band imaging with great success.

 

 https://www.cloudyni...-399/?p=9263609

 

If you could provide the specifics on the focal length you are imaging at also that would be helpful.

 

Please contact our Explore Scientific Support staff at +1 (866) 252-3811 ext. 2 if you have any further questions.

I apologize for the delay in replying. I want to thank you for the answers to users and the desire to help in solving problems.

My knowledge of English is very poor and, therefore, I cannot use the help desk phone. To write my posts I use Google translator.

 

If you don't mind me asking, what dealer did you purchase your mount from?

 in the online store "Telescope-Express"

 

 

If you could provide the specifics on the focal length you are imaging at also that would be helpful. 

I would like to see your PHD2 guide logs to troubleshoot your issue

 was made with a quadruplet 65mm  fl=420mm   asi1600 camera.

 PHD2  log https://drive.google...iew?usp=sharing

 

 

I'm sorry, but probably because of my poor English, the meaning of my previous message was incomprehensible. I wanted to find out from other users of the iEXOS-100 mount, does the engine rotate in this way? The manufacturer of this mount knows better than others how the RA motor rotates. And therefore, watching the video can determine this constructive feature or defect.

 

you in fact think that this tiny variation in rate is making a large contribution

"that this tiny variation in rate" leads to the following - in all 100% of the images the stars are oval. Regardless of the length of exposure - a few seconds or a few minutes. In this video, you can see in real time this “this tiny variation in rate”.  https://www.youtube....h?v=pjKQOMlne44

The photograph clearly shows the uneven speed. (look at the zigzag)

I can provide a video where you can see the terrible consequences of "this tiny variation in rate" when video shooting the Moon with a rolling shutter camera. Need to? And the main question. Is it out of luck to me with bad example iEXOS-100 and Jim Johnston was lucky with a successful version of iEXOS-100? Or what?

Attached Thumbnails

• 

[Gelisob]

Hi Gelisob,

 

It sounds like you are new to ASCOM. First, EQMOD is an open-source ASCOM driver that is only for Synta mount systems, basically the Skywatcher and Orion EQ6, EQ5 and other mounts. It works as a local server and also has some added features that are not standard ASCOM compliant. These enhancements include a multi-star alignment system.  One of the ASCOM Standard API assumptions is that the mount is "physically polar aligned". There is no ASCOM standard API for polar alignment functions. The PMC-Eight ASCOM driver does not include any polar alignment functions which is typically done in the ASCOM client applications if it is available at all.  

 

To get a good physical polar alignment a lot of people either use the program SharpCap or purchase the QHY Polemaster.  These only work if you can see Polaris. If you can't see Polaris, you need to use the Declination Drift alignment method to get a physical alignment. 

 

I use Cartes du Ciel as our planetarium program in our observatory and MaxIm DL to control our equipment. Most astronomy programs out there can use ASCOM drivers.

 

Hope this answers your questions. The PMC-Eight groups.io forum has some threads on polar alignment, so you might search for that to get some more detail on what others are doing.

Thanks for the information Jerry. I got my first result with wired control. https://www.flickr.c...05/40753689593/

Since I cant do correction alignement wired, I used "laser in the barrel" approach to roughly polar align and then "swear and peek through a hole" approach to get it in the middle..

Cartes du Ciel does have "sync" in the telescope menu too but I'm guessing it just moves the whole field and is only semi-helpful.

This was enough for so-so 1 minute exposures.. rather poor, given that tiny star-adventurer mini with it's little polar scope and polaris placement crosshair in it gave me 3 minutes without much hassle. But no go-to made searching things a pain and major time sink.

Looks like I cant get wired field alignment/corrector without a guide camera with my iexos-100. (imager is sony, doesnt play ball with things).

[Jerry Hubbell]

Thanks for the information Jerry. I got my first result with wired control. https://www.flickr.c...05/40753689593/

Since I cant do correction alignement wired, I used "laser in the barrel" approach to roughly polar align and then "swear and peek through a hole" approach to get it in the middle..

Cartes du Ciel does have "sync" in the telescope menu too but I'm guessing it just moves the whole field and is only semi-helpful.

This was enough for so-so 1 minute exposures.. rather poor, given that tiny star-adventurer mini with it's little polar scope and polaris placement crosshair in it gave me 3 minutes without much hassle. But no go-to made searching things a pain and major time sink.

Looks like I cant get wired field alignment/corrector without a guide camera with my iexos-100. (imager is sony, doesnt play ball with things).

What focal length are you imaging at with the iEXOS 100?

[Ethanwyh]

Hi guys,

 

I noticed that most of you all did not use ST4 guiding but ascom instead. May I know how did you get your computer to connect to the mount to both PHD2 and SGP/APT? I own an iExos-100 mount but I keep failing at trying to get both programs to conenct to the mount.

 

When I successfully connected my mount to APT first, it would show "ACCESS TO COM PORT: 8 DENIED" 

Vice versa for the case where I successfully connected my mount to PHD2, it would show the same error for APT.

 

Any ideas on how to go about solving this? Help would be greatly appreciated.

 

Just FYI, I managed to get serial (ascom) connection so it wouldn't be any hardware issue. 

[Gelisob]

Hi guys,

 

I noticed that most of you all did not use ST4 guiding but ascom instead. May I know how did you get your computer to connect to the mount to both PHD2 and SGP/APT? I own an iExos-100 mount but I keep failing at trying to get both programs to conenct to the mount.

 

When I successfully connected my mount to APT first, it would show "ACCESS TO COM PORT: 8 DENIED" 

Vice versa for the case where I successfully connected my mount to PHD2, it would show the same error for APT.

 

Any ideas on how to go about solving this? Help would be greatly appreciated.

 

Just FYI, I managed to get serial (ascom) connection so it wouldn't be any hardware issue. 

Read few posts above where I whine about getting ascom control to work with mine. Maybe you too have not switched it's usb mode, by default it is in the wrong mode (doesnt matter that it shows up in device manager)

 

 

What focal length are you imaging at with the iEXOS 100?

 

I'm testing my mini-telescope that is 500mm, as can seen in the link details too

 

 

Isnt it cute eh!

[Jerry Hubbell]

Hi guys,

 

I noticed that most of you all did not use ST4 guiding but ascom instead. May I know how did you get your computer to connect to the mount to both PHD2 and SGP/APT? I own an iExos-100 mount but I keep failing at trying to get both programs to conenct to the mount.

 

When I successfully connected my mount to APT first, it would show "ACCESS TO COM PORT: 8 DENIED" 

Vice versa for the case where I successfully connected my mount to PHD2, it would show the same error for APT.

 

Any ideas on how to go about solving this? Help would be greatly appreciated.

 

Just FYI, I managed to get serial (ascom) connection so it wouldn't be any hardware issue. 

In order to connect to the mount using multiple ASCOM clients you need to connect to an ASCOM hub, or local server driver. Some drivers act as hubs but the PMC-Eight driver is not a hub. We suggest you use the ASCOM platform POTH to connect to the PMC-Eight driver and then connect all your other ASCOM client programs to the POTH. Then you can use PHD2 to send PulseGuide commands via the ASCOM driver to correct the mount and also use your other ASCOM programs at the same time. No need to use the ST4 port.

[Jerry Hubbell]

Read few posts above where I whine about getting ascom control to work with mine. Maybe you too have not switched it's usb mode, by default it is in the wrong mode (doesnt matter that it shows up in device manager)

 

 

 

I'm testing my mini-telescope that is 500mm, as can seen in the link details too

 

tamron500mm-sony6300.jpg

 

Isnt it cute eh!

That's pretty cool.  Using a 500 mm focal length on the iEXOS 100 is pretty ambitious not in terms of weight, but in terms of PE. It should work okay as long as you have an effective autoguiding system on the mount, but you may be pushing the weight limit. Jim Johnston has  been able to get guided performance down to around 1 to 1.5 arc-seconds RMS. 

 

I took a look at your photo of Bode's Galaxy and it looked pretty darn good considering that you are pushing the limits of the mount's performance.

Edited by Jerry Hubbell, 28 April 2019 - 10:49 AM.

[Jerry Hubbell]

Hi sergtert,

 

You said

" I can provide a video where you can see the terrible consequences of "this tiny variation in rate" when video shooting the Moon with a rolling shutter camera. Need to? And the main question. Is it out of luck to me with bad example iEXOS-100 and Jim Johnston was lucky with a successful version of iEXOS-100? Or what?"

 

It could be that you have in fact received a defective mount as this is the first time I have heard of this problem, and as you say, Jim Johnston has had very good luck with his mount.  In the raw unguided PE charts I have not seen a large, uncorrected 1 to 2 second period in the signal. What focal length are you imaging at, and can you tell me the image scale your image was taken at (arc-seconds/pixel) ?

 

Thanks

 

[Gelisob]

That's pretty cool.  Using a 500 mm focal length on the iEXOS 100 is pretty ambitious not in terms of weight, but in terms of PE. It should work okay as long as you have an effective autoguiding system on the mount, but you may be pushing the weight limit. Jim Johnston has  been able to get guided performance down to around 1 to 1.5 arc-seconds RMS. 

If a cheaper tiny star-adventurer mini managed to do 3 minutes then this must definitely do a lot more without a problem. And weight is definitely not an issue, this 500mm lens+camera combo weights 1.1kg (2.4 pounds)

Still trying to find ways to do software align routine similar to eqmod to avoid buying extra guide camera, if there is no way, i guess i will get one.

[Jerry Hubbell]

Gelisob said: " Still trying to find ways to do software align routine similar to eqmod to avoid buying extra guide camera, if there is no way, i guess i will get one."

 

SharpCap may still be an option for you if you could find a way for it to connect to your DSLR. Maybe the other subgroups on CloudyNights could help there.

Edited by Jerry Hubbell, 28 April 2019 - 12:06 PM.

[Newfie Stargazer]

Gelisob said: " Still trying to find ways to do software align routine similar to eqmod to avoid buying extra guide camera, if there is no way, i guess i will get one."

 

SharpCap may still be an option for you if you could find a way for it to connect to your DSLR. Maybe the other subgroups on CloudyNights could help there.

SharpCap is what I have been doing to perform a polar alignment.  Not sure if it will connect to a DSLR though...

 

Jim

[sergtert]

Hi sergtert,

 

You said

" I can provide a video where you can see the terrible consequences of "this tiny variation in rate" when video shooting the Moon with a rolling shutter camera. Need to? And the main question. Is it out of luck to me with bad example iEXOS-100 and Jim Johnston was lucky with a successful version of iEXOS-100? Or what?"

 

It could be that you have in fact received a defective mount as this is the first time I have heard of this problem, and as you say, Jim Johnston has had very good luck with his mount.  In the raw unguided PE charts I have not seen a large, uncorrected 1 to 2 second period in the signal. What focal length are you imaging at, and can you tell me the image scale your image was taken at (arc-seconds/pixel) ?

 

Thanks

Hello Jerry Hubbell

 

Thank you for the quick response. I used an off-axis guide camera ar0130 and  main camera asi1600mc  telescope FL=420mm.

Both have a pixel size of 3.75  and pixel scale = 1.84 arc-sec/px     I have a RA error  twice the DEC error.   This makes the stars oval.

This is caused by jerks of the RA motor. 

 

Thanks

Attached Thumbnails

• 

[Jerry Hubbell]

Hello Jerry Hubbell

 

Thank you for the quick response. I used an off-axis guide camera ar0130 and  main camera asi1600mc  telescope FL=420mm.

Both have a pixel size of 3.75  and pixel scale = 1.84 arc-sec/px     I have a RA error  twice the DEC error.   This makes the stars oval.

This is caused by jerks of the RA motor. 

 

Thanks

Hi,  could you attach your PHD guide log so I can take a look at it directly?

 

Thanks

[sergtert]

Hi,  could you attach your PHD guide log so I can take a look at it directly?

 

Thanks

 

Hi, The message #206 provides a link to the log. I offer it again - Log PHD2 iEXOS-100

 

Thanks

[Ethanwyh]

In order to connect to the mount using multiple ASCOM clients you need to connect to an ASCOM hub, or local server driver. Some drivers act as hubs but the PMC-Eight driver is not a hub. We suggest you use the ASCOM platform POTH to connect to the PMC-Eight driver and then connect all your other ASCOM client programs to the POTH. Then you can use PHD2 to send PulseGuide commands via the ASCOM driver to correct the mount and also use your other ASCOM programs at the same time. No need to use the ST4 port.

Hey Jerry,

 

Thanks so much for your help! I was reading up on POTH and yup, this seem to do the trick. WIll be taking out on tests this week when the skies are better. Hopefully it'll all turn out well.

 

Cheers!

[Jerry Hubbell]

Hi, The message #206 provides a link to the log. I offer it again - Log PHD2 iEXOS-100

 

Thanks

Hi sergtert,  I missed that the first time!  sorry about that.

 

Thanks!

[sergtert]

Hi sergtert,  I missed that the first time!  sorry about that.

 

Thanks!

Hello. I am very grateful and appreciate your help. And I hope that the problem will be resolved.

 

Thanks

[Jerry Hubbell]

Hi sergtert,

 

I compared your guide log with the logs I received from Jim Johnston and noticed a few things. First there is a difference between yours and his Autoguider in that he is guiding at a focal length of 162 mm and you are at 420, so your image scale is almost 3x what his is.

 

There are 2 main differences that I see in your log compared to Jim's, the first is that both the RMS and Pk-Pk noise is higher in Jim's data. This is because he has a larger image scale than you. It seems that your RMS value in pixels though is much higher than his, basically twice as much (0.6 px RMS, versus 0.3 px RMS for Jim's). With the iEXOS 100 you should have guiding performance of < 0.5 px. The amount of movement shown in your guidelog can be caused by a couple of things related to the mount and also related to the sky conditions or seeing.

 

The other thing I see when looking at the periodicity spectrum of your data is that you have much more, and higher amplitude, broadband noise over the full period range compared to Jim (see screenshots below).  I think this is an indication of the amount of seeing during your observation run. Typically this type of broadband noise is caused by the sky. That's not to say that the gear mesh and the quality of the gears may not also be contributing to this, I would not expect that. The belt drive system should take care of any broadband gear noise that you might see with standard spur gears. If the ring and worm gears were very rough, then you could possibly see this type of broadband noise, but again, I think it would be filtered out by the belt drive.

 

Overall, your RMS values are lower than those in Jim's data so I think that this is the expected response.

 

NOW.... to the question about the small 1 second oscillations.  In order to really understand that issue, I would need you to do another guiding session except I need you to take the data at a much higher pace. You should set your exposure time down to 0.2 seconds so that I can see the higher frequency data which includes this 1 second oscillation. The previous guide log was taken at 1 second exposures which only allowed me to see periods down to 2 seconds which as you can see from the spectrum was very quiet down at that end.

 

So if you can do that when you get a chance that would be great.

 

Thanks!

 

sergtert Periodic Error Chart

 

Jim's Periodic Error Chart

 

sergtert Frequency Spectrum Chart

 

Jim's Frequency Spectrum Chart

 

[sergtert]

NOW.... to the question about the small 1 second oscillations.  In order to really understand that issue, I would need you to do another guiding session except I need you to take the data at a much higher pace. You should set your exposure time down to 0.2 seconds so that I can see the higher frequency data which includes this 1 second oscillation. The previous guide log was taken at 1 second exposures which only allowed me to see periods down to 2 seconds which as you can see from the spectrum was very quiet down at that end.

 

So if you can do that when you get a chance that would be great.

Hello

Thank you for taking the time to do a detailed log analysis. In the near future I will try to make a test with subsecond exposures.

Thanks

[sergtert]

Hello Jerry

Guiding with exposures 0.2 sec.    PHD2 log exposure 200ms   

Thanks