<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/eq-mod/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/eq-mod/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 27 Aug 2023 09:29:58 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/eq-mod/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Add Autohome to EQASCOM. </title><link>https://sourceforge.net/p/eq-mod/feature-requests/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be very useful to a lot of people to have an Autohome feature in EQASCOM in order to use the homing sensors of the latest SW mounts. I know it has been asked before on the yahoo group and dismissed. It's been several years now since SW added those sensors to their mounts and it could be really useful for the people doing full remote.  Maybe it is time to add it to EQASCOM ?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Antiath</dc:creator><pubDate>Sun, 27 Aug 2023 09:29:58 -0000</pubDate><guid>https://sourceforge.netbba99f646c14258e9e742d2539a2407eb61acc62</guid></item><item><title>#14 PierSide reporting in interface</title><link>https://sourceforge.net/p/eq-mod/feature-requests/14/?limit=25#c31f</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ascom specifies only two &lt;strong&gt;pointing state&lt;/strong&gt; situations:&lt;/p&gt;
&lt;p&gt;PierEast&lt;br/&gt;
PierWest&lt;/p&gt;
&lt;p&gt;You can add the pointing direction of a telescope&lt;/p&gt;
&lt;p&gt;PierEast, pointing West&lt;br/&gt;
PierWest, pointing East&lt;/p&gt;
&lt;p&gt;see fig 3&lt;/p&gt;
&lt;p&gt;EQMOD display indicates &lt;strong&gt;physical side&lt;/strong&gt; of pier. That should have only&lt;/p&gt;
&lt;p&gt;PierEast  (yellow area 4)&lt;br/&gt;
PierWest (purple area fig 4)&lt;/p&gt;
&lt;p&gt;If you add the telecope pointing direction you get four situations. Not two! I have carefully added them to fig 4. See this custom figure:&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">han.k</dc:creator><pubDate>Sun, 12 Feb 2023 09:42:59 -0000</pubDate><guid>https://sourceforge.net9e45cd7e21013d059b0b9165375f7c456710b13f</guid></item><item><title>PierSide reporting in interface</title><link>https://sourceforge.net/p/eq-mod/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If EQMOD is reporting the physical side of pier instead of the "pointing state" then it would be more correct to display four different situations instead of two:&lt;/p&gt;
&lt;p&gt;PierSide=West, telescope pointing East&lt;br/&gt;
PierSide=West, telescope pointing West&lt;br/&gt;
PierSide=East, telescope pointing West&lt;br/&gt;
PierSide=East,  telescope pointing East &lt;/p&gt;
&lt;p&gt;See&lt;br/&gt;
&lt;a href="https://download.ascom-standards.org/docs/SideOfPier" rel="nofollow"&gt;https://download.ascom-standards.org/docs/SideOfPier&lt;/a&gt;(1.2).pdf&lt;/p&gt;
&lt;p&gt;Han&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">han.k</dc:creator><pubDate>Sat, 11 Feb 2023 20:12:33 -0000</pubDate><guid>https://sourceforge.net695543b878cd73ab0e95834ff329638622e476a4</guid></item><item><title>#13 Move to Github</title><link>https://sourceforge.net/p/eq-mod/feature-requests/13/?limit=25#81a1</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for the offer but given the nature/maturity of this project I see no need to move from sourceforge at this time.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Shillito</dc:creator><pubDate>Sun, 06 Mar 2022 10:35:28 -0000</pubDate><guid>https://sourceforge.netc6f2a9fee1a1ed9dec60588584796ec5e4aece37</guid></item><item><title>Move to Github</title><link>https://sourceforge.net/p/eq-mod/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I propose to move this project to Git / GitHub.&lt;/p&gt;
&lt;p&gt;Please let me know if you want to do this and I will do the work.&lt;/p&gt;
&lt;p&gt;Advantages:
* More developers
* More visibility
* Better source control
* Automatic build system
* Modern
* More Developers&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wim Jongman</dc:creator><pubDate>Fri, 04 Mar 2022 17:05:01 -0000</pubDate><guid>https://sourceforge.netea7debb9e3f25299bcd4bbd7af64f645d8c9348d</guid></item><item><title>ASCOMPAD Reconnect to mount on startup</title><link>https://sourceforge.net/p/eq-mod/feature-requests/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;feature request:&lt;/p&gt;
&lt;p&gt;would be nice that ASCOMPAD would have an option to reconnect to the last connected  mount upon startup. I use ASCOMPAD directly with my Synscan App ASCOM driver and everytime i restart the PC i then have to go into device/mount/connect "OK".&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">robert hasson</dc:creator><pubDate>Thu, 29 Apr 2021 12:24:00 -0000</pubDate><guid>https://sourceforge.netd2dd2d33e2213fbae007b9835ead9755b94cc465</guid></item><item><title>#11 Gamepad control</title><link>https://sourceforge.net/p/eq-mod/feature-requests/11/?limit=25#e246</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Chris,&lt;/p&gt;
&lt;p&gt;Thanks you for the explanations!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Boyang Liu</dc:creator><pubDate>Tue, 16 Jun 2020 19:05:54 -0000</pubDate><guid>https://sourceforge.net1d73d6cc5eabb8b866199cdceb1019e61362a9eb</guid></item><item><title>#11 Gamepad control</title><link>https://sourceforge.net/p/eq-mod/feature-requests/11/?limit=25#ea38</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This is something we have considered, discussed and tested in the past but sadly was found not to be practical. The issue is the wide range of slew speeds the mount can have move at and the relatively small amount of deflection on a joystick. Yes the software can detect small adjustments if the joystick but that doesnt' mean that the user will be capable of operating the stick with the precision that the softeare can read it. In practice we found it was just too easy to accidentally move the stick a little to far and loose your target completely (especially if wearing gloves on a cold winters night). Typically the joystick interface is used for fine positioning or targets not for satelite tracking so what we've done is implemented a two speed option where a slight deflection will move at your "preset 1" speed whilst a full deflection will move at whatever rate you have currently selected.&lt;/p&gt;
&lt;p&gt;Note that typically these mounts are not best suited for tracking satelites due to the "low resolution" of the very fast slew speeds - wha tI mean by that is the mount communication protocol acts to quantise the number of actual rates achievable - and any speed variation is not "continuous" so the mount will "jump" at each speed change - the mount firmware also requires that the motors are actually stopped prior to any "fast speed" change.&lt;/p&gt;
&lt;p&gt;Chris.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Shillito</dc:creator><pubDate>Tue, 16 Jun 2020 09:53:38 -0000</pubDate><guid>https://sourceforge.net6f0edeb6307b230fa73c17e089ce3cb65a7abd33</guid></item><item><title>Gamepad control</title><link>https://sourceforge.net/p/eq-mod/feature-requests/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Not sure whether this is the right way to post questions and suggestions but here are my thoughts:&lt;/p&gt;
&lt;p&gt;My joystick (T.16000M) has many different levels of pressure responds, and clearly EQMOD knows that, since during gamepad calibration, the number changes continously from 0 to 65535 when I gradually bend the stick from one direction to another.&lt;/p&gt;
&lt;p&gt;But when I use the stick to slew the mount, seems that the slew action is only triggered when I press to somewhere like +30000 or -30000 (for convenience, assuming 0 at center), and it only does slew/no slew , and when it slew, it slew at a constant speed, instead of slewing at different speeds given different stick pressure.&lt;/p&gt;
&lt;p&gt;In principal when I have different levels of pressures, I do not need other way to set the slew speed, the slew speed shall directly come from how much or how hard I bend the stick. In this way, the control could be much easier and more flexible.&lt;/p&gt;
&lt;p&gt;Why I raise this: I want to track satellites with a joystick, and I want to fully utilize the capability of the hardware to make the tracking easier.&lt;/p&gt;
&lt;p&gt;Is there anything I missed that caused me asking something that is already solved?&lt;/p&gt;
&lt;p&gt;Cheers&lt;br/&gt;
Boyang&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Boyang Liu</dc:creator><pubDate>Mon, 15 Jun 2020 23:23:11 -0000</pubDate><guid>https://sourceforge.neta1b6bb2487052a689ef6c77d6fd64e3444e56a5c</guid></item><item><title>#10 EQMOD Opening without Scope Connection Fix </title><link>https://sourceforge.net/p/eq-mod/feature-requests/10/?limit=25#1989</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;As I've tried to explain EQMOD is not shitting itself down - it is being commanded to close by the client application you are using. Use a different client, such as the tooolbox application supplied with EQMOD, and you can happy open up EQMOD with the mount disconnected. So there really is no need for anything to change.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Shillito</dc:creator><pubDate>Wed, 31 Jul 2019 08:07:54 -0000</pubDate><guid>https://sourceforge.net0a2e720c1fbfc7724bbdeb57fca752792c56affd</guid></item></channel></rss>