EQMOD Control Failure

[BlueAstra]

I have been unable to resolve my communications problems with my EQ6 mount using the ASCOM/EQMOD/EQDIR configuration. I have tried the following equipment in almost every possible combination:

ZBOX HD-1D11 Nettop (Atom D510 @ 1.66GHz, 2GB ram, 64GB SSD, W7 32bit HProf)

ACER 3950 Desktop PC (Intel core i3 550, 2G ram, 500G HDD, W7 64bit H Prem)

Hitec USB-EQDIR Module

Shoestring Serial-EQDIR Module

Prolific based USB-Serial adapter (PL2303 driver, 12.3.10, 3.3.11.152)

FTDI based USB-TTL cable (32/64bit driver CDM20802)

ASCOM v5.5.1, EQMOD v1.23e

MAXIM DL v5.1.4, Starry Night Pro Plus v6.0

I normally have other equipment connected (EG, focusser, powered hub, cameras) but these have all been disconnected for this test. Only the EQDIR module or FTDI cable is connected.

The basic problem is that I can setup almost any combination of the above equipment and connect successfully to the mount. However, during a slew to a target at some point EQMOD will indicate a communication loss and try to send stop commands. The mount will continue to the target (the stop commands are ignored) and stop, but no further comms is possible unless I exit MAXIM or SN and restart the programs. The one exception to this is the FTDI USB-TTL cable which connects, but after a short pause EQMOD shows connection errors without any further action. I have tried changing port parameters without success.

The only successful means of communication is with a USB-Serial adapter through the handset in PC Direct mode. This works without a problem, but I do notice single comms loss events very occasionally. This is less than the 5 consecutive errors which triggers a stop, so it has shown to be effectively 100% reliable.

The only other thing I’ve noticed is that the EQ6 red power light flashes on/off during a slew (handset or EQDIR), and sometimes flickers. The PSU is the one supplied with the EQ6 (12V, 6A). Not sure if this is significant or not.

I have now run out of ideas trying to find a solution to this. I am trying to find a setup that will suit a DIY observatory, and having to use the handset during setup is inconvenient and does not follow the EQASCOM guidelines. However, it seems I haven’t a choice. I would appreciate if anyone has any further suggestions.

[BlueAstra]

I thought it would be useful to summarise my experiences in trying to track down and cure communications problems with my EQ6 Pro mount when used under ASCOM/EQMOD control. It might help other users who have similar issues, and point to areas for investigation. The help from the EQMOD, ASCOM and EQ6 Yahoo forums was also invaluable.

The equipment setup is a Nettop ZBOX HD-1D11 (Atom D510 @ 1.66GHz, 2GB ram, 64GB SSD) running XP, Ascom v5.5.1, EQMOD v1.23e, connected via USB to a Hitec EQDIR module, which connects direct to the EQ6 input. All other equipment was disconnected during the tests.

The typical fault in EQDIR mode was the occasional comms loss just after connection, and an almost guaranteed comms loss during a slew. This reduced to an occasional single event comms loss when using the handset in PC direct mode (USB-Serial adapter – Handset port), which didn’t provoke a stop command. The communication status can be seen if you click on the ‘display +’ button (top left) on the EQMOD panel, and/or the Ascom symbol which opens a comms terminal window. The mount worked perfectly normally if you just used the handset.

The first suspect was the prolific chipset used in the Hitec EQDIR adapter. Prolific chipsets are not noted as the most reliable by the EQMOD designers, and XP did not allow access to the latest drivers (3.3.11.152, which are for Vista onwards). I upgraded to W7 on the nettop and downloaded the latest drivers from prolific, but it made no difference. I then tried a Shoestring Serial EQDIR module with an Astronomiser USB-Serial adapter, but this also used prolific and had the same problems. Next up was a FTDI based USB- 5V TTL cable, same problem. Finally, the gold standard, a Keyspan USB-Serial adapter, which unfortunately also gave the same communication issues.

So the problem was probably not associated with the computer – EQDIR link, so I started to look elsewhere. I had noticed that the red LED on the mount flashed occasionally during slew. In my case I was using a free ‘12V 6A’ PSU supplied with the mount, through an extension cable to the mount. The handset said I was getting 11.7V, dropping to 10.4V during a RA+DEC fast slew. This gave the flashing LED during the slew. When I removed the extension cable I got 12.2V static and 11.7V during a slew, and a solid LED. However, I still got the communication failures. I removed the power connector at the mount and measured the voltage with a multimeter held directly against the jack plug. This showed the voltage varying from 12.1 – 11.3V over a period of about a second or so, even with nothing connected.

Many people use this mount and EQDIR/EQMOD with no issues, and many people use a power tank to power it. Lots of people also use laptop style power ‘bricks’ to power the mount. Power tanks/batteries run at about 13.8V, so I wondered if the low voltage, or the cyclic nature of it, was contributing to the comms error. I replaced the PSU with a stabilized supply set at 13V and the comms errors have gone away! If I were to guess I would say the cyclic power fluctuation triggered a comms error during the voltage ‘dip’. This would be aggravated during a slew since the overall voltage dropped when the motors ran. So finally I believe the problems were caused by a faulty power supply, and cured with a good regulated supply.

The supplied power brick ran the mount perfectly with just the handset, so you would never notice a problem under these conditions. Also, if the mounts were not tested with EQMOD/EQDIR prior to delivery, the supplier would never notice it either. The problem only appeared during direct EQMOD/EQDIR control. The problem would also not occur if you used a power tank or battery, since they tend to run at about 13.8V. Of the USB-Serial adapters, they all subsequently proved to work. The Keyspan is probably best, and it comes with lots of useful diagnostic software. However, I now used the FTDI based USB- 5V TTL cable as my EQDIR interface, very cheap and reliable.

So if you get comms issues with EQMOD, check your power supply first, then move on to the various bits of hardware/software. Post queries in the various forums. The cable based USB- 5V TTL EQDIR solutions are a good method for linking your computer to the mount. To have a reliable EQMOD setup allows you to realise just how good this software is for mount control.