Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_30_second_exp_2_winners.thumb.jpg.b5430b40547c40d344fd4493776ab99f.jpg

stash_old

Members
  • Content Count

    1,356
  • Joined

  • Last visited

Community Reputation

672 Excellent

About stash_old

  • Rank
    Sub Dwarf

Profile Information

  • Gender
    Not Telling
  • Interests
    Angling
  • Location
    Cranwell UK
  1. But only when a human is at the helm LOL - most computers go one for years when humans leave them alone LOL I never make mistakes - quote from my wife "you are always right" LOL ---------------------------- missed the "you think" bit LOL
  2. - no just me being mischievous LOL - it always M/S fault never the user
  3. Ah but wait until you power off and start again - LOL
  4. Quote from APT forum "Hi Lawrence, I'm pretty sure you don't need the the Canon EOS Utilities to be installed to use APT with an EOS camera. APT installs and uses the Canon Application Programing (API) library, which provides the software required to connect to EOS cameras. If you wish to leave the Canon Utilities installed then you should be able to disable it connecting to your camera automatically. It's been quite a, while since I used the utilities but, if memory serves, there should be an EOS utility icon in the Windows System Tray (on the right hand side of the Taskbar). Right clicking on this may give you some option to cdisable EOS start when camera is connectedc. You might have to search around a bit, if I've got this wrong. But it can be done. Hope that helps. Cheers, Jim" So just make sure that the EOS software isn't loaded and grabbing the camera before APT - its says quite clearly it uses API lib (installed by APT) not the EOS software utilities. P.S. that goes for any other "camera" software you may have loaded - most likely
  5. Forgeting RDP from M/S for a moment a lot of other Remote viewers require Internet as they act as an relay service and so will not work without the internet. Not totally up to date on Teamviewer but it didn't allow your type of connection. But hen there is this https://community.teamviewer.com/t5/Knowledge-Base/Can-TeamViewer-be-used-within-a-local-network-LAN-only/ta-p/4618 Dont know what version of Win 7 you have but if you can install M/S RDP service on your Win 7 then you can use standard RDP viewer to connect the 2 devices but just use the IP address or see if network explorer on can see the other device (you may have set he Win 7 up NOT to allow RDP). he other problem is that you will need to change the Win 7 to ignore your DHCP as this most likely sets up the default root to be your router (and so the Internet) and set the default gateway to something like 0.0.0.0 but still using the same network IP subnet. some info to help with Win 7 end https://kb.parkland.edu/50610
  6. While the camera is plugged in - look in the devices (device manager) and see if there is an ! sign against the device if recognised. Plus may also show up as extra disc drive - if so can you open the "canon drive" and see your files. Presume you have a SD card inserted.
  7. You have got your camera in manual mode (dont know the 450d well) if you are using APT and you have looked at the canon matrix of camera support on APT site that defines which version of the processor type is supported. https://www.ideiki.com/astro/EOS.aspx If you choose the wrong matrix processor it will not work but might connect. https://ideiki.com/astro/usersguide/starting_apt__dslr_or_ccd_cmos_.htm?ms=AAA%3D&st=MA%3D%3D&sct=MA%3D%3D&mw=MjQw Plus requirements need to be met for APT - not normally needed. Plus make sure you haven't loaded any software that "grabs" the Canon camera ! Normally not a problem on Windows In extreme cases when software/OS is not set up correctly you will need to start APT in run as Administration Mode
  8. Ok tried it out on last nights moon and with a slight Indi settings dslr camera problem and it seemed to work well. Thanks Parick/Han.
  9. Totally 100% agree - should be great when its finished Will follow with interest and benefit for my future project.
  10. Hi Han , Would this (Autofocus on Planets) still work with a DSLR ?
  11. Dont know if this helps or not but Gina did you read this thread ? https://indilib.org/forum/ccds-dslrs/3255-using-3-cameras-at-once.html?start=12 - Bet you have
  12. Gina said "Since Ekos can only handle one imaging system currently, separate instances of KStars/Ekos are needed to handle dual imaging. It does handle a separate camera for guiding. Each imaging camera will have it's own RPi for capture and focussing the lens." and I concur that if you want to run 2 concurrent imaging camera's (i.e. NOT 1 imaging and 1 guiding which is ok) it is my understanding that is not possible at the moment because of Ekos !- perhaps @RadekK could confirm or deny this ! You can as you point out run many Indiservers in a "Chain" but there will be one master and the rest will be slaves as I understand it - I have done "chaining" using multiple PI's and this works. In effect Ekos thinks its talking to one Server as I understand the chaining process. Ok the master server can contain many devices and Kstars/Ekos has a profile so the 2 Kstars/ekos would have different devices defined in the active profile. The following mentions this and Gina was part of the discussion and I presume had further PM's with the Dev's. https://indilib.org/forum/ccds-dslrs/4256-multiple-imaging-camera-s.html Easy test Gina could run 2 Ekos/Kstars Plus 1 Indiserver with all the devices set up Dont know if anyone has done it it yet
  13. As far as I am aware you can Virtual Linux on the same Mint Tower - subject to memory and processor speeds and run either Ekos/Kstars or CCDciel in the virtual set up. Will still need 2 RPI running Indiserver. OR YOU MIGHT just be able to run CCDCIEL + Ekos on the Tower (No virtualisation needed) and have 2 RPI running Indiserver. One Indiserver would run Mount,guiding,platesolving,camera A,focusing while the other would just run Mount simulator , Camera B and Focusing. You just point Ekos and CCDCIEL to different Indiserver IP addresses. This should work as I think the Indiserver config files are held on the Indiserver computer (i.e. not the tower). Thats the theory
  14. Thanks to Radek there is a new version of Astroberry available. Please may I suggest ,as I stated on Indi, please make a back up of your existing SD card or use a new one - just in case there are bugs. Most do this by default Hell last thing is to get some clear sky (whats that) and find your new update causes you to loose clear skies. Thank you @Radek for the new version. https://www.astroberry.io/distro/ I wonder what this month anniversary of Raspberry PI might bring (if anything) - 8GB + 64bit OS version perhaps
  15. Moonlite is a well documented protocol + Robert Brown's Myfocuser - both have indi driver's and ascom! But they re for Stepper motors and Arduino. Gina on SGL has done RPI plus hat focuser plus indi driver i think
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.