most recent 30 from http://astroanswers.org 2010-09-10T20:49:48Z http://astroanswers.org/feeds/user/5 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://astroanswers.org/questions/455/andor-camera-using-ascom-drivers/461#461 Chris Rowland 2010-07-27T14:54:40Z 2010-07-27T14:54:40Z

<p>I've had a look on the Andor site, they provide a SDK and say there are some third party drivers.</p> <p>It should be possible to write an ASCOM driver that will connect using their SDK or through one of the third party drivers.</p> <p><a href="http://www.andor.com/software/software_support/" rel="nofollow">http://www.andor.com/software/software_support/</a></p>

http://astroanswers.org/questions/84/how-can-i-convert-code-samples-between-vb-net-and-c/449#449 Chris Rowland 2010-07-13T10:33:55Z 2010-07-13T10:33:55Z

<p>From what is posted I would guess that the code needs to be better formatted so it is split in to separate lines.</p> <p>Maybe the line separators are not what is expected.</p>

http://astroanswers.org/questions/442/problem-installing-ascom-platform5b Chris Rowland 2010-06-25T20:46:24Z 2010-06-25T20:51:57Z

<p>I've been unable to install ascom platform (ASCOMPlatform5b.msi).</p> <p>I get a message that I need .net 2.0.something. It looks like a version checker is not up to date. I'm running XP SP3 w/ dotNet framework 4.0</p> <p>Would be happy to hear it's operator error.</p> <p>Regards, JJ</p> <p>(posted by JJ on ASCOM-Talk and moved here as it looks useful)</p>

http://astroanswers.org/questions/442/problem-installing-ascom-platform5b/443#443 Chris Rowland 2010-06-25T20:51:57Z 2010-06-25T20:51:57Z

<p>Try downloading and installing .NET 2.0 with any latest SPs from the Microsoft site.</p> <p>AIUI the various flavours of .NET are designed to work alongside one another and .Net 4.0 will not satisfy a program looking for 2.0.</p>

http://astroanswers.org/questions/435/celestron-unified-driver/436#436 Chris Rowland 2010-06-11T04:45:50Z 2010-06-11T04:45:50Z

<p>This is beacuse your system is using a comma as a decimal separator and the installer is expecting a full stop. There are workrounds suggested here</p> <p><a href="http://astroanswers.org/questions/105/on-platform-5-5-why-do-i-get-a-message-platform-5-is-required-when-i-install" rel="nofollow">http://astroanswers.org/questions/105/on-platform-5-5-why-do-i-get-a-message-platform-5-is-required-when-i-install</a></p> <p>and here</p> <p><a href="http://astroanswers.org/questions/177/ascom-platform-5-0b-installer-hangs-if-comma-is-decimal-separator" rel="nofollow">http://astroanswers.org/questions/177/ascom-platform-5-0b-installer-hangs-if-comma-is-decimal-separator</a></p> <p>This will be fixed in the next release of the driver.</p>

http://astroanswers.org/questions/428/ascom-utilities-net-implementation/429#429 Chris Rowland 2010-05-29T16:08:44Z 2010-05-31T07:13:49Z

<p>In C# </p> <pre><code>string test = new ASCOM.Utilities.Util().PlatformVersion; </code></pre> <p>works and in VB.NET</p> <pre><code>Dim test as String = New ASCOM.Utilities.Util().PlatformVersion </code></pre> <p>works and gives Intellisense, once the "()" is typed after the object definition.</p> <p>Intellisense isn't available with the original implementation because Util has been defined as type Object, not Util.</p>

http://astroanswers.org/questions/424/ascom-support-for-multiple-axes/425#425 Chris Rowland 2010-05-27T23:00:57Z 2010-05-27T23:00:57Z

<p>I don't see why an ASCOM driver couldn't be written for this. The driver would need to convert to and from the three or four mount axis positions and the sky coordinates of Ra and Dec.</p> <p>This would allow any scope control program to connect to this system and to the application it would look the same.</p> <p>There may be a lot of things that aren't handled in the ASCOM protocol but some could be put in the driver setup and, for astronomical purposes, the others could be ignored.</p>

http://astroanswers.org/questions/391/is-the-pulseguide-camera-function-blocking-or-non-blocking/392#392 Chris Rowland 2010-05-05T07:30:21Z 2010-05-05T07:30:21Z

