Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1
AstroEQ Support / Battery power options
« on: May 10, 2021, 01:51:50 »
Hello,
I am looking to get a more OTA focused. At the present, I am at spagetthi junction with AstroEQ. I would like to mount power to the OTA. Which power bricks work with AstroEQ?
I have a hefty brick powering it at the present, (within specs). It works well, But...
Amps to drive the motors are what are required. I am looking at the Pegasus Astro Pocket Powerbox Advance. To me, I think 1 12v 5A link is all that is needed. Thoughts?
What other options are available?
I am looking to get a more OTA focused. At the present, I am at spagetthi junction with AstroEQ. I would like to mount power to the OTA. Which power bricks work with AstroEQ?
I have a hefty brick powering it at the present, (within specs). It works well, But...
Amps to drive the motors are what are required. I am looking at the Pegasus Astro Pocket Powerbox Advance. To me, I think 1 12v 5A link is all that is needed. Thoughts?
What other options are available?
2
Mount Support / Re: AstroEQ out of sync?
« on: September 07, 2020, 05:50:11 »
Hello,
I resolved the loose pulleys. However, I think I have different problem. I have the same ratio 3:1 but 36:12 and 30:10 are different. The motors are the same. This looks like a design issue. Back to the drawing board.
Using this site for a ballpark answer, I found 36:12 is slower than 30:10 by 66.7%. This explains that issues that I am having. Less teeth and narrower belt means faster. I ordered a matching pair of 4:1 to produce an easier working relationship.
https://zalophusdokdo.github.io/StepperMotorsCalculator/en/index.html
I resolved the loose pulleys. However, I think I have different problem. I have the same ratio 3:1 but 36:12 and 30:10 are different. The motors are the same. This looks like a design issue. Back to the drawing board.
Using this site for a ballpark answer, I found 36:12 is slower than 30:10 by 66.7%. This explains that issues that I am having. Less teeth and narrower belt means faster. I ordered a matching pair of 4:1 to produce an easier working relationship.
https://zalophusdokdo.github.io/StepperMotorsCalculator/en/index.html
3
Mount Support / Re: AstroEQ out of sync?
« on: August 08, 2020, 19:01:40 »
Hello,
Hmm... the dec and ra pulley set screws were loose. That was the problem.
Hmm... the dec and ra pulley set screws were loose. That was the problem.
4
Mount Support / AstroEQ out of sync?
« on: August 07, 2020, 12:26:44 »
Hello,
I seem to be running into an issue. My gear is based on RPI4B and AstroBerry 2.0.3. AstroBerry contains INDI and KSTARS. I have the AstroEQ using ttyACM. I use AstroEQLoader to setup AstroEQ. My mount is an old Celestron VIXEN Super Polaris.
Any clear night is the same. KSTARS and EQMOD arrive at the target. AstroEQ is halfway there. Instead of pointing south from north the device is pointing at the ground. I listen for slipping. My RA does chatter sometimes. It is more in line with the target than DEC. When KSTARS stops at the target, AstroEQ stops. AstroEQ hasn’t finished getting there.
My AstroEQ config:
Motor Step: 1.8 degrees
Mount gear: 144
Gear Ratio: 3.0
Slew Rate: 94 <—
This Slew Rate is my selection. Manually slewing to a target is smooth and faster at this setting. Any larger and slewing is a crawl. It isn’t getting to the target. Something is out of sync. To me, it must be the slew rate. I have amps set to .7.
The motors are the same. I think the gear ratios might be overly optimistic. I used the stated specifications. The gears are not the same. The motors are the same style, NEMA17.
I will investigate the gear ratios. I will also check for symmetry within EQMOD.
How should the Slew Rate be set? To me, it should not cause any out of step issues. It is a speed control.
I seem to be running into an issue. My gear is based on RPI4B and AstroBerry 2.0.3. AstroBerry contains INDI and KSTARS. I have the AstroEQ using ttyACM. I use AstroEQLoader to setup AstroEQ. My mount is an old Celestron VIXEN Super Polaris.
Any clear night is the same. KSTARS and EQMOD arrive at the target. AstroEQ is halfway there. Instead of pointing south from north the device is pointing at the ground. I listen for slipping. My RA does chatter sometimes. It is more in line with the target than DEC. When KSTARS stops at the target, AstroEQ stops. AstroEQ hasn’t finished getting there.
My AstroEQ config:
Motor Step: 1.8 degrees
Mount gear: 144
Gear Ratio: 3.0
Slew Rate: 94 <—
This Slew Rate is my selection. Manually slewing to a target is smooth and faster at this setting. Any larger and slewing is a crawl. It isn’t getting to the target. Something is out of sync. To me, it must be the slew rate. I have amps set to .7.
The motors are the same. I think the gear ratios might be overly optimistic. I used the stated specifications. The gears are not the same. The motors are the same style, NEMA17.
I will investigate the gear ratios. I will also check for symmetry within EQMOD.
How should the Slew Rate be set? To me, it should not cause any out of step issues. It is a speed control.
5
AstroEQ Support / Re: Motors and AstroEQ
« on: June 12, 2020, 02:37:13 »
Hello Tom,
Thank you. I must have goofed then.
I should have provided this schematic first. The schematic for both motors is as follows.
A ----
||
A'----
B ----
||
B'----
Per the Motor table I provided.
AB = Step 1
BA' = Step 2
A'B' = Step 3
AB' = Step 4
Then, I would have
A1/A2 = First coil, and B1/B2 = Second Coil.
Given the FAQ, the ABBA schematic then is as you describe. But A' is the lead. To me, the pattern is flipped depending on which pin gets the pulse first. The table says A is the first step. Given the logic was yours, which pin fires first step, 2 or 5, to match the table?
Going backards is the same table but starting at A. Both forward and backwards have A as the first step.
Should this be the sequence if pin 2 gets energized first.
2 = A = Black
3 = B' = Blue
4 = B = Red
5 = A' = Green
or
The Schematic shows this sequence with supplied charge
1B = 2 = +
2A = 3 = -
2B = 4 = -
1A = 5 = +
The motor is expecting and using FAQ ABBA. Leading variable is always positive.
A + B = 2 + 4 = Step 1
B + A' = 4 + 5 = Step 2
A' + B' = 5 + 3 = Step 3
A + A' = 2 + 5 = Step 4
For Reverse, the motor is epecting and using FAQ ABBA
A' + A = 5 + 2 = Step 1'
B' + A' = 3 + 5 = Step 2'
A' + B = 5 + 4 = Step 3'
B + A = 4 + 2 = Step 4'
This assumes that the FAQ ABBA is good and the motor likes the setup. However, the schematic is different. What does AstroEQ bring to the motor?
Ok. I used my Fluke to test what is at the AstroEQ. Starting from the Driver, North is pin 1. has Given the pins in the RJ11 where 2 3 4 5 and the driver, they each tap out to be as follows.
2 = A1 = A = Black = +
3 = B2 = B' = Blue = -
4 = B1 = B = Red = +
5 = A2 = A' = Green = -.
Therefore the PDF is not correct for the DRV8825. The FAQ is correct for the DRV8825. Thank you for your assistance.
T
Thank you. I must have goofed then.
I should have provided this schematic first. The schematic for both motors is as follows.
A ----
||
A'----
B ----
||
B'----
Per the Motor table I provided.
AB = Step 1
BA' = Step 2
A'B' = Step 3
AB' = Step 4
Then, I would have
A1/A2 = First coil, and B1/B2 = Second Coil.
Given the FAQ, the ABBA schematic then is as you describe. But A' is the lead. To me, the pattern is flipped depending on which pin gets the pulse first. The table says A is the first step. Given the logic was yours, which pin fires first step, 2 or 5, to match the table?
Going backards is the same table but starting at A. Both forward and backwards have A as the first step.
Should this be the sequence if pin 2 gets energized first.
2 = A = Black
3 = B' = Blue
4 = B = Red
5 = A' = Green
or
The Schematic shows this sequence with supplied charge
1B = 2 = +
2A = 3 = -
2B = 4 = -
1A = 5 = +
The motor is expecting and using FAQ ABBA. Leading variable is always positive.
A + B = 2 + 4 = Step 1
B + A' = 4 + 5 = Step 2
A' + B' = 5 + 3 = Step 3
A + A' = 2 + 5 = Step 4
For Reverse, the motor is epecting and using FAQ ABBA
A' + A = 5 + 2 = Step 1'
B' + A' = 3 + 5 = Step 2'
A' + B = 5 + 4 = Step 3'
B + A = 4 + 2 = Step 4'
This assumes that the FAQ ABBA is good and the motor likes the setup. However, the schematic is different. What does AstroEQ bring to the motor?
Ok. I used my Fluke to test what is at the AstroEQ. Starting from the Driver, North is pin 1. has Given the pins in the RJ11 where 2 3 4 5 and the driver, they each tap out to be as follows.
2 = A1 = A = Black = +
3 = B2 = B' = Blue = -
4 = B1 = B = Red = +
5 = A2 = A' = Green = -.
Therefore the PDF is not correct for the DRV8825. The FAQ is correct for the DRV8825. Thank you for your assistance.
T
6
AstroEQ Support / Motors and AstroEQ
« on: June 10, 2020, 21:33:25 »
Hello,
I am using a custom motor to run a telescope using RPI 3 B+ and Astroberry. I recently had a problem with a driver. It would get very hot at 1.8A. Then it quit. I am reviewing my wiring to make sure I have it setup correctly.
My table from my motor, NEMA 17, is as follows
Step A B A' B'
1 + + - -
2 - + + -
3 - - + +
4 + - - +
CW is walks down
CCW walks up.
Both NEMA 17 are paired from the same specs.
Per the AstroEQ scematic, both RA and DEC are pinned the same way.
Table 1
2 = B1
3 = A2
4 = B2
5 = A1
A motor is geared as in diagram 1 of 4 where:
Table 3
Black = A
Green = A'
Red = B
Blue = B'
At the motor to the AstroEQ, I should have the following
Table 4
Red = B1 = 2
Green = A2 = 3
Blue = B2 = 4
Black = A1 = 5
Here is my problem. At 128x forward works, reverse stutters. 600x, 700x, and 800x forward and reverse works. I am looking for the optimal configuration. I have been attempting different settings. The image supplied works as described.
I am using a custom motor to run a telescope using RPI 3 B+ and Astroberry. I recently had a problem with a driver. It would get very hot at 1.8A. Then it quit. I am reviewing my wiring to make sure I have it setup correctly.
My table from my motor, NEMA 17, is as follows
Step A B A' B'
1 + + - -
2 - + + -
3 - - + +
4 + - - +
CW is walks down
CCW walks up.
Both NEMA 17 are paired from the same specs.
Per the AstroEQ scematic, both RA and DEC are pinned the same way.
Table 1
2 = B1
3 = A2
4 = B2
5 = A1
A motor is geared as in diagram 1 of 4 where:
Table 3
Black = A
Green = A'
Red = B
Blue = B'
At the motor to the AstroEQ, I should have the following
Table 4
Red = B1 = 2
Green = A2 = 3
Blue = B2 = 4
Black = A1 = 5
Here is my problem. At 128x forward works, reverse stutters. 600x, 700x, and 800x forward and reverse works. I am looking for the optimal configuration. I have been attempting different settings. The image supplied works as described.
7
AstroEQ Support / AstroEQ Firmware Errors
« on: June 08, 2020, 17:46:43 »
Hello,
I am attempting to get the latest update for my AstroEQ under Raspberry PI 3B+ running BUSTER. When attempting to get the new firmware, the software attempts to load then crashes to RETRY. Retry hangs up. I ran the software under SUDO. The files download successfully. I was able to upload the firmware under SUDO.
I am attempting to get the latest update for my AstroEQ under Raspberry PI 3B+ running BUSTER. When attempting to get the new firmware, the software attempts to load then crashes to RETRY. Retry hangs up. I ran the software under SUDO. The files download successfully. I was able to upload the firmware under SUDO.
8
AstroEQ Support / Re: Motors only turn in slew/high speed.
« on: July 18, 2019, 18:37:00 »
Hello,
I just went through this same issue recently. I swapped cables and motors and isolated the cable. Then I got out my wire tester. Yes, the cable was bad.
I just went through this same issue recently. I swapped cables and motors and isolated the cable. Then I got out my wire tester. Yes, the cable was bad.
9
AstroEQ Support / Re: DEC motor stopped responding
« on: June 17, 2019, 19:16:40 »
Hello Tom,
I have it working. The problem was the DEC RJ-11 cable. Apparently, it broke apart after three uses. I also have the AstroEQ running under AstroBerry (Ubuntu Mate). I created a custom rule for it. Now for a clear night.
Thank you for your replies. The PSU was appropriate. It was not the cause. The cable was never under stress. But, it was broken.
I have it working. The problem was the DEC RJ-11 cable. Apparently, it broke apart after three uses. I also have the AstroEQ running under AstroBerry (Ubuntu Mate). I created a custom rule for it. Now for a clear night.
Thank you for your replies. The PSU was appropriate. It was not the cause. The cable was never under stress. But, it was broken.
10
AstroEQ Support / Re: DEC motor stopped responding
« on: June 15, 2019, 20:19:16 »
Hello Tom,
The AstroEQ is at the current Rev. Check Firmware says no updates. I am using the current debug.
What is troubling is the dead DEC. I thought I could use debug to see the communication between the OS and the driver. Nope, the debug version does not track success of driver talk. I am continuing investigating my problem.
Thank you for taking time to reply. I will post my reply when I find out the need.
The AstroEQ is at the current Rev. Check Firmware says no updates. I am using the current debug.
What is troubling is the dead DEC. I thought I could use debug to see the communication between the OS and the driver. Nope, the debug version does not track success of driver talk. I am continuing investigating my problem.
Thank you for taking time to reply. I will post my reply when I find out the need.
11
AstroEQ Support / Re: DEC motor stopped responding
« on: June 15, 2019, 12:31:44 »
Hello,
Using Debug, I find this problem with DC. With these repeated strings of failure, the last line says success. Funny. It must be a red herring.
Generating Acceleration Table for DC
Attempt 1 Failed. Abandoned at IVal: 10
Trying Top Speed IVal of 2 and Accel Time of 3.899999998509884
Attempt 2 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.7999999970197678
Attempt 3 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.6999999955296516
Attempt 4 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.5999999940395355
Attempt 5 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.4999999925494194
Attempt 6 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.3999999910593033
Attempt 7 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.299999989569187
Attempt 8 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.199999988079071
Attempt 9 Failed. Abandoned at IVal: 7
Trying Top Speed IVal of 2 and Accel Time of 3.099999986588955
Attempt 10 Failed. Abandoned at IVal: 7
Trying Top Speed IVal of 2 and Accel Time of 2.999999985098839
Attempt 11 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.8999999836087227
Attempt 12 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.7999999821186066
Attempt 13 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.6999999806284904
Attempt 14 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.5999999791383743
Attempt 15 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.499999977648258
Attempt 16 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.399999976158142
Attempt 17 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.299999974668026
Attempt 18 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.19999997317791
Attempt 19 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.0999999716877937
Attempt 20 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.9999999701976776
Attempt 21 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.8999999687075615
Attempt 22 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.7999999672174454
Attempt 23 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.6999999657273293
Attempt 24 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.5999999642372131
Attempt 25 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.499999962747097
Attempt 26 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.399999961256981
Attempt 27 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.2999999597668648
Attempt 28 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.1999999582767487
Attempt 29 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.0999999567866325
Table Generation Success:
Loading seems to show problems. All return values are HEX. =HEX is good. An =0 is bad. 0 says that nothing was written.
1 :T10 :a1 :b1 :s1 :n1 :c1 :d1 :a2 :b2 :s2 :n2 :c2 :d2 :q1 :q2 :r1 :z1 :z2 19
18
:O11
Awaiting Response...
61
13
=
:T10
Awaiting Response...
61
13
=
:a1
Awaiting Response...
61
48
48
51
48
50
65
13
=00302A
raaVal2764800
:b1
Awaiting Response...
61
68
57
51
65
48
48
13
=D93A00
rabVal15065
:s1
Awaiting Response...
61
48
48
52
66
48
48
13
=004B00
rasVal19200
:n1
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
raIVal0
:c1
Awaiting Response...
61
48
48
13
=00
raaxisReverse0
:d1
Awaiting Response...
61
48
48
13
=00
radriverVersion0
:a2
Awaiting Response...
61
48
48
51
48
50
65
13
=00302A
dcaVal2764800
:b2
Awaiting Response...
61
68
57
51
65
48
48
13
=D93A00
dcbVal15065
:s2
Awaiting Response...
61
48
48
52
66
48
48
13
=004B00
dcsVal19200
:n2
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
dcIVal0
:c2
Awaiting Response...
61
48
48
13
=00
dcaxisReverse0
:d2
Awaiting Response...
61
48
48
13
=00
ramicrostepEnable0
:q1
Awaiting Response...
61
48
48
13
=00
raadvancedHCEnable0
:q2
Awaiting Response...
61
48
48
13
=00
ragearchangeEnable0
:r1
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
raGuideRate0
:z1
Awaiting Response...
61
48
48
13
=00
raGoto0
:z2
Awaiting Response...
61
48
48
13
=00
dcGoto0
These screens shot gives the load and desired results. What would be a suggested remedy?
Using Debug, I find this problem with DC. With these repeated strings of failure, the last line says success. Funny. It must be a red herring.
Generating Acceleration Table for DC
Attempt 1 Failed. Abandoned at IVal: 10
Trying Top Speed IVal of 2 and Accel Time of 3.899999998509884
Attempt 2 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.7999999970197678
Attempt 3 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.6999999955296516
Attempt 4 Failed. Abandoned at IVal: 9
Trying Top Speed IVal of 2 and Accel Time of 3.5999999940395355
Attempt 5 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.4999999925494194
Attempt 6 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.3999999910593033
Attempt 7 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.299999989569187
Attempt 8 Failed. Abandoned at IVal: 8
Trying Top Speed IVal of 2 and Accel Time of 3.199999988079071
Attempt 9 Failed. Abandoned at IVal: 7
Trying Top Speed IVal of 2 and Accel Time of 3.099999986588955
Attempt 10 Failed. Abandoned at IVal: 7
Trying Top Speed IVal of 2 and Accel Time of 2.999999985098839
Attempt 11 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.8999999836087227
Attempt 12 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.7999999821186066
Attempt 13 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.6999999806284904
Attempt 14 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.5999999791383743
Attempt 15 Failed. Abandoned at IVal: 6
Trying Top Speed IVal of 2 and Accel Time of 2.499999977648258
Attempt 16 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.399999976158142
Attempt 17 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.299999974668026
Attempt 18 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.19999997317791
Attempt 19 Failed. Abandoned at IVal: 5
Trying Top Speed IVal of 2 and Accel Time of 2.0999999716877937
Attempt 20 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.9999999701976776
Attempt 21 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.8999999687075615
Attempt 22 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.7999999672174454
Attempt 23 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.6999999657273293
Attempt 24 Failed. Abandoned at IVal: 4
Trying Top Speed IVal of 2 and Accel Time of 1.5999999642372131
Attempt 25 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.499999962747097
Attempt 26 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.399999961256981
Attempt 27 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.2999999597668648
Attempt 28 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.1999999582767487
Attempt 29 Failed. Abandoned at IVal: 3
Trying Top Speed IVal of 2 and Accel Time of 1.0999999567866325
Table Generation Success:
Loading seems to show problems. All return values are HEX. =HEX is good. An =0 is bad. 0 says that nothing was written.
1 :T10 :a1 :b1 :s1 :n1 :c1 :d1 :a2 :b2 :s2 :n2 :c2 :d2 :q1 :q2 :r1 :z1 :z2 19
18
:O11
Awaiting Response...
61
13
=
:T10
Awaiting Response...
61
13
=
:a1
Awaiting Response...
61
48
48
51
48
50
65
13
=00302A
raaVal2764800
:b1
Awaiting Response...
61
68
57
51
65
48
48
13
=D93A00
rabVal15065
:s1
Awaiting Response...
61
48
48
52
66
48
48
13
=004B00
rasVal19200
:n1
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
raIVal0
:c1
Awaiting Response...
61
48
48
13
=00
raaxisReverse0
:d1
Awaiting Response...
61
48
48
13
=00
radriverVersion0
:a2
Awaiting Response...
61
48
48
51
48
50
65
13
=00302A
dcaVal2764800
:b2
Awaiting Response...
61
68
57
51
65
48
48
13
=D93A00
dcbVal15065
:s2
Awaiting Response...
61
48
48
52
66
48
48
13
=004B00
dcsVal19200
:n2
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
dcIVal0
:c2
Awaiting Response...
61
48
48
13
=00
dcaxisReverse0
:d2
Awaiting Response...
61
48
48
13
=00
ramicrostepEnable0
:q1
Awaiting Response...
61
48
48
13
=00
raadvancedHCEnable0
:q2
Awaiting Response...
61
48
48
13
=00
ragearchangeEnable0
:r1
Awaiting Response...
61
48
48
48
48
48
48
13
=000000
raGuideRate0
:z1
Awaiting Response...
61
48
48
13
=00
raGoto0
:z2
Awaiting Response...
61
48
48
13
=00
dcGoto0
These screens shot gives the load and desired results. What would be a suggested remedy?
12
AstroEQ Support / DEC motor stopped responding
« on: June 14, 2019, 23:16:16 »
Hello Tom
My DEC motor stopped running. What is strange is that I can swap drivers. The RA works but the DEC doesn't.
What preceptitated this, is me. I pulled the wrong PSU brick to power the AstroEQ while working USB HUB issues with RPI3B+. What should I check to ensure the function of the AstroEQ? Both drivers work in the RA port. DEC does not function.
Thank you
John
My DEC motor stopped running. What is strange is that I can swap drivers. The RA works but the DEC doesn't.
What preceptitated this, is me. I pulled the wrong PSU brick to power the AstroEQ while working USB HUB issues with RPI3B+. What should I check to ensure the function of the AstroEQ? Both drivers work in the RA port. DEC does not function.
Thank you
John
13
Mount Support / AstroEQ and uploaded settings
« on: April 10, 2019, 00:32:37 »
Hello Tom,
Lately, I am finding the AstroEQ Firmware 3.9.0 uploading to be working with a profile. When downloading, I get a blank data or a partial list. This is seems to be more prevalent under Debian Linux. Under Windows, the tool works fine.
Best regards,
John
Lately, I am finding the AstroEQ Firmware 3.9.0 uploading to be working with a profile. When downloading, I get a blank data or a partial list. This is seems to be more prevalent under Debian Linux. Under Windows, the tool works fine.
Best regards,
John
14
AstroEQ Support / Re: Forgetful configuration issue?
« on: March 13, 2018, 14:41:21 »
Hello,
Under RPI 3mB and Jessie, astroeqloader pulled up a partially empty list. The Goto values were there. Everything else was blank.
As I was verifying from Windows, I added the missing values. This almost reminds me of invalid values.
RA motor
0.9 (if .9 is the value, it will be blank.)
3
144
12 (Calculated by Update)
DEC motor
1.8
3
144
126 (Calculated by Update)
I get an RA IVal is too small. But, it’s calculated. DEC values are accepted. What is missing?
0.9
Under RPI 3mB and Jessie, astroeqloader pulled up a partially empty list. The Goto values were there. Everything else was blank.
As I was verifying from Windows, I added the missing values. This almost reminds me of invalid values.
RA motor
0.9 (if .9 is the value, it will be blank.)
3
144
12 (Calculated by Update)
DEC motor
1.8
3
144
126 (Calculated by Update)
I get an RA IVal is too small. But, it’s calculated. DEC values are accepted. What is missing?
0.9
15
AstroEQ Support / Forgetful configuration issue?
« on: March 13, 2018, 11:09:40 »
Hello,
I setup under Windows the peculiar settings of motors, pulleys and belts. Every reload of the configuration yields a blank setting. I reload the saved file and save again. Test under EQmod and reload. It is blank or partially blank.
After a firmware update, the configuration is loading correctly. Under Windows, AstroEQ works as advertised.
Under RPI, it acts eradict. In INDI, I set the motor details. To me, it seems that INDI sees the EQ6 as forces SkyWatcher mount configuration. It looks like it considers any AstroEQ settings as bogus. Or the problem above is real. I am going to setup the Debian configuration tool to see if the Windows problem is real.
I setup under Windows the peculiar settings of motors, pulleys and belts. Every reload of the configuration yields a blank setting. I reload the saved file and save again. Test under EQmod and reload. It is blank or partially blank.
After a firmware update, the configuration is loading correctly. Under Windows, AstroEQ works as advertised.
Under RPI, it acts eradict. In INDI, I set the motor details. To me, it seems that INDI sees the EQ6 as forces SkyWatcher mount configuration. It looks like it considers any AstroEQ settings as bogus. Or the problem above is real. I am going to setup the Debian configuration tool to see if the Windows problem is real.