malc-c

The reason is because you have set CDC to use GSServer and not EQMOD

Well at least we're getting somewhere as you say the motors are running, but the direction / duration following an instruction is always incorrect. If you've swapped the leads over, and checked the motors then there is little more you could do other than return the complete kit back to the retailer.

So based on the last post, the handset initializes, but setting the speed to 9 and pressing any of the directional keys, or selecting any target from the handset, the handset shows it slewing to target but the actual motors fail to run. You've also tried swapping the two link cables yet still the motors fail to move. I was going to say that this points to the motors, but we have yet not being able to identify if there is actually any voltages or pulses being sent to the motors from the synscan unit. If you have access to a digital volt meter you could test the steppers as suggested in this article If you get the resistances between each coil then this could suggest the steppers are fine, but the synscan unit is at fault. Alternatively, contact the retailer and see about returning the handset, synscan unit and both steppers with all the cables, ideally under warranty if the scope falls within that time frame.

You're welcome Malcolm (seems strange typing that, seems I'm talking to myself 🙄) I'm sure it will work as expected. Provided both EQMOD and Stellarium have the same location and time settings and you start with the the scope in a know position (ie the default home position) you should be fine. I have my HEQ5 / 200P permanently set up in an observatory, but to give clearance I use the custom park position offered by EQMOD. So long as the scope is parked at the end of a session, be that the default home position or a custom park position and not moved between sessions then you shouldn't need to do any additional alignment at the start of any session. Also with EQMOD, if you sync after centring each target this gives even more goto accuracy allowing you to be up and running even quicker.