<p>It looks like an oversight in the template documentation.</p> <p>The Camera Programmer's Reference says:</p> <blockquote> <p><strong>Remarks</strong></p> <p>This method may return immediately after the move has started, in which case back-to-back dual axis pulse-guiding can be supported. Use the IsPulseGuiding property to detect when all moves have completed.</p> </blockquote> <p>It's up to the driver author to implement whatever will work with the hardware.</p> <p>I'd suggest implementing IsPulseGuiding even with a blocking move, just in case some other thread gets in.</p> <p>Applications should always check IsPulseGuiding so they can cope with blocking or unblocking calls. </p>

http://astroanswers.org/questions/370/telescope-pointing-state/371#371 Chris Rowland 2010-04-28T12:23:09Z 2010-04-28T12:23:09Z

<p>This has been the source of a considerable amount of confusion. This is because it's not as simple or obvious as it appears.</p> <p>Basically ASCOM intends that the SideOfPier property and it's friends refer to the pointing state <strong>NOT</strong> to the physical side of pier. This property is needed so that mount error correction and the dome shutter position can be handled correctly.</p> <p>The current telescope V2 document, marked Revised 16 Jan 2008, has a good explanation in the Telescope.SideOfPier property section.</p> <p>Make sure that you have the latest version of this, available from the ASCOM site here <a href="http://ascom-standards.org/Standards/Index.htm" rel="nofollow">http://ascom-standards.org/Standards/Index.htm</a>, the version that's installed as the basic installer is older and doesn't have the clarification.</p> <p>To clarify the PierSide enumeration:</p> <p>PierEast means that the mount is on the East side of the pier, looking West <em>when the mount is looking away from the pole</em>, i.e. South in the northern hemisphere.</p> <p>For PierWest the scope is looking East.</p> <p>In this circumstance the pointing state and the physical side of pier are the same, but there is a zone where the scope is looking North and West or North and East where the scope is physically on the other side of the pier but the pointing state has not changed. (This is for the Northern hemisphere.)</p> <p>If the scope can reach a position without doing a pole flip then the SideOfPier property has not changed.</p>

http://astroanswers.org/questions/347/ascom-upgrade-4-1-to-5-0/351#351 Chris Rowland 2010-04-27T07:45:46Z 2010-04-27T07:45:46Z

<p>You need to install the 5.0 platform, then the 5.5.1 update.</p> <p>5.5.1 isn't a full platform, just an upgrade and can only be installed over 5.0.</p> <p>I'm a little surprised that 4.1 worked at all on a 64 bit system because it's entirely 32 bit. Maybe it's OK if all the applications that use it are also 32 bits.</p> <p>(Posted as a new answer because a comment has no formatting)</p>

http://astroanswers.org/questions/342/lx200r-corrector-plate-is-off-its-base/343#343 Chris Rowland 2010-04-25T17:37:42Z 2010-04-25T17:37:42Z

<p>I would think that a scope with a corrector that moves from side to side like that is faulty.</p> <p>I suggest that you contact your dealer and get it investigated and if necessary fixed or replaced under guarantee.</p>

http://astroanswers.org/questions/340/ascom-installation-problem/341#341 Chris Rowland 2010-04-25T08:15:35Z 2010-04-25T08:15:35Z

<p>The reason for the installer to fail is probably because the helper.dll has not installed correctly. The check for the version uses the helper and any error will give the error you see.</p> <p>I can't be so helpful about the error installing 5.5.1, this works on a lot of W7 64 bit machines. Registering the helper dll by hand might help but somebody else may have a better solution.</p>

http://astroanswers.org/questions/281/dome-driver-source-code-in-c/330#330 Chris Rowland 2010-04-21T13:09:56Z 2010-04-21T13:09:56Z

<p>The driver templates are included in the ASCOM platform. Install this with the Developer components option selected. You need to make sure they are in the correct place, the installation instructions explain how to do this.</p> <p>They are for C# and VB.NET and are a very good way to get started.</p>

http://astroanswers.org/questions/319/why-am-i-getting-error-80040154/320#320 Chris Rowland 2010-04-12T07:59:19Z 2010-04-12T07:59:19Z

