Jump to content



  • Posts

  • Joined

  • Last visited

Everything posted by niknak

  1. Hi James. I have 1.6.3 at the moment but I'll PM you. In your experience .... what have been the most stable and useable cams for use with OAC?? Any recommendations for me to look at ?? What about the Altair units as Mark mentions above ?
  2. Thanks Mark. Downloaded and tried but still no joy. Although I'm not sure the INDI server has set up right. It never seems to want to connect. Will play with it more later. I see you list the Altair GPCAM in your sig. Is that with a Mac ?? Does it (Altair) work well with everything ??
  3. Afternoon folks. Recently bought a QHY5L-II-M for guiding and perhaps a little planetary imaging. I know It may have been asked before but has any else had trouble with this cam and OSX? I'm running OSX 10.14 and have PHD2, EZCap and OACap installed. Both programs appear to be able to see the camera but a preview generates nothing. Has anyone else had success? What did you use? Any suggestions much appreciated.
  4. I did consider a mirror less system but I’m really after a compact camera. something along the lines of a Sony rx or canon g series.
  5. Hi folks. Im in the market for a new high end compact camera. My old canon G9 has served me faithfully for years but I’m looking to upgrade. I’d love to stay with canon but they have not way to mount an adapter onto the front. As I’m looking to spend £400 to £600 I wondered if anyone had any suggestion of makes and models that had high iso capability and that also had a proper way of mounting to a telescope (not digiscoping) that I might consider. There may not be any but I thought it was worth an ask :) cheers.
  6. Having recently sold my DMK41 I find myself slightly regretting that decision. However, before I go back out and buy another cam for astro stuff I thought I'd canvas opinion on views for a replacement. It will be primarily used with my two coronados for solar stuff. Suggestions welcome.
  7. Now if we can just get ExampleApp to work ...........
  8. Tried Neb4 with both the decimal and the hex code - seems to work with both
  9. I know why PHD2 image was white. It was totally over exposed. The cap was off the cam.
  10. Big progress ...... (yay) but still not there. I have now placed the ChipID into Neb 4. It only works by removing the 0x at the start of the code 0x1A54F5C9 just needs inputting as 1A54F5C9. Once this was done I set a small capture series of 5 x 1s exposures with a 1s interval. The output of five FITS files is further than I've ever got - so some progress at least.
  11. Right..... Got PHD2 to accept the correct ChipID using the method you state so some small progress. I now get a white window inside the normally black window of PHD2 (see below) I asked it to log before starting so I have emailed you the most current log file just now.
  12. Just tried to change the chipid in openphd2 as requested but it doesn't see to want to save. It just keeps defaulting back to the "ee" beginning? It wont allow me to insert my "1a54f5c9" code
  13. But that is the right ChipID (in the log file) isn't it ?? yours was ee8f4c9 and not ee4f5c9 which is mine.
  14. Have you got an email address to send it to ?? or you you like the contents in forum ??
  15. Have added into ExampleApp and nothing happens - well, noting more than if you didn't have the camera plugged in at all. In PHD2 I get the following error message.
  16. Finally !!!!! Yay. I contacted Atik and they sent the usb1 and usb2 drivers. Once installed into windows, the chipID program could see and talk to the camera. Got the serial number and the ChipID - see below.
  17. Well........ I've tried and tried. I have visited the site that created the fdtichip-id program and followed all the instructions as far as can and it still yields nothing. I am however not a PC person being a long term mac user - which explains my desire to get it working on a mac. so ...... I'm taking it to a friend to see if he can get to the bottom of the FDTIChip-ID issue. In the mean time ....... As the device manager can see it but also states that it has no driver ....... I was wondering if you (or anyone else) had a copy of the original 16IC-c driver. According to ATIK it was missed of the latest Artemis software downloadable from the ATIK site.
  18. It does appear in the device manager. I don't have the disk with the original software so I cant try the old drivers.
  19. Just tried on a native PC and on the win7 virtual box I have on my macbook. Doesn't work on either ...... grrrr ! Calling a PC mate to see if he can shed any light. I did wonder if the reason your chip id program can't see it is the fact that it doesn't have a driver ???
  20. Hi Nick. Really sorry for dragging this out and I do really appreciate your (and everyone elses) help with this. I searched the error log for the term "VUSBID" but that term wasn't present either Interestingly, I rang Atik this morning to see if they could shed any light and as soon as I mentioned the words " mac, nebulosity and legacy" guess whose name instantly appeared
  21. Tried logging in PHD2 as well. I have searched the log but cannot find any of the search terms "validate" or "VPID" within it I can send you the log file if you think that would help ??
  22. Ok. I have tried double clicking the GetFTDIChiID.exe and opening it from a command prompt but get the same result each time (ie it cant find any FTDI devices) The camera does show up in the device manager (albeit without a driver) I have opened the ExampleApplication and put in the default mappings obtained from PHD2 but to no avail
  23. I have just redownloaded he binary to make sure it was the correct one. Once the program runs it displays (in a little pop up pane) the following ..... DLL Version = 1.1.0 Get Chip IDs using handle 0 FTDI devices connected Press return to exit. Perhaps as you say the two dlls need putting somewhere specific for it to work properly ?? Any ideas ??
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.