Since I installed both apps on the android device, in "Setup Basic Encoder Systems" for Dec/Alt I had to change the +sign to -sign in V6 Pro to get the right direction of the cursor in the sky chart. There was no change in telecope design!
From now on in V4 Pro the cursor in the sky chart always goes to wrong direction, regardless of the "+" or "-" sign for "Alt/Dec".
In "Mount Type" the setting is "Alt-Az. Push-To" (for my dobson mount).
I think there must be a bug in the app because the installed V6 Pro has affected adversely the older V4 Pro.
thank you for your advice
Bernhard Englert
Date
Votes
14 comments
-
Bill Tschumy Bernhard,
There is literally no way this can happen. These are two separate apps and they have no interaction. I believe you that something has changed, but I cannot see how this could be related to the installation on SkySafari 6.
What kind of encoder system are you using? My guess is something got changed there somehow.
-
Bernhard Englert Hi Tschumy,
No change in encoder system design: US digital 8192 steps for Dec, US digital 10000 steps for AZ. Dec Encoder is always on the right side of the mount.
BDSC for bluetooth connection to Skysafari on android device.
-
Bill Tschumy I've asked the other developer if he can think of how this could happen. Stay tuned.
-
Bernhard Englert Hi Bill,
Perhaps, a part of the problem could be that V 6 Pro has a volume of 1.33 GB. I tried to fix the problem now by uninstalling and reinstalling V 6 Pro.
The first time installing Skysafari, I succeeded after several tries and two or three breakups . But now I had no more succcessful installations. When I
reached about 1.25 GB Google Play stops the download via WLAN due to to big data volume. My Android device is a Samsung S2 tablet.
Any Ideas what to do?
Bernhard
-
Bernhard Englert Finally I succeeded in reinstalling V6 Pro at the last moment. In a daytime test this brought the cursor back to right direction for Dec/Alt in when resetting the "+" and "-" sign to former settings in V6. Don`t know why.
thank you Bill
-
Bernhard Englert Hi Bill,
tonight I did a nightsky test with V6 Pro. Three times the cursor moved to wrong direction in Dec/Alt whatever sign I tried. Every try with exit and rerunning the program. The fourth attempt, the cursor took the right direction but now with wrong "-"sign.
Finally I opened V4 Pro, there the cursor always went south regardless of which sign I used.
It would be nice to fix the bug
Bernhard
-
Bill Tschumy I discussed this with Tim, the person responsible for the scope control code. He agrees that there is no way installing SS6 should affect SS4. We just don't have an explanation for what you are seeing.
I just tried changing the encoder sign on the shipping Android version. I am seeing it reverse the directions on-screen just like I would expect.
Have you checked the battery power on you basic encoder system. Maybe low power is causing the strangeness.
-
Bernhard Englert Hi Bill,
now I´ve changed the powerbank ( XT Power 20000QC2, full powered!) and tried a brand-new lead accumulator.
Sadly no change of the random behavior. After several attempts I got the right cursor movement in Dec/Alt direction, unfortunately with wrong "-" sign.
best regards
Bernhard
-
Bill Tschumy Bernhard,
I'm not sure what to tell you. We can diagnose this without having your hardware. No one else has reported any strange behavior like this and we can only assume it is something happening in your hardware setup. Is there some way you can do a "reset" on your DSC?
Bill
-
Mark Morawski Bill,
Same problem with SS6. Changing the sign in the program has no affect on the movement of the scope. I have one axis that is incorrect with basic encoders, get auto doesn't work manual doesn't work. This is a coding issue in that sign change should impact the direction of scope movement in the program.
Second problem is that the prior setting do not release with you connect / disconnect scope. I get the error current scope position is to close or something to that affect. when I disconnect, it should reset all alignment parameters it doesnt.
Using Basic encoders setting UA doublestar mount hooked too beti, beti is just a pass through to Blue tooth.... have bought your program from the first release this would really be nice to get fixed.
-
westland I'm currently running into the same problem. The program was working perfectly until tonight, when both Alt and Az movement was the wrong way. Changing the signs seems to have no impact.
-
westland In addition, I have run this on both an S10 phone and an S4 tablet, with the same problem. No changes to the parameters have any effect on the direction of the encoders.
-
westland Resolved!
My problem was that the direction of the Alt/Az axis on my dob (HO14") using the SkyHub-B box, and Basic Encoder setting on SS6, were moving the cursor the wrong direction on SkySafariPro 6 (SS6), no matter whether I specified +8192 or -8192 ticks on either axis. So I was blaming SS6 for the problem, right.
It turns out I have a bad cable, and changing the cable rectified the problem.
Here is my explanation of what happens. When you lose one of the two channels from a quadrature encoder (what is used on most amateur scopes) the scope knows 'how much' to move, but not which direction. The code disk inside a quadrature encoder contains two tracks usually denoted Channel A and Channel B. These tracks or channels are coded ninety electrical degrees out of phase, and this is the key design element that will provide the quadrature encoder its functionality. In applications where direction sensing is required, a controller can determine direction of movement based on the phase relationship between Channels A and B. When the encoder is rotating in a clockwise direction its signal will show Channel A leading Channel B, and the reverse will happen when the quadrature encoder rotates counterclockwise. Apart from direction, position can also be monitored with a quadrature encoder by producing another signal known as the “marker”, “index” or “Z channel”. This Z signal, produced once per complete revolution of the quadrature encoder, is often used to locate a specific position during a 360° revolution.
Anyway, the cable was old and both axes had problems (not always at the same time) so the problem was sporadic.
Moral: before blaming the software, check your cables and encoders.
-
Keiron Smith Thank you for sleuthing out the solution, James!!!
Please sign in to leave a comment.