<p>The error seems to be somewhere in the COM world and so we aren't getting good information.</p> <p>What I suggest is that you change your code to use the client toolkit, this should keep more of the code in .NET and at the least it may be easier to determine what is going wrong.</p> <p>Here are some code snippets that might help</p> <pre><code>using ASCOM.DriverAccess; public partial class Form1 : Form { private ASCOM.DriverAccess.Camera oCamera; // camera object private string CameraID; // camera ID string // choose a camera try { CameraID = Camera.Choose(CameraID); lblCameraName.Text = CameraID; } // create and connect to the camera try { oCamera = new Camera(CameraID); oCamera.Connected = true; } private void ShowParameters() { if (oCamera == null) return; lblSizeX.Text = oCamera.CameraXSize.ToString(); lblSizeY.Text = oCamera.CameraYSize.ToString(); lblPixelSizeX.Text = oCamera.PixelSizeX.ToString("F2"); lblPixelSizeY.Text = oCamera.PixelSizeY.ToString("F2"); lblMaxBinX.Text = oCamera.MaxBinX.ToString(); lblMaxBinY.Text = oCamera.MaxBinY.ToString(); try { lblElectronsPerADU.Text = oCamera.ElectronsPerADU.ToString(); } catch { lblElectronsPerADU.Text = @"N/A"; } </code></pre> <p>This obviously won't compile as is but it's all copied from a working camera test applicaton. It should get you a bit further on.</p> <p>By the way, using the client toolkit, implemented in the ASCOM.DriverAccess namespace, is the preferred way to choose and connect to ASCOM devices in .NET.</p>

http://astroanswers.org/questions/294/starry-night-ascom-in-windows-7/295#295 Chris Rowland 2010-03-30T17:54:29Z 2010-03-30T17:54:29Z

<p>This was answered some time ago here. See <a href="http://answers.ascom-standards.org/questions/53/connecting-starrynight-to-celestron-scope" rel="nofollow">http://answers.ascom-standards.org/questions/53/connecting-starrynight-to-celestron-scope</a></p>

http://astroanswers.org/questions/291/synscan-eqg-eq6-orion-atlas-ascom-driver/292#292 Chris Rowland 2010-03-26T11:27:55Z 2010-03-26T11:27:55Z

<p>A lot of people with the SynScan controller use EQMOD.</p> <p>AFAIK this replaces the entire HC and implements it's own, PC based, control with it's own ASCOM driver.</p> <p>This may solve your problem.</p>

http://astroanswers.org/questions/279/ascom-driver-for-celestron-does-not-support-park-on-synta-mounts/290#290 Chris Rowland 2010-03-25T10:50:33Z 2010-03-25T10:50:33Z

<p>The Celestron scope driver does support Park for the Celestron scopes but not for the Synta scopes.</p> <p>This is because the low level command that's used isn't available on the Synta scopes.</p> <p>I don't see a good way to fix this. I don't want to break this for some of the Celestron scopes - which are my principal responsibility.</p> <p>It's not even very clear how to tell if the driver is connected to a Synta scope, in most cases the Synta hand control is designed to respond to the Celestron commands, it's just the command that's used for park that's missing.</p>

http://astroanswers.org/questions/276/how-to-set-the-slew-rate-of-the-ascom-dome-simulator/287#287 Chris Rowland 2010-03-24T13:39:33Z 2010-03-24T13:39:33Z

<p>It's a <strong>really bad idea</strong> to write directly to the XML file that the Profile uses because if the method of writing changes your code won't work. This happened to some people because until recently the profile information was stored in the registry. People who were writing directly to the registry had problems when the profile store changed to XML files.</p> <p>It is much better to use the profile.GetValue and Profile.WriteValue methods because if the way these are implemented changes your code will still work.</p> <p>Your example needs a slight addition:</p> <pre><code>Profile p = new Profile(); p.DeviceType = "Dome" string something = p.GetValue(deviceID, "Something", ""); p.WriteValue(deviceID, "Something", "", something); </code></pre> <p>I may have the exact format incorrect, I'm doing this from memory, the important thing is to set the device type.</p> <p>There are some examples in the documentation.</p> <p>A good way to set device specific things is to do it in the setup dialog. You will see that this is being done in the simulator.</p>

http://astroanswers.org/questions/285/dome-control-setup-wizard/286#286 Chris Rowland 2010-03-24T13:27:11Z 2010-03-24T13:27:11Z

