Dana Tousley replied to the topic 'Trying to connect PHD2' in the forum. 19 hours 47 minutes ago

rockstarbill wrote: When you connect phd2 to your camera and mount, select indi driver, then you should get a dialog with info to connect to indi. Click connect and then choose the device from the drop down menu and connect to it in phd2.


That's what I'm trying to do. I select INDI camera in PHD2, the INDI popup appears to select QHY and when I select it and press connect, that's when PHD2 dies. Is there a log somewhere I can attach?

Read More...

Dana Tousley replied to the topic 'Trying to connect PHD2' in the forum. yesterday

From the documentation written for me:

After launching PHD2, select your INDI equipment and set their options


That's what doesn't work. I never make it through connecting a QHY guide camera and EQMOD mount in PHD2 and making a PHD2 profile. I'm not even trying to involve EKOS. Just launching INDI from command line and launching PHD2.

PHD2 can't function with just INDI and without EKOS?

And the problem in the log is the last word, Bye. I was still trying to use it.

Read More...

Dana Tousley replied to the topic 'Trying to connect PHD2' in the forum. yesterday

And any time I manage to get to the INDI control panel to show, it will soon kill PHD2 also.

Read More...

Dana Tousley created a new topic ' Trying to connect PHD2' in the forum. yesterday

I started indiserver through the command line and tried to make a profile in PHD2. PHD2 just can't connect to the camera. I'm using a QHY 5L II M guide camera.

This is what info I get from the terminal:

dana@astrolaptop:~$ indiserver -v indi_qhy_ccd indi_eqmod_telescope indi_joystick
2017-03-25T18:08:37: startup: indiserver -v indi_qhy_ccd indi_eqmod_telescope indi_joystick 
2017-03-25T18:08:37: Driver indi_qhy_ccd: pid=2331 rfd=3 wfd=6 efd=7
2017-03-25T18:08:37: Driver indi_eqmod_telescope: pid=2332 rfd=4 wfd=9 efd=10
2017-03-25T18:08:37: Driver indi_joystick: pid=2333 rfd=5 wfd=12 efd=13
2017-03-25T18:08:37: listening to port 7624 on fd 8
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on GPS Simulator.TIME_UTC
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_PARK
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_SHUTTER
2017-03-25T18:08:38: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_sk.xml
2017-03-25T18:08:38: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_align_sk.xml
2017-03-25T18:08:38: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_simulator_sk.xml
2017-03-25T18:08:38: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_scope_limits_sk.xml
2017-03-25T18:08:38: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on .GEOGRAPHIC_COORD
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on .TIME_UTC
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on .DOME_PARK
2017-03-25T18:08:38: Driver indi_eqmod_telescope: snooping on .DOME_SHUTTER
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on CCD Simulator.FILTER_SLOT
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on CCD Simulator.FILTER_NAME
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on SQM.SKY_QUALITY
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on indi_eqmod_telescope.EQUATORIAL_EOD_COORD
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on indi_eqmod_telescope.TELESCOPE_INFO
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on .FILTER_SLOT
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on .FILTER_NAME
2017-03-25T18:08:38: Driver indi_qhy_ccd: snooping on .SKY_QUALITY
2017-03-25T18:09:09: Client 0: new arrival from 127.0.0.1:33170 - welcome!
2017-03-25T18:09:14: Client 0: read EOF
2017-03-25T18:09:14: Client 0: shut down complete - bye!

What additional information do I need for someone to attempt diagnosis?

Thanks in advance,

Dana

Read More...

Dana Tousley replied to the topic 'Help with GPSD' in the forum. 2 days ago

Just the mount works. GPS is in the trash. I will have to buy another one. When that arrives I will not plug it into my USB hub, I will have to plug it in to the USB on the other side of the laptop, so UDEV can differentiate between it and my mount by USB bus. Previously they were on the same bus and it was random as to which got recognized and given a name first. It's a Linux problem that windows somewhat shared. With Windows I had to be careful to always plug the same device into the same port to assign the same COM port.

Read More...

Dana Tousley replied to the topic 'New user thoughts on polar alignment routine' in the forum. 2 days ago

I was running 2.7.6 already. I'll have to look for the button again.

Read More...

Dana Tousley replied to the topic 'Help with GPSD' in the forum. 2 days ago

I changed an existing Vendor / Product ID (total of 4 bytes) to the one I had written into the GPS and the next time I tried connecting to mount - nothing. reloaded old driver - mount works again. Problem is I am extremely inexperienced with Linux and it takes me far longer than it should to look up even the simplest stuff.

Read More...

Dana Tousley replied to the topic 'Help with GPSD' in the forum. 3 days ago

I'm giving up. I've tried modifying both the Windows and Linux drivers - spent two hours under crystal clear skies last night trying to fix the Linux driver because it wouldn't see the mount either.

That puck is permanently hosed and needs replacing. Lesson: if you don't know what you're doing, don't #$&# with it.

Read More...

Dana Tousley replied to the topic 'Help with solving' in the forum. 3 days ago

I reinstalled the index files and everything worked without changing anything else.

Thanks,

Dana

Read More...

Dana Tousley replied to the topic 'New user thoughts on polar alignment routine' in the forum. 3 days ago

In Automatic mode it was still reversing directions last night.

