Welcome, Guest. Please login or register.

Username: Password:

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.

Messages - TCWORLD

Pages: [1] 2 3 ... 52
1
AstroEQ Support / Re: Configurator Unable to read EEPROM
« on: January 19, 2021, 20:33:15 »
Great. Glad it's sorted.

2
AstroEQ Support / Re: Configurator Unable to read EEPROM
« on: January 17, 2021, 14:23:05 »
Hi Julian,

Is the Status LED blinking slowly after you've updated the firmware?

There were some minor hardware changes between versions - the V4.4 is quite an old design, though not too far gone. The main difference that could cause an issue, is a missing resistor.

Fortuantely the V4.4 board already has the GPIO footprint (between the PIC and ATMEGA). All you need to do is solder a 1k resistor between pins 2 and 4 of the GPIO header (pin 1 is the square pad marked by the silk screen) and you should be good to go. While you're at it, if you have the ST4 connector, solder a wire from pin 4 of the GPIO header to pin 1 of the ST4 connector (the unconnected pin closest to the bottom edge of the board).

Kind Regards,
Tom

3
Mount Support / Re: Green Swamp Software GS Server
« on: January 04, 2021, 10:16:47 »
Great. Will push the new version to github once I've done some checks with EQMOD and indi.

4
General Discussion / Re: Synscan App, desktop and mobile
« on: January 04, 2021, 08:55:11 »
Hi,

This is a problem that stems from there being two skywatcher comms protocols.

The first, synta protocol, is used to communicate between a hand controller and the mount. This is what AstroEQ uses to talk to EQMOD.
The second is used to talk from accessories (such as WiFi controllers) to the hand controller. Being a different protocol, it's not compatible with AstroEQ. I presume your WiFi module talks in this language.

5
Mount Support / Re: Green Swamp Software GS Server
« on: January 04, 2021, 01:20:30 »
If you could give the attached firmware a try.

Just update the hex/ folder in the latest config utility version with the attached files

6
Mount Support / Re: Green Swamp Software GS Server
« on: January 04, 2021, 01:11:47 »
Ah, wait a moment.

I think I known what's happening.

When requesting a slew in the same direction as it is currently running (if the axis is already moving), the AstroEQ doesn't need the :J command following :I. Indi just issues :I without :J.

The problem with the extra :J command being issued, is that the motor is already running when it's sent, which means it locks up waiting for it to stop running so it can start a new movement (nothing has told it to stop).

I can probably make a simple adaption to the :J parsing such that if the axis is in an updatable state, it ignores :J.

7
Mount Support / Re: Green Swamp Software GS Server
« on: January 04, 2021, 01:08:59 »
Hi Phil,

The lack of a :K command shouldn't matter - that just instructs the axes to stop.
The AstroEQ is quite happy to receive the :Ixxxxxx command while running, then :J command sequence to initiate the change in speed. IIRC this what Indi does too, for which I'd made adaptions to support.

I presume you are using the latest firmware?

8
AstroEQ Support / Re: AstroEQ board 4.5 cant flash firmware
« on: November 19, 2020, 09:13:53 »
Have you checked the board for shorts/cold solder joints/incorrect components, etc?

9
AstroEQ Support / Re: AstroEQ board 4.5 cant flash firmware
« on: November 18, 2020, 18:47:10 »
I've used ArduinoISP to program the ATMega162 with it's bootloader quite successfully in the past.

Try the following instructions:

Program your Arduino with the ArduinoISP sketch.
Open command prompt (or a terminal if linux).
Change to the bin/ directory in the AstroEQ config utility
Run the following command (changing the path to point to wherever you saved the bootloader file, and the port to match your Arduino)

Code: [Select]
avrdude -C../etc/avrdude.conf -v -v -v -patmega162 -cstk500v1 -P\\.\COM10 -b19200 -Uefuse:w:0xFB:m -Uhfuse:w:0xDC:m -Ulfuse:w:0xFF:m -Uflash:w:optiboot_atmega162.hex:i -Ulock:w:0x0F:m
Assuming you have your pin connections correct, this should work. I'd plug the chip into the AstroEQ board, making sure you apply the 12V DC power supply, that way the 16MHz crystal is connected up to the chip which will be needed for programming. You can then connect the MISO/MOSI/SCK/RESET/GND pins from the AstroEQ boards ISP header to your Arduino (don't connect the 5V line as that is powered by the AstroEQ regulator).