<p>This link <a href="http://www.scopedome.com/en/ScopeDomeDriverHelp/geometria_kopuly.htm" rel="nofollow">http://www.scopedome.com/en/ScopeDomeDriverHelp/geometria_kopuly.htm</a> shows the geometry and gives a link to Chris Lord's detailed dome synchronisation algorithms.</p> <p>AFAIK the ASCOM dome hubs implement these and need the dome geometry values that it specifies. I think these are sufficient to solve this.</p> <p>Trying to deduce the relationship between scope position and the required dome position by doing a series of measurements would be time consuming and I don't know of anyone who does this.</p>

http://astroanswers.org/questions/281/dome-driver-source-code-in-c/282#282 Chris Rowland 2010-03-24T07:42:34Z 2010-03-24T07:42:34Z

<p>This Answer may help <a href="http://answers.ascom-standards.org/questions/185/hub-and-simulators-source-code-wanted" rel="nofollow">http://answers.ascom-standards.org/questions/185/hub-and-simulators-source-code-wanted</a></p> <p>There isn't much source code in C++ though. Most is in VB (6 or .Net) and C#.</p>

http://astroanswers.org/questions/110/ascom-install-error/273#273 Chris Rowland 2010-03-22T18:51:47Z 2010-03-22T18:51:47Z

<p>Deleting files and folders installed by installers is a bad idea because it confuses the installer, or quite probably removes files that are vital to it's operation.</p> <p>Things I'd try to retrieve the situation:</p> <ul> <li>Use System Restore to get your system to before everything went wrong, then try to reinstall or repair.</li> <li>Do a Repair installation. If you are lucky this will restore the deleted stuff and allow you to proceed.</li> <li>Do a remove of the installation. Hopefully this will remove the rest of the installation and an install will then work.</li> </ul> <p>It's difficult to know what else to suggest.</p>

http://astroanswers.org/questions/255/sky-scout-windows7/256#256 Chris Rowland 2010-03-07T11:05:25Z 2010-03-07T11:05:25Z

<p>The Celestron support site says that the SkyScout won't work with Windows 7:</p> <p><a href="http://www.celestron.com/c3/support3/index.php?_m=knowledgebase&amp;_a=viewarticle&amp;kbarticleid=2340&amp;ratingconfirm=1" rel="nofollow">http://www.celestron.com/c3/support3/index.php?_m=knowledgebase&amp;_a=viewarticle&amp;kbarticleid=2340&amp;ratingconfirm=1</a></p> <p>and also not with 64 bit Windows:</p> <p><a href="http://www.celestron.com/c3/support3/index.php?_m=knowledgebase&amp;_a=viewarticle&amp;kbarticleid=1785&amp;nav=0,218" rel="nofollow">http://www.celestron.com/c3/support3/index.php?_m=knowledgebase&amp;_a=viewarticle&amp;kbarticleid=1785&amp;nav=0,218</a></p> <p>It will be worth contacting them, if they see there's a demand they are moe likely to do something about it.</p>

http://astroanswers.org/questions/249/icons-inno-and-windows-7/250#250 Chris Rowland 2010-03-05T18:10:28Z 2010-03-05T18:10:28Z

<p>This could be a W7 issue. Perhaps it's changed the way that shortcut icons are specified. If you create a shortcut manually in W7 does it put the right icon in place?</p> <p>Another suggestion is to look at the properties of the shortcuts that Inno creates, are they different to the ones that W7 creates? The Inno Setup FAQ has something about setting paths for shortcuts.</p>

http://astroanswers.org/questions/119/ascom-windows-7-64bit/247#247 Chris Rowland 2010-03-03T08:00:42Z 2010-03-03T08:00:42Z

<p>TheSky needs additional DCOM setup for a driver to run properly. Without this it could generate some sort of security error. It's possible that the settings for the Celestron driver are incorrect. There have been sporadic reports of problems but other people saying it's fine.</p> <p>I can't test because I don't have TheSky.</p> <p>Using POTH between TheSky and the Celestron driver does work round this problem.</p> <p>But it doesn't answer why the Meade driver doesn't work.</p> <p>If there's someone out there, with TheSky, with the problem with the Celestron driver and some familarity with using Regedit to collect and set registry data who wants to help then please contact me and we will try to work through what is happening and how to fix it.</p> <p>Chris</p>

