Jump to content





  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by perfrej

  1. For the record: I have never, ever helped Mr Penrice disassemble an Atik camera. Never. I did change the USB connector in Mr Woods' QSI-583, though, and it still works. ALso for the record, then. /per
  2. That's "brexit" for you... Expect more misery in terms of pricing of foreign goods ahead. /per
  3. Haha! Yes, I probably could. I can go back to myself and see what I can incur in terms of cost... Ouch!
  4. And the big advantage of encoded and modeled mounts over guiding is that they indeed do correct the error in anticipation, like before it happens... We can do the old song "Never fall in love again" with a new text, "Never want to guide again" /per
  5. The sensor is good. Generally speaking, the KAF series of sensors are noisier than the Sony ones, but the latter simple don't have the real estate. Personally, I never use darks with my two KAF-8300M cameras, just BIAS and flats. /p
  6. Today, I would say the QSI and the Moravian cameras represent the best value for money. I currently use the QSI-683wsg8 and my next camera will be a Moravian. /p
  7. Yes, those forks look pretty much the same, don't they. I don't think they licensed anything in that design,though. Even the motors are made right there along with a derotator/focuser and the rest of the details. /p
  8. And the LRGB one is full bandwidth with the same scope, same camera and same brand filters. I agree that mount comes first, then camer then optics, but the latter two are much closer together. /p
  9. I recently chose 14 as a good middle speed for model building. Works vey well, and since I am not present in body, faster would have worked too /per
  10. Gus, That is the TEC-140 and a QSI-683 with Astrodon filters. TEC's own flattener, non-reducing, with 70 mm imaging circle. So in essence, the sensor is really too small and uses only a fraction of the available field. /p
  11. Well, the GM1000HPS does 15 degrees per second, the GM2000HPS 20... So this thing is twice as fast as their current fastest model, and according to what I heard it can do 50 as well. /per
  12. Many professional observatories use direct drive technology. What is needed is a brake system that can mechanically stop it from moving freely. SkyVision has that, ASA does not. I think direct drive is mature enough at this point. /per
  13. Could be... Look out when 40°/s send the secondary mirror towards the enemy! /p
  14. It appears the Italians have made their own super efficient direct drive motors and put them into two large AzAlt fork mounts. My wife and I were in Venice last week and stopped by north of Milan on the way over to our remote observatory. 10Micron people were very nice and showed us their clean factory during our brief stop. We also got to play with their new mount series with direct drive motors that they made themselves. I don't have much details to spill, but apparently they are extremely efficient, as evident by the size of the power supply in the lower left corner of this viseo: http://www.10micron.eu/en/new-az5000-dds-demo-video/ Probably a bit above my price range It is, anyway, interesting that the same control system as used in their normal mounts is now powering the massive direct drive motors. The thing zooms around at 40°/s so we had to stand clear. Power feed is 48V with low single digit amps. /per
  15. Hold your horses! This is a subsystem that exposes a bunch of the APIs also exposed by the Linux Kernel. We're talking about GNU utilities that can run in his environment, nothing really Linux. There is no graphics subsystem exposed, only the Windows file system. Alas, you cannot run any server software and you cannot use the bash shell to start or automate anything that bears the name "Windows". So, nothing INDI will work. Period. /per
  16. If one tries not to go on the "I want to do five targets per night" trip, and instead concentrate on one or three projects at a time, AND give them plenty of time, then the sensor's QE is not going to matter. Like Sara and Olly, I am sucker for field of view, so no Sony sensors here. I take many subs and do not ever use darks as I simply cannot see the difference on the final result between darks and no darks. So, BIAS and flats is my calibration method, and I do take a lot of subs. The more subs you have - up to a point - the less work you need to when processing. Simple as that. Here's what that can yield with a QSI-683 and lots of subs. I assure you, the processing was minimal both in the narrow-band and in the RGB image. /per
  17. I use the FTDI chip in my designs and the problem with com port numbering in Windows is only an issue if you unplug the device, and then replug it while the application still has the old com port open. It then gets the next available number - a process that actually makes sense. If you unplug again and make sure that the application doesn't have the port open it will revert to the original number. That's FTDI 231XS. Do't know about the other ones. /p
  18. The current incarnation of Model Maker supports a dome connected to MaximDL, and the dome must also be connected to Model Maker. Maxim will slave the dome, and Model Maker waits for it to start moving after each commanded slew, and then waits for it to become stationary. Maxim normally has a few seconds of waiting time before it starts moving the dome, so that's why MM has to wait until it detects movement before waiting for movement to stop. I have not tested this with a real dome myself, but I have reports from users verifying that it works fine. /per
  19. The free modeling tool, ModelMaker, that I wrote for 10Micron mounts supports dome slaving, so all the dome does is slow you down a bit as it doesn't slew as fast as the scope. The time it takes with a dome can be improved upon by placing the sky points in a sequence that involves as small dome slews as possible. A roll off is always faster for modeling, but a dome offers wind protection and quicker closure on weather events. A dome is also a lot more expensive, and you really don't want to go with the cheaper ones. /per
  20. I went for the ready-made VM... Works great. I am currently adding Qt's development environment in order to at least get a half-decent environment for actually programming. Spoiled by Visual Studio 2015, I am (whatever you think about windows, VS2015 is the most advanced environment out there). /per
  21. They would still have the same GUID in ASCOM and be indistinguishable... Only the direct driver way works, for instance with serial number, but if you load an ASCOM driver and want two instances theyu need to have different GUIDs, so two versions of the driver are needed.
  22. That is so that they can use two instances of an ASCOM driver. ASCOM does have the slight disadvantage of only permitting one device per GUID, but on the other hand, if you had two focusers with the same data in the hardware description, how would you keep track of which focuser is which? You really need to give them separate IDs some way. /per
  23. Oh, don't ever venture down the dark WiFi path! It inevitably leads to utter despair! Cable it... /per
  24. I confirm that I will spend some time with INDI, most likely in July or August, and produce a driver for 10Micron products and the Remote Control USB Hub. Being a remote buff, Ekos scheduler is the thing that finally got my attention, and I will most likely contribute at least logic input, if not code, to that project. Luckily, I do not do guided imaging at all, so one less component to worry about. I am interested in novel ways of focusing the telescope, but I have not yet researched how that is done in the Ekos environment. At this time, my vision is to use a Pi 2 or 3 in a Losmandy extension unit between mount and scope, and to run an INDI device server in that. The rest of the logic (Ekos) can execute either in that thing or in a separate and more powerful computer elsewhere. All I need is one 12V feed and one Ethernet up to the mount. Perhaps I can have this running in my remote observatory in Provence by Christmas or so. I plan to go down in late November and should have something ready and balcony tested by then. Whoah! /per
  25. That is typically cable or hub power problems. I had this happen and the problem was the USB 5V supply dipping ever so slightly. After fixing that, I found that it appeared sensitive to data lead glitches as well. Solution is to connect it with a new cable through a powered hub. If that fixes it you know what is wrong. On the other hand, a driver problem may do it as well, but the SX wheel is a standard Human Interface thing, so drivers shouldn't be a problem. /p
  • 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.