Jump to content

SkySurveyBanner.jpg.21855908fce40597655603b6c9af720d.jpg

UKAstroBill

Members
  • Posts

    29
  • Joined

  • Last visited

Reputation

6 Neutral

Profile Information

  • Location
    Oxfordshire

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Struggling with the interaction with filters. If it’s mono then LRGB will be fine so maybe ok for galaxies but then problematic if you want the Ha. For OSC similar issue with dual narrowband which are now very good. can they have come up with some orientable drop in filters that only cover the larger sensor?
  2. This is helpful. Any photos from the Altair with a full frame camera would be very useful to me. I’m pondering a new short refractor and the Altair is on my shortlist. I’m used to sorting out Backfocus but for a more portable rig where I might use no filter or filters of different thickness it looks very good. I had a look at it at PAS - slightly bigger and heavier than expected but immaculately made. Photos please!
  3. I’ve been using the new Altair 4nm certified Sii Oiii filter, both in its own and to do full SHO with the partner Ha Oiii filter. The certification is important as with these increasingly narrow bands any error can cause a massive drop in transmission. I don’t think it makes sense to get too worked up about the purity of the channel extraction given the cross talk in the Bayer matrix. While it’s all theoretically correct that there is mixing and an annoying matrix problem to solve where you would struggle to know the entries accurately, in practice I reckon it’s either ignorable or easily solved in a pragmatic way. With many targets the Ha is dominant and the biggest effect is pollution of the Oiii by Ha cross talk. With a Hypercam 24CFX and Altair Ha Oiii subtracting about 10% of the raw Ha killed the cross talk. Given the weakness of typical Sii signals the Oiii channel from my SII Oiii seems reasonably pure but I’m still looking at pollution of the Sii by the Oiii. in terms of the final Imagery the effect the the cross talk is pretty low. If you make eg an HOO image then the O having a bit of H it in just ends up with the red a little less saturated. No big deal. I’ll put some astrobin links up later.
  4. I'm loving my Hypercam 26C. Works great with Altair Capture and there has been a driver update for ASCOM gear so I am migrating to NINA. When I bought it the Altair was about £400 cheaper than the 2600. That has narrowed since I see. Having only had it a short while my processing is not necessarily optimal for the output of the camera, and I only stopped using a Nikon Z6 in the autumn, but my first two shots with the 26C are on astrobin at https://www.astrobin.com/full/scybuo/0/ https://www.astrobin.com/full/zv20wu/0/ both are OSC jobs - M31 with an IDAS NGS and the Rosette with the IDAS NB2. I'm using an offset of 32 and Gain 1 in Capture.
  5. That's a great response. Look forward to trying it. Thanks! By the way I just tried cloud makers and AstroImager looked like it could talk to my camera and I could operate the cooling and set some other choices, but was unable to capture a photo. Bizarre.
  6. OK so here is an interesting fact about oacapture and oalive. As they download right now they do not see the Hypercam 269c. BUT - if you grab the libaltaircam.dylib file from the latest Altair Capture and stick it into the oalive/capture package directory then the oa stuff does recognise the 269c, and as far as I can tell it works well apart from not having the cooler controls. So it would seem to me that only a small amount of work recompiling with the latest SDK ought to enable it properly. Hint hint! Altair Capture under MacOS works fine with the 269c apart from only saving 8 bit per channel files. I think thats probably the front end more than the library as the oa tools seemed to have more bit depth options. Without the cooling I did not want to probe extensively. I'll take a look at Cloudmakers next. As noted it will probably depend on which SDK has been used.
  7. I'll give oalive a go when I have finished trying to make sense of deBayering what I got from Windows Capture under Parallels. ADDED: Capture seems to like GBRG in APP and DSS for the 269c. I think it must be to do with ROWORDER things on the Bayer Matrix. APP reads the FITS files as RGGB and wants to process them that way. You have to use tab 0, and force the CFA to GBRG and then the stacked files look sensibly coloured.
  8. I’m in this boat with my Mac and a new 269c Hypercam. 1. MacOS Altair Capture works ok on my faster 2018 MacBook Pro but does not work properly on my older 2012 MBP with only USB2. I say OK because it appears to be limited to saving TIF files in 8 bits per channel. I’m not doing live stacking as I do that offline in APP. I’ve got the Windows version working as of last night under Parallels and it appears to offer fits file saving using the full bit depth. I have raised a ticket with Altair on the question of the Mac version having fuller bit depth support. 2. Also working with KStars/INDi/EKOS. I have this running on my Mac and PHD2 also is fine using a ZWO guide cam and controlling my CEM40. But my 269c is not recognised and I am trying to find out from INDI and Altair why. 3. the oa tools are something I have yet to try. On the list!
  9. Guidescope option looks wimpy. I think my Asiair Pro kit has a similar spec one and I got that to see if I can improve tracking on the SkyGuider Pro.
  10. On this same issue I do not want to modify my CEM40 as I want to switch regularly between single and dual operation. Is there a side by side kit that (a) comes with a dovetail fitted to the cross bar at right angles, that dovetail pointing in the same direction as the two telescope mounts; (b) the two mounts have brackets supporting both Losmandy and Vixen (c) one side can be adapted to finder/guide shoe, preferably with directional adjustments? Maybe I’m being lazy, but I just want to be able to swap between one and two with no fuss. I’m pretty sure I could do it with ADM parts at huge cost, but what I’d like is an affordable complete kit that preserves all the orientations.
  11. I’ve had the Astro Hutech part for a few weeks now and am really pleased with it. The optical length calibration for IDAS filters is perfect and the body lens interface is rock solid. Mine is the one coupling Nikon Z bodies to Nikon F lenses and it has a mechanical control for adjusting aperture on G type lenses. So you can adjust aperture from the adapter on non E Nikons and 3rd party lenses from Sigma for example. It’s calibrated for the IDAS range so that’s for filters that are 2.5mm thick. Thinner filters from other manufacturers will usually fit but you might not be able to achieve infinity focus as the optical path is too long. That’s not a fault in the design so much as the fact that AH have tuned the part to work perfectly with the par focal IDAS range. It works brilliantly with the IDAS set.
  12. Just looking at adapting one of these to an APM 107/700. If anyone has done that I’d be interested to know what adapters people used and if any spacing issues arose. Looks like I can go from m82 to m68 then to the m68 adapter starizona sell. I have m82 adapter Already on the focuser to take the Riccardi FF. in passing I note Starizona sell a 2in extension as necessary for the Esprit 120/150. Presumably this is a recent addition given comments above. If anyone has one of these on a scope around 100-110mm I’d be keen to see a flat taken on 35mm sensor, or better still a 1:1 24mm x24mm square crop from full frame. That’s what I shoot with using the Starizona SCT Corrector III that has a nominal circle of 27mm. It’s a bit of a stretch to the 34mm diagonal of that square but I can do it with flats at the price of noisy corners. The Apex claims 30mm circle so maybe rather better in that plan. With the 0.65 if that works I’d prefer it to the large Riccardi 0.75, which is the standard option. (I can use the Apex also on another scope.) Views very welcome!
  13. 533 is looking very attractive to me not just on price and amp glow but because it is square. Square sensors make a lot more sense for astro. Limited circular fields of illumination are best utilised by square sensors and there is no up in space. I just wish it was bigger. 20mm x 20mm would suit my scopes best and I’d like the lower noise of larger pixels.
  14. Borg responded with the useful detail that their filter adapter has an optical length of 31.3mm and is designed for IDAS filters, of thickness 2.5mm and refractive index 1.5168. So they have decided to calibrate well for a certain thickness, which makes a lot of sense. I’m ordering one and will try it out in comparison with the 2 inch version of FAstroTZ.
  15. All kinds of possibilities. Just make sure that when you screw in a filter it is clear of the sensor and the end of the lens. The Geoptik has plenty of clearance to ensure this and I screw the filter assembly well in to be clear of the lens. 1.25 is plenty for a 4/3 or DX sensor. meanwhile Borg have confirmed their part is fixed length and indicated they designed it with IDAS filters in mind. I hope to get more details after Thanksgiving. Don’t know the optical length yet.
×
×
  • 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.