http://astroanswers.org/questions/245/loading-celestron-unified-driver-5-0-14/246#246 Chris Rowland 2010-03-02T23:25:45Z 2010-03-02T23:25:45Z

<p>It's possible that this is the result of the additional DCOM setup that TheSky needs. Can you try running the Celestron driver from a different application and see if it works with that.</p> <p>A workround seems to be to run the Celestron driver through POTH. POTH can connect to TheSky and can also connect to the Celestron driver.</p> <p>I'd like to get to the bottom of this but I don't have TheSky, if you can let me know how this goes I might be able to see if I can modify the Celestron driver to avoid the problem.</p> <p>I'd guess that the reason it works if ASCOM 4.1 was installed first is because the DCOM setup done for that is OK and is not overwritten by the 5.0.14 upgrade.</p>

http://astroanswers.org/questions/223/why-update-to-5-5/224#224 Chris Rowland 2010-02-22T16:16:51Z 2010-02-22T16:16:51Z

<p>You get:</p> <ul> <li>Better serial port drivers</li> <li>Compatibility with Vista and W7</li> <li>64 bit support.</li> </ul> <p>So if you don't need these things there's no need to move.</p> <p>But drivers are increasingly likely to be written to need 5.5. This isn't done to be perverse, it's because of things like the 64 bit support becoming essential.</p>

http://astroanswers.org/questions/181/can-i-uninstall-an-innosetup-installed-driver-using-a-vs-setup-project-installer/183#183 Chris Rowland 2010-02-10T16:26:28Z 2010-02-10T16:26:28Z

<p>This answer on StackOverflow looks useful. <a href="http://stackoverflow.com/questions/2000296/innosetup-how-to-automatically-uninstall-previous-installed-version" rel="nofollow">http://stackoverflow.com/questions/2000296/innosetup-how-to-automatically-uninstall-previous-installed-version</a></p> <p>I would think that some sort of custom action could be run to run the inno uninstaller as specified in "UninstallString".</p> <p>At least it's a start...</p>

http://astroanswers.org/questions/177/ascom-platform-5-0b-installer-hangs-if-comma-is-decimal-separator/178#178 Chris Rowland 2010-02-10T12:04:02Z 2010-02-10T12:04:02Z

<p>People have reported that installations of ASCOM devices have problems where a comma is the decimal separator but I don't recall hearing of problems with Platform 5.0b itself. So I tried it as follows:</p> <ul> <li>Uninstall the 5.5.1 update</li> <li>Uninstall Platform 5.0</li> <li>Set the regional and language options to Portugese (Brazilian), it set the decimal separator to a comma.</li> <li>Install Platform 5.0b - no problem</li> <li>Install Update 5.5.1 - no problem.</li> </ul> <p>This seems to indicate that the problem isn't the comma separator. It doesn't say what it is, maybe somebody can suggest how we can get more information.</p>

http://astroanswers.org/questions/153/why-cant-my-driver-early-bind/154#154 Chris Rowland 2010-01-29T22:43:40Z 2010-02-06T15:51:19Z

<p>It's a bug in Conform. Peter knows and will be fixing it.</p> <p>And he's done so in Conform 3.0.0.17</p>

http://astroanswers.org/questions/158/how-can-i-make-starry-night-pro-5-work-with-my-meade-lx-200/160#160 Chris Rowland 2010-02-04T10:42:45Z 2010-02-04T10:42:45Z

<p>The Starry Night 5 installation instructions say that telescope control support has to be included when it's installed.</p>

http://astroanswers.org/questions/442/problem-installing-ascom-platform5b/443#443 Chris Rowland 2010-06-25T20:52:49Z 2010-06-25T20:52:49Z

Thanks Chris, that worked. Didn't know .NET wasn't cumulative. Also needed to install .net 3.5 for Optec drivers. JJ

http://astroanswers.org/questions/239/why-do-i-get-error-800a01ad-when-trying-to-install-platform-5-0/439#439 Chris Rowland 2010-06-13T15:52:42Z 2010-06-13T15:52:42Z

The OS being installed on drive D: may be significant so I've highlighted it.

http://astroanswers.org/questions/435/celestron-unified-driver/437#437 Chris Rowland 2010-06-11T12:58:03Z 2010-06-11T12:58:03Z