libindi-dev (hope that's the correct package) version 1.4.1+r3006~201703222147~ubuntu16.04.1

And is there an option to make the correction vector screen larger?

Thanks,

Dana

Read More...

Dana Tousley replied to the topic 'Horizon limits: scope outside limits. Nothing to abort' in the forum. 5 days ago

I get this all the time also so I'd like to hear the true solution, but I think it's related to location settings. I'm hoping that if I ever actually get the mount aligned and synchronized these messages will go away.

But time to work on that is dependent on weather, which I have only cloudy (when I don't have to work).

Read More...

Dana Tousley replied to the topic 'New user thoughts on polar alignment routine' in the forum. 1 week ago

Thanks for looking at the East-West thing, but take a look at SharpCap. It has real time updating correction vector, numeric error feedback and auto star selection. They hard coded the star solutions near the pole and it solves in under a second.

Read More...

Dana Tousley created a new topic ' New user thoughts on polar alignment routine' in the forum. 1 week ago

Tried the polar alignment routine for the first time last night, had a thought / observation and maybe a bug report.

When you get to the correction stage, with the picture showing the correction vector, it should be mathematically possible to translate the picture to a true alt-az picture. And it would be helpful to give correct altitude / azimuth directions, e.g. 20 arcmin up + 15 arcmin left. SharpCap attempts this, but doesn't translate the picture, their up means up on the picture, which the user has to determine by trial and error how that relates to actual mount movement. In the EKOS case, you have performed three solutions and moved the mount in a controlled direction, by then you should know the camera angle in relation to absolute altitude / azimuth. Proper orientation of the looping picture to the adjustments you have to make, and real time numeric feedback on the direction and magnitude of the required adjustments would be a big help.
°
Also, I'll have to try to duplicate this, but the first time I made it through the routine I had it in Auto and the mount moved West - West. So here I am at 60° west of the pole and made my adjustments. I thought I'd set it to go East and double check. It moved 30° East, solved, and then moved 30° West - back where I started from on the second round. I had to start teardown at that point I will attempt to repeat tonight.

Read More...

Dana Tousley replied to the topic 'Help with solving' in the forum. 1 week ago

Thanks I'll try the -fits2fits both ways, and try verbose. I put ALL the index files in that directory, 4200 to 4219. Eventually I will use everything from a 35mm prime lens with an APSC chip to my 127 Mak with my guidescope (8 arc min). Last night I was just trying to get through the polar alignment routine with my guide camera and scope.

Read More...

Dana Tousley created a new topic ' Help with solving' in the forum. 1 week ago

What should I look for it the online Astrometry.net works fine and the offline always says 'Solver Failed - try again'?

The index files are installed and are shown in the options panel. The FOV was solved by the online solver. The latest Astomometry.net is installed. Need some ideas to point me in the direction of a solution.

Thanks in advance,

Dana

Read More...

Dana Tousley replied to the topic 'Help with GPSD' in the forum. 2 weeks ago

I'll try. I already edited the .inf file with the Windows drivers and it still didn't work - but it's real common for the Prolific driver to not work in Windows as it is.

Read More...

Dana Tousley replied to the topic 'Help with GPSD' in the forum. 2 weeks ago

Well, I've spent a lot of time under the hood and learned how to write UDEV rules. Unfortunately I've also learned the hard way what NOT to do. I was trying to differentiate between my SkyWatcher AZ-EQ 5 GT, and a GlobalSat BU 353 S4. Ubuntu saw them both as Prolific PL2303 devices. The only differentiation was the USB device, exactly the thing I wanted to lock down. I could have made udev rules by bus number and device number, but I thought I'd get smart...

So I downloaded the Prolific EEPROM writer and tried to write a serial number, starting with the GPS. It wrote successfully, but did not show up as an attribute in udev. So here is where I made my fatal mistake. I thought I would change the product ID on one of them from 2303 to 2304. Surely they would now be different correct? They are, and Windows can't recognize a Prolific PL2304 and now the windows EEPROM writer can't write it back...

Udev isn't too happy about a Prolific PL2304 either. It's now a blinking brick that properly receives GPS satellite data, but can't send it anywhere.

So now I'm wiser, and hindsight being 20/20 thankful I hosed the $30 item rather than the $1300 one! I'll order another one, and I'll simply have to plug it into another port so it shows up on a different bus rather than just plugging it into the USB hub.

Read More...

Dana Tousley replied to the topic 'Joystick configuration' in the forum. 2 weeks ago

Awesome! Double Thank You.

Read More...

Dana Tousley replied to the topic 'INDI-EQMOD crashing constantly' in the forum. 2 weeks ago

Awesome! Thank you!

Read More...

Dana Tousley replied to the topic 'Joystick configuration' in the forum. 2 weeks ago

Found the file manually, and there is no reference to Port. The only thing it appears to be saving is debug info.

contents of /home/.indi/Joystick_config.xml:

<INDIDriver><newSwitchVector device="Joystick" name="DEBUG"><oneSwitch name="ENABLE">
      Off
  </oneSwitch><oneSwitch name="DISABLE">
      On
  </oneSwitch></newSwitchVector><newSwitchVector device="Joystick" name="DEBUG_LEVEL"><oneSwitch name="DBG_ERROR">
      On
  </oneSwitch><oneSwitch name="DBG_WARNING">
      On
  </oneSwitch><oneSwitch name="DBG_SESSION">
      On
  </oneSwitch><oneSwitch name="DBG_DEBUG">
      Off
  </oneSwitch></newSwitchVector><newSwitchVector device="Joystick" name="LOGGING_LEVEL"><oneSwitch name="LOG_ERROR">
      On
  </oneSwitch><oneSwitch name="LOG_WARNING">
      On
  </oneSwitch><oneSwitch name="LOG_SESSION">
      On
  </oneSwitch><oneSwitch name="LOG_DEBUG">
      Off
  </oneSwitch></newSwitchVector><newSwitchVector device="Joystick" name="LOG_OUTPUT"><oneSwitch name="CLIENT_DEBUG">
      On
  </oneSwitch><oneSwitch name="FILE_DEBUG">
      Off
  </oneSwitch></newSwitchVector></INDIDriver>

Any way to include Port information in this so it can be persistent also?

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!