- 38
- 39 820
SkyTrack
Canada
เข้าร่วมเมื่อ 8 ก.ค. 2020
Horizon File Import with SkyTrack v1.8.3
Import horizon files into SkyTrack
Phone app for creating horizon files by Ryan Kinnett rkinnett.github.io/gyrocam/
heavenscape.com
Phone app for creating horizon files by Ryan Kinnett rkinnett.github.io/gyrocam/
heavenscape.com
มุมมอง: 552
วีดีโอ
SkyTrack v1.8.0 - New Orbital Elements File Formats
มุมมอง 330ปีที่แล้ว
The old standard "TLE" file format for orbital elements will soon be inadequate for new satellites. Starting with v1.8.0, SkyTrack can use the new standard - OMM XML. For more information about the issue and new formats see celestrak.org/NORAD/documentation/gp-data-formats.php heavenscape.com
New TLE Retrieval Method in SkyTrack v1.7.9
มุมมอง 394ปีที่แล้ว
Beginning with v1.7.9 SkyTrack uses a new query method to retrieve satellite orbital elements from celestrak.org heavenscape.com
International Space Station Transit with the Sun
มุมมอง 797ปีที่แล้ว
A review of the transit feature in SkyTrack. My first attempt at capturing a solar transit of ISS. heavenscape.com
Technical Review of SkyTrack and ASCOM Driver Requirements
มุมมอง 995ปีที่แล้ว
This is a technical review of SkyTrack and the ASCOM methods and properties it uses for satellite tracking and custom tracking of comets, asteroids and other objects. heavenscape.com
Tracking Comets with PHD2 and SkyTrack v1.7.4
มุมมอง 1.4Kปีที่แล้ว
SkyTrack now has an integration feature with PHD2 sending custom tracking rates to make use of the PHD2 lock shift feature for comet tracking.
Tracking Comet C/2022 E3 (ZTF) with SkyTrack
มุมมอง 518ปีที่แล้ว
A quick review of finding and tracking comets with SkyTrack.
SkyTrack v1.7.2 New Features
มุมมอง 7632 ปีที่แล้ว
A review of new features with SkyTrack v1.7.2 heavenscape.com
Different Tracking Methods with SkyTrack
มุมมอง 1.3K2 ปีที่แล้ว
SkyTrack can track satellites with different methods as well as custom tracking for spacecrafts, planets, comets and asteroids. This video is an overview of tracking methods for those that are relatively new to use of the software. Oops! At 21:46 and 21:54 I meant to say "comet" not "satellite". heavenscape.com
SkyTrack v1.7.1 New Features
มุมมอง 3752 ปีที่แล้ว
New features review of SkyTrack v1.7.1 heavenscape.com
SkyTrack v1.7.0 New Features
มุมมอง 3792 ปีที่แล้ว
The new features of SkyTrack v1.7.0 are reviewed. For more details on the new SkyWatcher interface see th-cam.com/video/nUUAxPm7pjc/w-d-xo.html For more details on JPL object tracking see th-cam.com/video/L8nqFmo9TF0/w-d-xo.html https:/heavenscape.com
Tracking James Webb Telescope with SkyTrack v1.7.0
มุมมอง 7442 ปีที่แล้ว
Explanation of the final version of JPL object custom tracking in SkyTrack v1.7.0. Examples of tracking are shown with images of the James Webb Telescope. heavenscape.com
Satellite Tracking with SkyWatcher Mounts - New Interface in SkyTrack 1.7.0
มุมมอง 3K2 ปีที่แล้ว
Beginning with SkyTrack v1.7.0 there is a new legacy interface for SkyWatcher mounts. This overcomes previous issues with changing fast slew rates on-the-fly with SkyWatcher. SynScan Pro app v2.0.12 and mount firmware 3.39 or higher are required. Also required is a generation 3 SkyWatcher motor controller board - upgrades are available if your mount has an older board. Many thanks to SkyWatcher...
Track the Artemis Spacecraft with SkyTrack v1.6.9 Beta 1
มุมมอง 5582 ปีที่แล้ว
A beta version of SkyTrack is released today in anticipation of the upcoming launch of Artemis I. This is a test version of the new capability to download ephemeris data from the JPL Horizons website and set custom tracking rates in SkyTrack. heavenscape.com
New Features in SkyTrack v1.6.8
มุมมอง 3512 ปีที่แล้ว
A review of the new features in SkyTrack v1.6.8 heavenscape.com
Retrieve Object Data from SkyTrack in N.I.N.A.
มุมมอง 2792 ปีที่แล้ว
Retrieve Object Data from SkyTrack in N.I.N.A.
Iridium 42 Satellite Flare (NORAD 25077)
มุมมอง 3012 ปีที่แล้ว
Iridium 42 Satellite Flare (NORAD 25077)
Iridium 110 (NORAD 43481) Satellite Flaring
มุมมอง 6782 ปีที่แล้ว
Iridium 110 (NORAD 43481) Satellite Flaring
Applying TLE Filter Files for a Subset of Satellites (no audio)
มุมมอง 1712 ปีที่แล้ว
Applying TLE Filter Files for a Subset of Satellites (no audio)
Finding International Space Station Transits with Moon, Sun or Planets
มุมมอง 3543 ปีที่แล้ว
Finding International Space Station Transits with Moon, Sun or Planets
iOptron Az Mount Pro - Testing Satellite Tracking
มุมมอง 9183 ปีที่แล้ว
iOptron Az Mount Pro - Testing Satellite Tracking
Creating TLE File Filters with the Satellite Information Database - SkyTrack (Demo)
มุมมอง 2043 ปีที่แล้ว
Creating TLE File Filters with the Satellite Information Database - SkyTrack (Demo)
What Satellite Was That? Identify satellites with SkyTrack.
มุมมอง 3243 ปีที่แล้ว
What Satellite Was That? Identify satellites with SkyTrack.
International Space Station / Lunar Transit
มุมมอง 1.6K3 ปีที่แล้ว
International Space Station / Lunar Transit
Can you track ISS with this feature?
Absolutely!
@@brentboshart4624 Awesome! This might be what gets me to finally order one.
do you know for sure (ro somebody) if it works with Star Adventurer Gti? I dont know hot to check which borad do i have in my GTI, do i have to open it to check it? thanks in advance
anyone?
Hi!! My AzEq6 mount makes strange sounds. The engines make certain sounds that I have never heard. Is something wrong or is it because of the different speed at which it moves?
Thank you for all your hard work. I have a quick question. Is your app/program compatible with OnStep systems? Kind regards, Damo
Do a search at onstep.groups.io/g/main/topics I believe they have it working now.
What caused this flare?
I have the doc for ZWO's AM5 mount that exposes the command for variable speed for both axes. Would you be interested in adding support for these mounts? I will be happy to test and troubleshoot if you can write a custom driver for them.
Thank you, this is really helpful! Just a quick question - my iPhone compass always shows true north. Do I still need to input the magnetic declination?
If it shows true north then no need for magnetic declination.
Thank you very much for all your time in this wonderful project! qq.. reading in "mounts and interfaces" seems I can use legacy --> "Nexstar/CPC ALT/-AZ" for my Nexstar 130SLT ? .. its not CPC but is AltAz. does drive the mount , just wondering about accuracy. Thanks again
Does this program play nice with 10um mounts?
Does this work with Skyadventurer GTI mount?
I cant get it to connect to my star avdenturer gti
@@RM-il5bv bummer
any luck with star advenurer gti? did you try it?
@VitoPastore nope, didn't try it, so can't say if it works or not with the GTI
Yes
Will this software eventually be able to track a rocket launch?
Look up astronomylive. He has a program to do this
I would like to use this to point an antenna for satellite comms. While I do have astrophotography gear I could piggyback that I could use to ensure my alignment was good, I don't have that luxury when the satelittes are eclipsed or during the day. Is a rough polar alignment good enough for those cases? That may be more of a radio question and I understand if you don't have the answer offhand yourself. Was more just curious than anything.
I didn't even know there was firmware on my skywatcher mount I could update.
Will my AP Mach 1 work in continuous tracking mode?
Yes, I would expect it to work as well as my Mach2 and best results using the latest version of APCC Pro.
That's really cool. Would it look less blownout if you were observing it by eye?
Good day. Thanks for your brilliant program. How can I slew to GEO satellites? Unfortunately pushing "Start satellite Tracking" it doesn't slew.
Hello, Great video. I do not see the update to my Live View window after saving all my Viewing Limits - Elevation. I need your help when you have the time.
Email me your .hrz file to the email addreess on the website.
To clarify, with this release the limits only show in the sky view when using a horizon file, not with older viewing limit entries.
Can geostationary satellite's create a periodic repeating stationery reflective flash similar to a distant camera flash visible to the naked eye from earth without a telescope?
Hi man, I think I understand exactly what you are talking about. Just saw the same thing last night and I wonder if it was a geostationary satellite... How much time did the repetitive flash last?
@@LeDarwiniste I've seen it or them on a few different occasions over the years, in different locations of the sky. At different times of the year. Sometimes it's out there in the same spot every night for a few weeks other times just there for a couple of hours then disappears. It's the weirdest thing I know. Recently it's only a short duration maybe 5-10 seconds. Other times it's had longer duration between flashes up to 10-15min... Tempted to spend the money to build my own digital Astronomy telescope with night vision capabilities. See if I can get a good look at it an see if there is anything hiding in its "off" phase. From other research I've done, geostationary satellite's are to small and to far out to see with the naked eye.
Hi, Thank for the video. What is the LST in mount position/status?
Local sidereal time. www.localsiderealtime.com/whatissiderealtime.html
Hello, good software. Only automatic corrections are missing. Maybe in the future it will come to this.
Awesome.. Can this somehow be adapted to rocket launches and airplanes?
Cool. Anyone know if Losmandy G11 will work?
Thanks for the addition. Useful feature!
Hello, I saw your video about mount and ascom driver requirements for smooth satellite tracking. I currently use an EQ8R pro form my astrophotography alongside GSS. I wouls love to use that set up to try and capture the ISS. Do you have any idea weather my ascom driver works well with the software ??
Yes, using the latest SynScan Pro app and the SkyTrack "legacy" interface it will work great. See th-cam.com/video/nUUAxPm7pjc/w-d-xo.html
@@skytrack6932 This is amazing news, I'm slowly wrapping my head around the process. I'm thinking of using my EdgeHD 9.25 at native FL with my asi2600mc to perform initial alignments and the pointing medel and then switch to a higher FPS planetary cam and possibly use a barlow. I appreciate your swift response.
This is so fantastic, but I can't help but think I missed a video or a Read_me file that I should have seen or read. Am I to be at my polar aligned telescope while following these steps? I got to the mount calibration step just fine, but if I missed any instructions that directed me to set up my telescope, then I probably missed some other things as well. Thanks again, I just want to make sure I get set up right the first time. - "Dustin"
Hi Dustin. You do need to do through the normal setup with your telescope, polar alignment and star alignment. When that is complete then start by doing a "slew to" some bright stars. If you are not seeing the bright stars centered in your field of view then of course you will not be able to see satellites either because of alignment issues.
The software version number is 1.7.8 however it shows that a newer version 1.7.7 is available.
Haha, you caught me! The website is currently configured for v1.7.7 as the newest version and I am using a beta version of v1.7.8.
Was looking forward to using this however the SYnscan Pro app I have failed to connect to the mount on it's USB serial port. I know the USB serial port works as I can drive it using the ASCOM driver (but I only get bunnyhops with that). Annoyingly, my mount is the AZ-GTiX which has Wifi, and if I connect the Synscan App using the network it all works perfectly. But then I'm stuck with a PC that no longer has an Internet connection because the mount acts as the "router" but obviously only supports itself.
In the SynScan Pro app, under "Settings"-"SynScan Wifi" you can setup the mount to use "Station Mode" and to use your home WIFI
@@skytrack6932 Hi, thanks for the reply. I did try to get it into station mode but it seems Skywatcher has removed it from the latest version of the SynScan Pro App. I did find the section about Station Mode in the online PDF manual for the mount but the paper one that came with the mount does not mention it at all. I have to admit, not the first time I've been frustrated with SW's software. Great mounts, shame about the utility software support
@@kirkhamandy I'm using App Pro 2.3.3 and it is there, working fine.
@@skytrack6932 Ah, I see, it was greyed out. I needed to connect in Access Point Mode for it to become "ungreyed" out and then Station Mode can be enabled. Thanks for your help! Now I just need to get WiFi down to the end of my garden :)
Hey hi....Have you tested it Practically? Is this will track accurately? Thanks!
It tracks very well. It is critical though that you perform an accurate star aligment with the mount.
@@skytrack6932 great thanks so much!
@@skytrack6932 You mean aside from perfect PA, also do a star aligment?
Congrats on your first transit! You did a pretty good job actually; with my first transit I think I got my focus pretty good, but my exposure time was way to long so it didn't look half as good as yours. Maybe you could add a simple tool to estimate correct exposure: take satellite angular velocity, enter your scope focal lenght and camera pixel size (which basically gives you angular resolution), and you can calculate how long would it take for the satellite to move one pixel - that would be a reasonable exposure time. I actually have a spreadsheet to do exactly that when I try to capture a transfer. With Sun transit you can go pretty low as you have plenty of light, but with Moon or especially planets there have to be some compromises. One other idea I have, that you could maybe think of adding in the future: generate precise ground track of a satellite (optionally with specified offset) the same way you do it for transit lines - I recently learned that there are some satellites that use visible laser eg. for cloud cover measurement and if you know precisely where and when to be, you can actually see that laser beam shine on you if you look up :)
Something I forgot to mention in the video, is the “T+Epoch” parameter in the “Satellite Data” frame. The epoch is the time of reference for which the orbital elements are derived so it gives you an idea of how fresh the data is. Of course, even if it is reasonably current an orbit adjustment could have just been made. Anyway, “T+Epoch” is the age of the data is expressed in days. When I got permission to use direct links from Celestrak.com for TLE files, they requested that the software has some mechanism to prevent a user from continually downloading files and putting undue resource on their servers. To honour that request, SkyTrack will not download a new file if the current file is less than one hour old. For transits, you may want to work around this by deleting the previous TLE file in the skytrack folder so a new one will download. Doing that should be the exception though.
Congratulations for your transit!! Once I tried to understand how often the TLE of the ISS were updated and to what I noticed the TLE were updated once or twice a day. And I met at a star party someone who works in collaboration with NASA about a project he has with the ISS, long story short, he told me that they perform manoeuvres to slightly change the trajectory of the ISS several times a day but the TLE don't get publicly updated every time they do it. It might be why your transit was not perfectly were you expected it. I also noticed that sometimes, ISS tracking is very precise and easy, and sometimes it's a bit off for "no reason".
Excellent demonstration! Will be trying this out with my iOptron AZ Mount Pro too.
Fantastic. I have a few coming up.
This software is awesome. Any plans to make it track planes or maybe rocket launches?
Awesome! Do you believe the new ZWO AM5 mount is able to track? Thanks
I have heard reports that the AM5 is able to track, however make sure you are using the latest release of the ZWO ASCOM driver. Early releases had some issues.
Super interesting. I know it's obvious to those who have looked at ascom on more than just the surface level, but I've had multiple conversations with newer mount owners hadn't grasped the concept of ascom being a platform and ascom drivers *not* being made by ascom but instead by the manufacturer or whoever else, which leads to implementation inconsistencies. Just thought it worth mentioning. I'm also curious what command set some iOptron alt/az mounts have that the EQ counterparts don't have (there must be enough difference to make a legacy driver worthwhile.) I recently got a CEM40EC, knowing it wouldn't work with continuous tracking, as far as I know. Interestingly, the ascom calibration fails to run at all, immediately failing when I try to run it. I didn't spend a lot of time debugging but it was curious. Anyway I appreciate all of your information and continuous support and enjoy SkyTrack immensely! I'm just using my old AVX for it still ;)
iOptron is different again. Starting with the Az Mount Pro they implemented a "special mode" for satellite tracking capability. It is neither ASCOM or their regular command language. They plan to implement the same "special mode" for their equatorial mounts but there is no development timetable established yet.
@@skytrack6932 oh wow, interesting thanks for the insight!
Thanks for that video, I didn't realise there's THAT many requirements for actual satellite tracking that mount has to meet. One thing you could've probably mentioned is that some mounts (like older SW mounts for example) have a "speed limit" for continously updating MoveAxis speed, and above that they have to stop before they can actually change that speed (my ongoing problem with AZ-EQ5, still waiting for that promised firmware update :D) - and with that they will track fine only if satellite is moving slower that that speed limit in each axis.
Love Skytrack. A big thanks.
wish i had found your video before i tracked the comet manually :)..but this would help certainly next time.
I tried it out and it works! I did my usual routine with APT, sync the mount and connect with phd2, calibrate phd2, goto C/2022 E3 (ZTF), open skytrack, download ephemerides and connect with phd2. The Ra/Dec rates are automatically transfered to phd2, very nice. Now I started taking 180s exposures for 1h30m. On the first picture the comet was centered and after 1h30m the comet was still perfectly centered, amazing.
I used a plugin for N.I.N.A. called Orbitals which besides other things also connects to the comet tracking feature of PHD2. This worked really well on C/2022 E3 (ZTF) till late in the night. Upon looking into PHD2, I saw that the RA value was set to 5000arcsec/hr and did no longer go higher. This seems to be the current limit of PHD2. As far as I understand it, SkyTrack's custom tracking doesn't have such limits?
SkyTrack does not set limits but each mount/ASCOM driver will have its limits. Both pulse guiding (PHD2) and RightAscensionRate/DeclinationRate properties (SkyTrack with ASCOM Custom tracking) are meant to correct sidereal tracking due to peridioc error or polar misalignment. So the limits will probably be something less sidereal rate. I'm not sure at this point the actual limit that PHD stipulates. I noticed the Comet Tracking dialog in PHD2 never shows higher than 5000 arsec/hr but if I send it rate higher than 5000 and then ask for the current rate it will report back the higher rate. I need some more clear skies for additional testing.
When you click on 'Start Satellite Tracking' and the circle turns green to indicate that it 'is in the FOV'. For that to actually work, the mount would have to be very well star aligned? How about polar alignment? It's probably hard to say, but do you think it's worth a try using the C9 on an AVX mount? As far I remember, slewing to a target after doing the two star alignment was never spot on. Sometimes the target wasn't even in the FOV. Since I started using N.I.N.A., I don't bother much with alignment as it frames the target by doing plate solves and for that a rough alignment is sufficient. Thank you.
It does not indicate the exact FOV but where the mount is pointing. Precise pointing is essential. SkyTrack has the ability to platesolve an entire satellite pass ahead of time for a highly desirable pass like ISS. Have a look here. th-cam.com/video/RYYW8UDt1M0/w-d-xo.html
@@skytrack6932 Thank you very much. That feature looks very handy. Of course the ISS is my desired target in the end. Unfortunately it won't pass at my location until mid march. Well it does, but all the passes going over 20 deg alt are at like 04:50 in the morning :/ But hopefully after weeks of clouds I'll have a chance to test it on a satellite sometime before that.
This is rather insightful. A few nights ago I used JPL horizons dRA*cosD, d(DEC)/Dt data with phd2 but was rather disappointed. It didn't keep up with the motion. I though maybe it was too fast for the default 0.5x guide rate; but now I see in your video the RA Rate is not the same dRA*cosD value I can pull up for February 2nd. So my question is, is there a different field I need to filter for, or do I have to do some kind of conversion of dRA*cosD? I also get similar numbers from the minor planet center ephemeris.
JPL multiples dRA by the cosine of the declination to calculate a linear rate in the plane of the sky. We don't want that with our astronomy mounts so divide the value (dRA*cosD) by the cosine of the declination (cosD) to just get dRA.
@@skytrack6932 Thank you very much! Can you refer me to more documentation or discussions about this. I couldn't find much about it.
@@Core5 I don't know of any references but am always happy to answer any further questions if I am able.
@@skytrack6932 Much obliged. I should mention for the sake of others who come by this. But I found the MPC ephemeris does provide the correct rate when 'Separate R.A. and Decl. coordinate motions' is selected.
So if custom tracking is grayed out I can always connect with phd2 and track on a star. Do you have to enter the RA/Dec rates manually?
No you do not have to enter the rates. After downloading the JPL file with the rates and the integration between SkyTrack and PHD2, Skytrack will automatically keep PHD2 updated with the current rates.
@@skytrack6932 Thanks, I will give it a try as the comet is still visible.
Thank you so much for this fantastic new feature! I had previously had to track the comet by locking onto the comet itself via PhD2. Now I can use multi stars tracking to get a much better performance. I am also amazed at how often you crank out new features.
I assume that this would work for other targets beside comets... Would that be correct? Thanks
It sure would! There would be a limitation how fast the object is moving as PHD2 is only using pulse guiding. It would work for sure for asteroids but not for low orbit satellites as they move too fast. I plan to do a similar comparison of tracking the James Webb space telescope whenever I get some clear skies.
@@skytrack6932 Thanks, That would be the target types I had in mind... Chandra, the Tesla, and the planets... Awesome!
This looks like a great piece of kit! However, when I connect to my CGEM mount the Skytrack sidereal time differs from the mount sidereal time by about 14 minutes. Is it best to fix this in Skytrack, or to change the mount's hand controller to be the same as Skytrack? Where does Skytrack get its local sidereal time? Thanks! :)
Sidereal time is calculated from local time, UTC Offset (Time Zone) and longitude. Double check your longitude entry for the site in SkyTrack and make sure you have the correct direction (E/W). If you cannot solve the issue send me an email to the address on the website.
PHD2 does a great job of comet tracking. Comparisons with ASCOM Ra/Dec rate properties comet tracking may be difficult as the comet nucleus may not be perfectly spherical.
Awesome! Something to think about.. PHD2 has a comet autoguiding mode which requires comet drift rate information, and it serves a TCP socket server which planetarium apps can use to send this information to PHD2. CDC, for example, implements this link. I see that SkyTrack queries comet RA and dec drift rates from JPL, so the data is available in SkyTrack. Please consider adding a "Send comet drift rates to PHD2" button or something like that. Granted, users can just view the downloaded ephemeris and manually transcribe rates into PHD2, but the drift rates change by a couple of percent per hour around closest approach, making it cumbersome to keep up with manually. Then again, this may open a can of worms if you have any interest in broader integration with PHD2, and by the way that API is not well documented as far as I can find.
I am surprised at how few mounts support the ASCOM properties RightAscensionRate and DeclinationRate for custom tracking rates. I assume that PHD2 for comet tracking would be using pulse guiding. That is an approach that I could look at.
PHD2 does use pulse guiding for comet tracking. Comet guiding mode doesn’t technically guide on a comet, but rather guides on nearby stars but continually adjusts where in the guide camera view the star should be found according to the specified rates. Then it uses pulse guiding to keep the star centered in a moving target box.
@@rkinnett I never know which RA/Dec value to choose. In the ephemeris downloaded from Skytrack there are 3 Ra/Dec values: 'R.A._____(ICRF)_____DEC' 'R.A.__(a-apparent)__DEC' 'dRA*cosD d(DEC)/dt', so which one goes into phd2?
@@indysbike3014 great question. I have no idea. I’m also not certain if “RA*cos(D)” is what PHD2 needs or if we need to undo (divide by) the cos(D) part. Looking into it..
@@rkinnett Yes, without knowing the internal workings of PHD2 I would say divide "RA*cos(D)” by the COS(declination). I do when using ASCOM RightAscensionRate. I found what I need for the PHD2 api. I'll give it try with SkyTrack and JPL data.
Do I need to enable custom tracking for long exposures like 2min? I want to image comet c/2022 e3 ztf.
It may depend on the arcsec/pixel of your imaging setup. For example, right now the comet is moving at a declination rate of 0.09 arcsec/sec. So with a 2 min exposure (120s) it would move in declination 120x0.09=10.8 arcsec. My imaging setup is 1.2 arcsec/pixel so without custom tracking I would see a shift in declination of 10.8/1.2 = 9 pixels. (Arcsecs per pixel = (206.3 * camera pixel size in uM) / focal length of scope in mm)