[guide-user] problem with adding OAG chip
Bill Gray
pluto at projectpluto.com
Fri Apr 24 14:50:33 EDT 2020
On 4/24/20 2:04 PM, Bernd Klemt wrote:
> thanks for your help. I solved the problem (see attachment, if allowed). My line
> looks as following, again beside the line break:
>
> Moravian G2-8300 + ASI290Mini KAF-8300 5.4 5.4 3358 2536 215
> 0,.7,.31,.23,1936,1096
I've added this, plus the ASI290 by itself, to the various 'ccds'
files. (Guide has a 'ccds.nam' for English, 'ccds.nad' for German,
'ccds.nai' for Italian, 'ccds.nas' for Spanish). If you download
https://www.projectpluto.com/ccds.zip
(about 28 KBytes) and unZIP the contents in your Guide folder, you'll
replace at least 'ccds.nam', and the CCD Dialog will show the various
cameras people have asked about or added themselves in recent years.
Of course, we'll probably have to tweak the separation between
main chip and guider, once we have that information.
I haven't had many inquiries about these for a while, but in the
'history' section at the bottom of ccds.nam, I see that I had one
a week ago and another in January, with various cameras added each time.
If you _do_ add your own camera with a guider chip, I'd suggest
taking a look at the text in ccds.nam that begins with "Some of the
guider chip placements are done in a 'legacy' manner..." It used to
be that you had to figure the ratio of the width of your guider chip
to the width of the main chip, same for the heights, and then the
ratio of the separation between chips to the main chip's height. It
was all very error-prone. It still works, but the new system lets
you just say (for this case) "the ASI290 guide chip has 1936x1096
pixels, each 2.9 microns square, and the chip centers are X millimeters
apart." Which is the data you'll usually get from a specification sheet.
-- Bill
> It looks the same beside the distance of the guiding chip from the main chip (at
> the moment I don't know the actual separation). It was murphy or a too
> "intelligent" editor! For editing I used Notepad++ and it substituted spaces with
> a tab. When opening the camera file with the standard Editor I immideately saw
> that the columns were not in line. Correcting this and the guiding chip appears
> in Guide!
>
> Clear skies
> Bernd
>
> Am 24 Apr 2020 um 11:26 hat JoeMize geschrieben:
>
>> Bernd, the following I saved in 2017, it´s a discussion with Bill Grey adding a
>> 2nd guiding chip for my MMOAG opposite the on-board STL11K guiding chip and
>> rotated 90deg for better field coverage. I hope this helps you find your
>> problem...joe :)
>>
>> Actual ccds.nam SBIG Research 11000XM line, new guider chip highlighted - works
>> perfectly. SBIG Research 11000XM KAF-11000M 9 9 4008 2672
>> 917 0,.6231,.1313,.1477,640,480 0,-1.08117,.098470,.196939,480,640
>>
>> Bills discussion follows, unfortunately in a future conversation Bill couldn´t
>> get the "dotted path" of the MMOAG chip to display...joe
>>
>> From: Bill Gray
>> Sent: Sunday, October 15, 2017 8:23 PM
>> To: Joe Mize
>> Subject: Fwd: Re: [guide-user] Is Guide9 capable of displaying 'two' Guider chips?
>>
>> Hi Joe,
>>
>> From our original correspondence back in early 2016... must admit,
>> I'd completely forgotten about it. But fortunately, it was still in
>> my e-mail archives, so I didn't have to recreate the math.
>>
>> -- Bill
>>
>> -------- Forwarded Message --------
>> Subject: Re: [guide-user] Is Guide9 capable of displaying 'two' Guider chips?
>> Date: Thu, 28 Jan 2016 13:06:44 -0500 From: 'Joe Mize' jmize at svic.net [guide-user]
>> <guide-user at yahoogroups.com> Reply-To: guide-user at yahoogroups.com To:
>> guide-user at yahoogroups.com
>>
>> Thkx Bill, that did it. I duplicated `ccd.nam´ as a backup before I appended
>> your figures, "SBIG Research 11000XM KAF-11000M 9 9 4008 2672 917
>> 0,.6231,.1313,.1477,640,480 _0,-1.08117,.098470,.196939,480,640_".
>>
>> When starting Guide9 the new chip wasn´t displayed. Opening "CCD Dialog",
>> unchecking Show Fame, cycling the Dialog and rechecking Show Frame the second
>> Guide chip appeared. The 2nd Guide chip is perfect for Guide Star selection and
>> image composition.
>>
>> FYI: Right click-dragging a line to measure the short dimension of the new chip
>> Guide9 shows the following:
>> 3.7412´ = 224.47"
>> PA 359.1 deg
>> RA offset : 0.0603´ = 3.6232" = 0.59 sec
>> Dec offset: 3.7404´ = 224.44"
>>
>> Thkx again Bill...joe :)
>>
>> "May He Go Among the Imperishable Stars"
>> Joe Mize, StarFields Observatory,
>> Chiefland Astronomy Village
>> http://www.cav-sfo.com/indexarchive.html
>> *From:* mailto:guide-user at yahoogroups.com
>> *Sent:* Thursday, January 28, 2016 10:25 AM
>> *To:* guide-user at yahoogroups.com <mailto:guide-user at yahoogroups.com>
>> *Subject:* Re: [guide-user] Is Guide9 capable of displaying 'two' Guider chips? Hi
>> Joe,
>>
>> OK, it should work about like this :
>>
>> The main chip is a KAF-11000, with 4008 x 2672 pixels, each nine
>> microns square. That makes it 36.072 x 24.048 millimeters.
>>
>> The guiding chips are both TC327s, with 640 x 480 pixels, 7.4
>> millimeters square. So they're 4.736 x 3.552 millimeters.
>>
>> The built-in guider chip is 4.736 / 36.072 = 0.13129 times the width
>> of the main chip, and 3.552 / 24.048 = 0.14770 times the height. That
>> leaves us with the separation between the chips to figure out... which,
>> fortunately, SBIG documents :
>>
>> http://archive.sbig.com/sbwhtmls/ccdplacement_large.htm
>>
>> (which could have spared me even the very modest amount of arithmetic
>> done above). The center-to-center distance is 15.39 millimeters, which
>> is 15.39 / 24.048 = 0.63997 times the height of the main chip. Which
>> is why the guider chip specification for the SBIG-11000 is
>>
>> 0,.6231,.1313,.1477,640,480
>>
>> ...first the separation horizontally (zero, in this case; the chips
>> are one over the other), then the vertical separation (0.6231 times the
>> height of the main chip, not quite what we got... looks as if I used the
>> height from the above URL, which probably contains some non-imaging rows).
>> Next, we have the ratios in width and height between guider and main chip.
>> Finally, we specify that the guiding chip has 640x480 pixels.
>>
>> Your extra guiding chip, being tilted 90 degrees, would have width
>> ratio 3.552/36.072 = 0.098470 and height ratio 4.736/24.048 = 0.196939.
>> If it's 26 millimeters, center to center, from the main chip, that would
>> be 26/24.048 = 1.081171 main chip height units. Except we'll make it
>> negative, to put it on the opposite side from the built-in guiding chip.
>>
>> Tacking all that on to the existing guiding chip specifier, we get
>>
>> 0,.6231,.1313,.1477,640,480 0,-1.08117,.098470,.196939,480,640
>>
>> Edit your 'ccds.nam', look for the SBIG 11000 line, and add that
>> second bit, and the guiding chip will show up. (Unfortunately, without
>> a second set of guiding rings...)
>>
>> As a side note: in hindsight, this was a really dumb design
>> decision. At the time I wrote this part of Guide, I assumed there
>> would only be a few guiding chips, and I'd add them in as I learned of
>> them. So I didn't invest a lot of time making it user friendly. But
>> even given that, it would have been about as easy for me to make
>> the format for the above line look like this :
>>
>> 0,15.39,9,9,640,480 0,-26,9,9,480,640
>>
>> ...i.e., offsets in millimeters, followed by guider chip sizes in
>> microns, then guider size in pixels. Had I done so, it would have
>> saved a lot of trouble, both for Guide users trying to add their own
>> guiding chips (or making mosaics), and for me in terms of providing
>> tech support for them. Dunno what I was thinking when I made it the
>> way I did, but it's definitely not my finest hour.
>>
>> -- Bill
>>
>> "May He Go Among the Imperishable Stars"
>> Joe Mize, StarFields Observatory,
>> Chiefland Astronomy Village
>> http://www.cav-sfo.com/indexarchive.html
>>
>> From: Bernd Klemt
>> Sent: Friday, April 24, 2020 5:32 AM
>> To: guide-user at projectpluto.com
>> Subject: [guide-user] problem with adding OAG chip
>>
>> Hello all,
>>
>> I tried to add a guiding chip to an existing camera in CDDS.NAM and also in
>> CCDS.NAD (the german counterpart). But without success.
>>
>> I raised the numer of cameras by 1 at the top of the files (201 in my case). I
>> copied the existing camera entry (Moravian G2-8300)
>>
>> Moravian G2-8300 KAF-8300 5.4 5.4 3358 2536 212
>>
>> and gave it a new ID which wasn't used: 215. Then I added the following
>> parameters:
>>
>> 0,.9,.31,.23,1936,1096 which means that the guiding chip (a ZWO ASI290 Mini in the
>> Moravian Off Axis Guider) is in the middle above the main chip and the guider chip
>> has 31% of the width and 23% of the height of the main chip. And the number ot the
>> pixels of the ASI290 Mini is 1936 x 1096.
>>
>> So the complete line of the new camera definition looks like this (without the
>> line break):
>>
>> Moravian G2-8300 + ASI290Mini KAF-8300 5.4 5.4 3358 2536 215
>> 0,.9,.31,.23,1936,1096
>>
>> But whatever I do, when choosing the new camera in Guide, the ccd frame is shown
>> without the guiding chip and it's surrounding circles. I even tried the values
>> form several SBIG guiding chips, no success.
>>
>> Any help is appreciated.
>>
>> Clear skies
>> Bernd
>>
>> Bernd Klemt
>> Sternwarte Herne
>>
>> MPC (A18)
>> www.sternwarte-herne.de
>>
>>
>>
>> --
>> guide-user mailing list
>> guide-user at projectpluto.com
>> http://projectpluto.com/mailman/listinfo/guide-user_projectpluto.com
>>
>
> Bernd Klemt
> Sternwarte Herne
>
> MPC (A18)
> www.sternwarte-herne.de
>
>
>
More information about the guide-user
mailing list