EQMOD Problems

[Kaliska]

I'm setting up a new mini pc with all the required software to run my imaging setup and the only issue i have run into is getting my mount connected to EQMOD. I know the cable works as i've used it on my laptop and everything checks out, but as soon as i swap it over to the new pc nothing happens. I fire up EQMOD Toolbox and get this. I installed the FTID drivers, but still can't get it working and couldn't see it in the device manager either. Any help or pointers in the right direction would be greatly appreciated.

Duncan

[LightBucket]

Which cable are you using, as some use the Prolific chipset and not FTDI...

[Kaliska]

its the Lynx Astro USB EQ DIRECT one.

[Adreneline]

Hi. Apologies of you have already done this but did you click on Driver Setup and search for the comm port? - click on the little binocular symbol once the Driver Setup window opens. With my NUC the Lynx is either on Comm 3 or Comm 10 depending on which port I plug it into. Also, I had to run Toolbox as 'administrator' the first time I ran it in order to 'Register' the software (right-click and select 'Run as Administrator')

HTH

[Kaliska]

@Adreneline    I thought you had cracked it when i ran it with admin rights as as i got a "success", but thats where it stopped. I've attached a few images of what its showing me.

[Adreneline]

Hi,

This is my driver setup page:

I've input the entries for Timeout, Retry and Baud.

Not connected to the mount at present so can't check the System status; I will do tomorrow if you're still having problems.

 

[Atreta]

3 hours ago, Kaliska said:

I'm setting up a new mini pc with all the required software to run my imaging setup and the only issue i have run into is getting my mount connected to EQMOD. I know the cable works as i've used it on my laptop and everything checks out, but as soon as i swap it over to the new pc nothing happens. I fire up EQMOD Toolbox and get this. I installed the FTID drivers, but still can't get it working and couldn't see it in the device manager either. Any help or pointers in the right direction would be greatly appreciated.

Duncan

I noticed that in the first picture, under "windows and ascom registration ", eqmod_sim.exe is chosen  instead of eqmod, could it be causing this?

[Kaliska]

6 hours ago, Atreta said:

I noticed that in the first picture, under "windows and ascom registration ", eqmod_sim.exe is chosen  instead of eqmod, could it be causing this?

No, that was just me registering both eqmod and eqmod_sim, both produced the same result.

But, thought I'd just try and connect it again this morning before i went to work and guess what, it connected first time! I didn't do anything different, no additional drivers were installed, i just don't get it, wasted pretty much all of yesterday trying to get this fixed

Thanks guys for your help anyway, onwards and upwards as they say.

[Adreneline]

7 hours ago, Atreta said:

eqmod_sim.exe is chosen  instead of eqmod

Haha! Why didn't I spot that? Must have been "the lateness of the hour"! Well spotted  

Fingers crossed that will sort the problem for @Kaliska

[Adreneline]

Getting a few crossed threads here! Not sure whta happened there.  Glad to hear it's working - sometimes the old 'on-off' switch saves the day!

 

[Kaliska]

2 minutes ago, Adreneline said:

Sorry to hear it's still not working

No, its working now after it had a good nights sleep apparently, never seen the "leave it for 6hrs to get some rest then try again" option in the Eqmod FAQ