10
AstroEQ Support / Re: AstroEQ board 4.5 cant flash firmware
« on: November 17, 2020, 23:50:21 »
Hi,

Did I supply the ATMega as well as the PIC? (can't remember now). If so, it should already have the bootloader on it.

11
Mount Support / Re: AstroEQ out of sync?
« on: August 09, 2020, 10:23:23 »
Glad you've sorted it.

12
AstroEQ Support / Re: Compatibility problems EQMOD v200
« on: June 21, 2020, 22:51:01 »
If it's working with V1.29, then its an EQMOD issue, not an AstroEQ issue. There is no difference between the two in how the AstroEQ communicates.
The compatibility issue previously reported was due to a new feature in EQMOD V2.00 that conflicted with a command (now changed) used by the configuration utility.

Its possible that there is an issue with the "special version" of v2.0, I have no idea what changes Chris made to that for you. Or it could be as simple as an installation problem.

13
AstroEQ Support / Re: Compatibility problems EQMOD v200
« on: June 21, 2020, 18:28:03 »
Hi Rick,

Sorry it takes me some time to respond, I am exceedingly busy at the moment..

What do you mean by "EQMOD can't find any ports"? I presume you've set up the EQMOD settings and selected which COM port it should be using?

Sometimes switching between versions can cause problems with the EQMOD.ini file. You could try making a backup of the EQMOD configuration and starting fresh - say rename "%APPDATA\EQMOD\EQMOD.ini" to something like "%APPDATA\EQMOD\EQMOD.ini.bak", the load EQMOD again and it should create a new file. If that doesn't help, you can rename the backup back to restore your previous setup.

I presume having downloaded the latest config utility that you've run the update firmware button to ensure the latest firmware is on the AstroEQ?
What does the status light of the AstroEQ do when you try to connect EQMOD?
When you configure the AstroEQ settings, you'll need to make sure that the Advanced HC Detect option is set to disabled (the default) as the old controllers are missing a resistor which is used as part of that detection.

With little information to go on, I can't offer any more advice.

14
AstroEQ Support / Re: Motors and AstroEQ
« on: June 12, 2020, 09:26:37 »
Different motor drivers have different naming conventions for the pins. The net labels on the AstroEQ are following the A498x driver naming where 2x is one coil, and 1x is the other coil. The DRV882x and several other drivers are named differently, with Ax is one coil and Bx is the other coil.

Your suggested pinout has each coil being driven by both drivers (e.g. + of one driver - of the other), this is wrong. It will prevent the motors spinning properly, and will cause overheating of the drivers and motors due to inability to current regulate.



Follow the ABBA wiring scheme, it is correct for all of the 16-pin Pololu driver modules.

For your motor A/A' are one coil, and B/B' are the other coil. Any of the following are valid wirings:

Code: [Select]
Option 1:
x  A   B   B'  A'  x

Option 2:
x  A   B'  B   A'  x

Option 3:
x  A'  B   B'  A   x

Option 4:
x  A'  B'  B   A   x

Option 5:
x  B   A   A'  B'  x

Option 6:
x  B   A'  A   B'  x

Option 7:
x  B'  A   A'  B   x

Option 4:
x  B'  A'  A   B   x

If the motors rotate in the wrong direction (i.e. sidereal tracking spins east not west), you select the "Reverse" option in the configuration utility to correct for it.

15
AstroEQ Support / Re: Motors and AstroEQ
« on: June 12, 2020, 00:12:02 »
Hi,

You've got your connections crossed. The drivers and motors all use different naming schemes. In the A1/A2/B1/B2 scheme, A1/B1 are the first coil, and A2/B2 are the second coil.

As your motors are labelled A and B, where A is one coil, and B is the other coil. then the RJ11 cables should be wired as A B B A per the FAQ. It doesn't matter which coil you use for A, and which coil you use for B, nor which end of each coil is which, as long as you are consistent on both RA and DEC wiring.

In your case, the simplest way to correct your wiring is to swap the red and green wires, so:

  • N/C
  • Green
  • Red
  • Blue
  • Black
  • N/C

Pages: [1] 2 3 ... 52