Re-reading through the post there is no mention that the handset displays the "no response" message when plugged in, so that suggests to me that the main board in the synscan unit is working as the microcontroller(s) are running and talking to the handset. The fact the motors don't move suggests that it is either the driver chip section on the board that's blown, or and more probable a wire connected to the DIN plug or socket has broken off (wouldn't be the first time on synscan units for the EQ3/ EQM35 and EQ5). here's an example of the same issue - scroll down to the last but one post on page 2 Check each wire behind the DIN sockets on the motor casings, and each cable for continuity.

Can't really comment , however, most synscan mounts are shipped with a long serial serial cable that has an RJ 11 at one end and a 9 pin D type plug on the other. This is designed to upload firmware to the handset, and if the handset is placed into PC-DIRECT mode, as a pass through to update the mounts firmware. Thing is these days most computers no longer have a true serial port so a USB to true RS232 convertor is needed. This was originally the way to control the scope in the early days of EQMOD. The problem comes when you then use the same lead in the handset port, which then shoves +/- 12 (ie 24 volt potential) into the PIC's serial UART which they can't handle and blow. An EQDIR cable uses a USB to 5v TTL Serial chipset with the other end of the cable terminated with an RJ45. 12v 2amp may be close to the limits. It only leaves around 200mA with both axis slewing. Plus if its out in a cold damp environment it could cause the voltage to drop. These boards whilst rated at 12v really like one or two more volts and get upset if the voltage drops below 12v. It could have been the case that caused it to fail half way through. Bearing in mind that the handset is powered through the supply to the main board, and will use up at least 50mA just to illuminate the display, reducing that 200ma headroom even more. Anyway, glad you have the thing working

You can't use both. You either use the handset to select targets or you use a planetarium application and EQMOD. EQMOD will assume you are starting from the default home position unless you have defined a custom park position and park and start from that position every time. The HEQ5 has no physical encoders so both the handset and EQMOD have no idea where the mount is pointing when the mount is powered up. Both presume the mount is in the default home position of weights down pointing North with the RA parallel to the NCP (unless you used EQMOD to set a custom park position as mentioned). So after you have done the alignment with the handset the scope is pointing at whatever the last alignment target was, but when you then connect the scope to the computer and launch EQMOD it will assume the mount is in the default home starting position. Therefore all subsequent slews will be way off target If you are doing visual observing then I would suggest just using the handset to do everything. If you are doing imaging then use EQMOD / ASCOM / PHD2 and any planetarium application and your chosen camera application.

Its no so much the capacity of the battery it the voltage it provides. Whilst the specs state 12v 3amp (tip positive), that 12v is the under load voltage. Depending on the design of the PSU you may find that the voltage drops to 10 or 11 volts when both motors are running. Now as you have the same issue when using the supplied power brick as you do with other supplies I would suggest you contact the retailer with a view of having the scope collected under warranty and let them test and repair or replace the mount.

Two things that result in the "no response ..... XX/YY axis" message. The board has lost power and thus nothing is getting to the microcontrollers, or the serial ports on the microcontrollers have been blown by too high a voltage. The latter is more common on older dobsonian scopes where two identical boards are linked and the cables are inserted into the wrong port on the board. As Mandy has pointed out the part is an inductor, and generally doesn't fail. I've fixed my own HEQ5 board by replacing the two electrolytic capacitors C3 and C41 next to the connector J1. I've used the same values but with a higher voltage rating. If this doesn't resolve the issue, and you get a similar "comms failure" when using EQMOD or similar then this would suggest that the fault lies in the serial communication circuits. This can be down to a blown signal diode(s) (mainly fitted to MC003 / 004 boards found on Dobs) or damaged PIC microcontrollers. I've managed to program 16F886's for a variety of boards which has been documented in this thread including my own HEQ5. If you find that you get similar issues with an EQDIR cable as you do with the handset and you are in the UK, then drop me a PM and we'll see about repairing the board.

There's more of a chance of it falling out rather than being stuck as it the tab that holds the mount in place, but I agree with the poster above, take the cable to any IT support company and ask them if they could re-terminate the cable with a new plug for a drink. Shouldn't take a techie more than 30 seconds to cut and crimp a new one on

You will be quite hard pushed to find any manual for these scopes. The old 3tr / 11tr names have been dropped, but the actual design hasn't changed over the years. Most of the time they came with very simplistic instructions like the ones on Tasco's customer service page here They operate the same way as any EQ telescope. This old post might help ?

If the mount is an EQ mount, you state that both ALT and latitude is 0. Unless you are at the Equator your latitude will be different to match the same latitude as your location, which if in the UK is around 54 degrees. You say you use the "hand cable" I presume you mean a handset, yet you state you use EQMOD and NINA. You can't use both. If the handset is the same as most SW EQ mounts you can't have it perform the alignment and then start using EQMOD. I also asked how are you connecting a computer, is it using an EQDIR cable? If you can post a picture of how you have the scope set up and state where you are based it will help us second guessing. Can you also confirm that you have entered the custom gear settings for the AZ-GTi as stated in my previous post with the link to the EQMOD page ? - Without doing so the mount will be way off target as it will assume you are using an HEQ5 or EQ6 mount which have totally different gear ratios Unless you are using the mount in an observatory where it doesn't get moved, EQMOD assumes you are starting from the default home position, which is weights down, RA axis pointing at the NCP with the DEC axis parallel to it. You can then use whatever aquarium program to select a target, which if needs correcting is done through the NSWE buttons on the EQMOD interface on screen. Then once centred you Sync the target via the planetarium program (I don't use NINA so can't advise on that aspect). If you repeat this for stars in the west, and east EQMOD should then work out the corrections and any target inside those points should be more or less centred on subsequent gotos.

I agree.. But sadly that's the way things are going... Synta would much rather you buy a new handset than a $20 spare part.

How are you making that connection? - do you use an EQDIR cable or are you connecting the computer to the mount via the synscan handset set into PC-DIRECT mode ?

I came across a similar post from a few years back by accident when I was looking for details unrelated to this issue. I seem to recall the poster (on one of the other forums) was unable to locate a drop in replacement and had no choice but to shell out and buy a new handset. The screen appears to be COG (chip on glass) which is a graphical screen and you would need to know the pixel array size and the controller used to ensure you get legible charters. One other possibility is that Synta had these mass produced under its own specifications and is proprietary to the handset. this SGL thread provides the part numbers which don't return much information, and if you read the last few posts you can see you are not alone, and that someone tried a similar display which didn't work.

To see if its and EQMOD problem or something else, are you able to slew to a target when using the handset? If that the case then and the issue only happens when using the PC / EQMOD then it could be that the incorrect location data hasn't been set in EQMOD, the PC time is incorrect or one the application is using daylight saving ontop of the PCs BST setting, or it could be (and I'm betting this is the case) that you haven't set the mount to use the custom gear settings as stated on the EQMOD prerequisites website

It's not really any criticism, just really an observation that triggered my OCD... For me its a shame that the shiplap where the roof section and side walls meet when closed becomes out of alignment through the join after the fourth row down from the top. It's not a criticism, but given your high attention to detail throughout the build it seems that this was overlooked. It has no impact on the practical aspect of what is one of the best DIY self build observatories we've seen for some time on the forum.

They will most probably launch from Boca whilst under development, but they have just topped out the tower at the Cape, and halfway through erecting a factory / assembly plant, so "regular" launches will probably move there. Also there are less hoops for SpaceX to jump through to appease the bureaucrats and other organisations which slowed up progress at Boca.