That's good, thanks for letting us know. If you mark the answer as accepted (the big tick) it will help others find it.

http://astroanswers.org/questions/428/ascom-utilities-net-implementation/430#430 Chris Rowland 2010-05-31T07:16:23Z 2010-05-31T07:16:23Z

This is only partially correct, I've edited my answer to show how to get a one line implementation with intellisense.

http://astroanswers.org/questions/428/ascom-utilities-net-implementation/429#429 Chris Rowland 2010-05-29T22:03:30Z 2010-05-29T22:03:30Z

It won't - but Dim strTest as String = New ASCOM.Utilities.Util will - or the equivalent in C# does.

http://astroanswers.org/questions/158/how-can-i-make-starry-night-pro-5-work-with-my-meade-lx-200/423#423 Chris Rowland 2010-05-27T07:02:54Z 2010-05-27T07:02:54Z

-1 This is irrelevant to the question and is somebody plugging his own product.

http://astroanswers.org/questions/405/autostar-497-upgrade/409#409 Chris Rowland 2010-05-19T07:57:30Z 2010-05-19T07:57:30Z

Thanks George, our LX200 is working at present but if it goes wrong we will be very interested in your fix. We are in the UK.

http://astroanswers.org/questions/380/i-cant-log-into-aa/381#381 Chris Rowland 2010-04-30T19:41:31Z 2010-04-30T19:41:31Z

It worked for me using a Yahoo Open ID earlier today but then it didn't, but after a few tries I got through. No magic, just persistence.

http://astroanswers.org/questions/112/meta-is-ascom-answers-only-about-ascom/113#113 Chris Rowland 2010-04-30T09:10:43Z 2010-04-30T09:10:43Z

As I see it this site is for &quot;How do I...&quot; questions rather than the &quot;Which is Better...&quot; sort of question. The former will tend to have a single, technical, answer while the latter tends to be more of an invitation to a discussion. Discussions seem to fit better into the social type of group with a much freer format that this more rigid format.

http://astroanswers.org/questions/370/telescope-pointing-state/371#371 Chris Rowland 2010-04-28T14:51:56Z 2010-04-28T14:51:56Z

I described this in the second half of my answer above - or at least tried to - the bit from &quot;To clarify the PierSide enumeration:&quot;.

http://astroanswers.org/questions/340/ascom-installation-problem/341#341 Chris Rowland 2010-04-26T07:34:02Z 2010-04-26T07:34:02Z

This is the normal COM registration using regsrvr for dlls. A search will give the exact protocol.

http://astroanswers.org/questions/319/why-am-i-getting-error-80040154/321#321 Chris Rowland 2010-04-12T15:35:19Z 2010-04-12T15:35:19Z

Sorry, I missed that you were using this. The error is a COM class not registered error but it's not clear which class, it could be the Chooser class or something that it is trying to call. A search on the error number shows that this is quite common but to only advice seems to be to find the dll that's not registered and register it. Some suggest using the SysInternals RegMon utility to find out what's going on.

http://astroanswers.org/questions/311/moveaxis-any-alternatives/315#315 Chris Rowland 2010-04-09T07:39:05Z 2010-04-09T07:39:05Z

Using the Slew command to do small nudges of a position doesn't work with the Celestron scopes because the slew commands do a fairly large backlash movement as part of the slew.

http://astroanswers.org/questions/317/celestron-unified-driver-disappears Chris Rowland 2010-04-09T07:36:42Z 2010-04-09T07:36:42Z

This doesn't normally happen so it must be something unexpected about your system. Can you give us some more information please: What operating system are you using? Is it 32 or 64 bits? What is the location used by the OS? What applications are you using? Do other drivers remain? If it's Vista or W7 what are the user security settings? Do you get any errors reported? Exactly what 5.5 version are you loading that works? AFAIK the only current upgrade is 5.5.1

http://astroanswers.org/questions/279/ascom-driver-for-celestron-does-not-support-park-on-synta-mounts Chris Rowland 2010-03-24T07:39:32Z 2010-03-24T07:39:32Z

A log would be useful, showing a normal slew and a failed park. Send it directly to me with a note saying what time you do the park so I can find it. There's also another question here with the Park tag that may be useful, use &quot;Celestron.Telescope&quot; for the scope Id.