I'm with you on the two synchronised landings of the falcon heavy boosters.... it was just perfect. This year Space X is setting a lot of records, as of today, 143 landings of the booster stage, 44 launches so far this year with most boosters being reused 4 or more times. Its almost getting boring watching the live feeds as unlike other companies nothing goes wrong and Falcon 9 launches are so dialled in. I agree with you that the complexity with Starship is such that its almost bound to fail at the start. But if they manage to pull off the chopsticks plucking an almost hovering booster from the sky it's going to escalate the race to the moon to a new level as we can see, SpaceX has the next three revisions of Starship and booster in production, almost ready to fly weeks after the first orbital flight test. We'll soon find out as Musk has announced that the orbital test flight will occur before the end of November, possibly sooner. In that time we should see all 33 Raptors lit in a test fire. The last test fire of booster engines (7) included the three gimballed engines which according to Musk worked well. I also agree with you on your last sentence. Even with most of the fuel exhausted the booster would make a big explosion, if it failed at take off it would be horrendous, probably taking out the tank farm and some of the complex. But it would make for some exceptional viewing !!

Stu, IF we are comparing the two, SpaceX have done a lot more than NASA. Granted the full stack of booster and starship have yet to be launched, but SpaceX have launched and landed a starship without it falling over or RUD'ing along the way. They have repeatedly test fired the raptors, and now with plan on testing all 33 engines within the next month when starship 25 is stacked on top (one of the channels on YT mentioned that it needed the added weight of a fuelled starship to prevent the booster from ripping itself off the pad if it was tried without.) - And if all goes to plan following an announcement by Musk that barring red tape they will be ready to do the first orbital flight by the end of November. But I would agree that in reality SLS/Artemis will get to the Moon first. All they need to do is launch what's standing on pad 39B. Whilst un-manned it is planned to reach and orbit the Moon, which for SpaceX is some time away assuming the planned orbital flight is a success. It would be fantastic to see the booster get caught in the chopsticks and starship land, or splash down without issue, but my gut feeling is that the booster will end up taking out the tank farm on its return. They then have to launch two starships and perform a refuelling operation in orbit before setting off for the moon... So it could be a year or two before SpaceX reaches that goal

So if they effectively used the same parts, then we would assume that on the shuttle they were leak proof then... I mean you wouldn't want evaporating hydrogen leaking just feet away from an ignition source (like three engines and two SRBs !) - In fact I would go as far as saying that the shuttle was more problematic as not only did you have the quick disconnect to load propellent but also the similar quick disconnects between the external tank and shuttle that fed fuel to the three engines. I don't recall the shuttle having the same issues the SLS has. Don't get me wrong... I was really disappointed when the launch attempt was aborted. I can't wait to see man back on the Moon, and given modern 4K and 8K cameras the video that will be sent back will be amazing. But these setback are things that should have been checked and tested before being assembled and fitted.

I agree. Silk purse / sow's ear comes to mind. Given the time frame to get where SLS is today may have been quicker if the rocket was designed from the ground up. But then it probably would have cost three or four times the budget and unlike Apollo where the drive was more political than scientific would never have got the backing. I don't remember the space shuttle having any similar leaks when fuelling with liquid hydrogen, so maybe they should have used the same design (assuming the same parts could be used) . Conversely if they have used the same parts and they knew the design of the seals had issues then what did they expect when it was used on the SLS...

5% leak, so a single percentage over the acceptable threshold. So many on the chat of NASA Spaceflights stream was coming up with alternate meanings for SLS - most along the "slightly leaking spacecraft" or similar vein. At this rate, given SpaceX's success of lighting both all 6 raptors on starship and 7 on Booster 7 in one week, Elon will be walking on Mars by the time the problems with SLS are resolved and gets launched !

Just watched it on catch up. Have to agree with the others, it was a golden opportunity to cover a lot of the questions that are asked here on the forum. They could have covered the advances in equipment, such as the portable trackers, and demonstrated how to use it. They covered the use of mobile phones, so why not show one set up with a suitable bracket rather than just talk about it. They also could have shown the use of web cameras, and then moved on to dSLR cameras, eventually showing a setup with a dedicated cooled camera. It could still have included the section on the professional equipment, but that could have been a lot shorter, as could the section where they looked back at Pete's journey with the S@N team. Granted, it could have gone the other way and been too nerdy, causing people to turn off, especially if they included post processing of data, but it is a specialist programmed aimed at everyone from the casual interest observer to the dedicated armature interested in astronomy, most of which would / could be interested in the technical side.

Same here...