Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

stargazine_ep28_banner.thumb.jpg.b94278254f44dd38f3f7ee896fe45525.jpg

Anne S

Synscan v3 handset update issues

Recommended Posts

I'm trying to update my v3 handset prior to selling the mount. I need to update the bootloader from v1.0 to v1.7 before I can upgrade the firmware from 3.12 to the newest version. I've tried following the instructions in the bootloader download but the upgrade loader refuses to install anything.

Before I realised I needed to update the bootloader, the synscan loader v3.3 just showed 255 255 255 where it should display the handset software, ie 3.12.

Can anyone advise what I'm doing wrong?

The handset won't run the mount probably because I had a replacement motor control board a few years ago., I'm guessing. It worked fine before that. I've been using eqMod for years.

Thanks.

Anne

Share this post


Link to post
Share on other sites

Are you using a serial connection to update?

I think this is usually asked and it might help some who can help see this post.

Share this post


Link to post
Share on other sites

I'm using the lead that came with the mount and a usb converter that I'm sure worked when I used it last. I've another one that worked in Kelling earlier this month, I'll try that tomorrow. W7 laptop.

Share this post


Link to post
Share on other sites

Try updatingt he bootloader first them the firmware. I had the same issue because I done it the wrong way around.

Share this post


Link to post
Share on other sites

That's my problem, I couldn't get the firmware loader programme to let me update the bootloader. I had tried to update the software first before I realised. Maybe I should have rebooted the computer before trying again.

Share this post


Link to post
Share on other sites

I've tried updating the bootloader this morning. I get an error message "Version 3.xx firmware does not work on 255.xx hardware. What do I try next? Not yet heard back from Skywatcher.

Share this post


Link to post
Share on other sites
53 minutes ago, Anne S said:

I've tried updating the bootloader this morning. I get an error message "Version 3.xx firmware does not work on 255.xx hardware. What do I try next? Not yet heard back from Skywatcher.

That is probably the reason. Sometime in the past the V3 hardware was changed meaning that the latest v3 firmware cannot be used with the earlier v3 handsets. I have two v3 handsets, neither of which can be upgraded beyond firmware version v3.38.09.

Share this post


Link to post
Share on other sites

That explains it. If one could get the older version of the update software it would be possible to update it slightly - it's on 3.12. However I thought it wasn't controlling the mount when I tried it outside  - it just complained about the software needing updating. I've now tried in inside and it slews fine. I'll amend my for sale listing accordingly.

I may get an answer from Skywatcher yet with the necessary files to update as far as possible.

Thanks for your help.

Anne

Share this post


Link to post
Share on other sites
2 hours ago, Anne S said:

That explains it. If one could get the older version of the update software it would be possible to update it slightly - it's on 3.12. However I thought it wasn't controlling the mount when I tried it outside  - it just complained about the software needing updating. I've now tried in inside and it slews fine. I'll amend my for sale listing accordingly.

I may get an answer from Skywatcher yet with the necessary files to update as far as possible.

Thanks for your help.

Anne

You probably won't need bootloader 1.7. This was released due to bug which might cause the handset to lock up when updating the handsets firmware  .

SynScan V3 hand controller firmware v3_37.zip

SynScan V3 hand controller firmware v3_36.zipen_download_caty01468002791.zip

Share this post


Link to post
Share on other sites

Thank you for those files. One other question, when I opened the loader programme from the Skywatcher website, if I click button that displays the current firmware at the bottom of the programme window, it showed 255 in all positions. Do you know why it didn't show my version 3.12 etc there? I was beginning to wonder if I have a problem in the serial cable, perhaps a wire broken somewhere. I don't have another lead to try as all my pc connection cables only have 4 cores. I don't really want to buy another cable if this won't do anything.

Share this post


Link to post
Share on other sites
2 hours ago, Anne S said:

Thank you for those files. One other question, when I opened the loader programme from the Skywatcher website, if I click button that displays the current firmware at the bottom of the programme window, it showed 255 in all positions. Do you know why it didn't show my version 3.12 etc there? I was beginning to wonder if I have a problem in the serial cable, perhaps a wire broken somewhere. I don't have another lead to try as all my pc connection cables only have 4 cores. I don't really want to buy another cable if this won't do anything.

I'm not sure why the firmware uploader is displaying 255.255.255, never seen that.  Does the handset display the correct firmware version ?

Share this post


Link to post
Share on other sites

Yes it does. It only shows 255 etc when I open the loader window and click on the handset button. When I try to update it says shows the error above. I haven't tried your files yet. I'm beginning to think it can't read the handset info.

Share this post


Link to post
Share on other sites

One thing to try, is to run the updater as Administrator, i.e. right click the application & select "Run As Administrator". that can usually get around a lot of the issues....

Share this post


Link to post
Share on other sites

I'm doing the update from a Windows 7 professional laptop, does that still apply?

Share this post


Link to post
Share on other sites
Posted (edited)

Hi all,

same issue here today...

the idea was updating from 3.35 to 3.39.

Before updating 3.39 firmware, updated Bootloader to version 1.7.

Synscan Firmware loader 3.3 said  "Update Completed" but  unfortunately handset stop working.

HC powered off /powered on and  HC  show  "Press Enter to renew Bootloader"... press Enter.. it said waiting... and Finished. But retrying power cycle display always same message "Press enter to renew bootloader", "Waiting", "Finished". 

So I tried booting on update mode (0+8) and it says Synscan 1.7 update .

RJ11  cable connected to HC, opened Synscan Firmware Loader 3.3, press HC Version display Hardware 255.255

If I try update (firmware 3.39 or older versions ) I received message "Version 3.xx firmware does not work on 255.xx hardware"

Did you resolve? 

Previous firmware update to version 3.35 worked without any problem , so no cable or pc issue :(

Regards,

Luigi

 

Edited by Gigi1982

Share this post


Link to post
Share on other sites

Update ! :)

I't a long story but I fixed my SynScan v3 ... 

After investigating the strange behaviour between different Synscan Firmware Loader versions, I suspected that problem was inside this software and not the HC Firmware or HC BootLoader (1.7).

These are my initial tests:

  • Trying an update to firmware 3.39.10 using Synscan Firmware Loader 3.3 -> FAILED - "Version 3.xx firmware does not work on 255.xx hardware"
  • Trying an update to firmware 3.36 using Synscan Firmware Loader 3.3 -> FAILED - "Version 3.xx firmware does not work on 255.xx hardware"
  • Trying an update to firmware 3.39.10 using Synscan Firmware Loader 2.6 -> FAILED - Update procedure starts but hang on 0.0% and after minutes return "Update failed"
  • Trying an update to firmware 3.36 using Synscan Firmware Loader 2.6 -> FAILED - Update procedure starts but hang on 0.0% and after minutes return "Update failed" 

So my considerations:

  • SynScan Loader 2.6 doesn't check Hardware version before update procedure
  • SynScan Loader 3.3 check Hardware version before update procedure

 

Second test: checking in-deep  communication between SynScan Loader and HC using a rs232 monitoring tool (acts like a tcp sniffer).

  • Press HC version on Synscan Firmware Loader 3.3 = Loader send "I" command through rs232 and HC return "255 0 3 255"
  • Press HC version on Synscan Firmware Loader 2.6 = Loader send "I" command through rs232 and HC return "255 0 3 255"
  • Press Update on Synscan Firmware Loader 3.3 = Loader send "I" command through rs232 and HC return "255 0 3 255" and stop
  • Press HC version on Synscan Firmware Loader 2.6 = Loader send a set of commands (Hex) command through rs232 but HC doesn't return a response

So my considerations:

Could be something related to new SynScan protocol 3.3, supported by Loader 3.3 but not the old 2.6 ?

Sysncan Firmware Loader 2.6

  • not able to use 3.3 protocol - ?
  • doesn't check HW version before update - sure

Sysncan Firmware Loader 3.3 

  • able to use 3.3 protocol - sure
  • check HW version before update - sure

 

Third and final test: Try another Synscan Firmware Loader version between 3.3 and 2.6

I downloaded  Synscan Firmware Loader 3.0 from a Dropbox link and repeated tests:

  • Press HC version on Synscan Firmware Loader 3.0 = Loader send "I" command through rs232 and HC return "255 0 3 255"
  • Press Update on Synscan Firmware Loader 3.0 = Loader send "I" command through rs232 and HC return "255 0 3 255" and start sending data for update :)
  • Press HC Version return Hardware  255 (not fixed)   Firmware 3.39.10  Database 3.28 

 

After update completed, reboot HC and now it works !!!

I don't know why Hardware version is wrong but HC returned to new life, tested tonight and worked great

 

So, in summary, my steps for FIX are:

  • Download SynScan Firmware Loader 3.0 (I don't know if forum permits links so send me a pm if you can't find it)
  • Download HC Firmware (tested 3.36 ,3.38, 3.39.05,3.39.10)
  • Run Update :)

 

Apologize for this long and boring thread but I hope it will be useful for other people

Regards,

Luigi

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

@Gigi1982 Just tried your fix on both of my v3 handsets which were stuck on v3.38.09. Both are now reflashed with v3.39.10 using the older v3.0 firmware uploader. 

Share this post


Link to post
Share on other sites
13 minutes ago, Cornelius Varley said:

@Gigi1982 Just tried your fix on both of my v3 handsets which were stuck on v3.38.09. Both are now reflashed with v3.39.10 using the older v3.0 firmware uploader. 

Nice :) I'm glad for you

I'm not a Skywatcher employee so the discovered fix should work for someone but I don't guarantee :) .

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By pete_81
      Hi guys,
      With new mount and upgraded scope features, now looking to venture into imaging.
      Before I start, I'm not looking to get feedback on polar alignment, mono guidecam, better imaging cameras, etc; this is more a 'dummies guide' setup discussion! I'm not expecting to get great images at this stage, just more the options available, getting over some issues, so that I can jump outside on a clear night with an ideal, foolproof(!), setup for either imaging or visual as time would permit and what may work best for me. As you may guess from the topic name, I'm a mac user (Macbook Pro) and would rather keep to this if possible (whilst I do have Windows (and Ubuntu) via parallels, I'd rather not use these).
      I've got a setup which has worked well for visual, and obviously want to have a couple of 'staple' setups that I can use depending on expectations of night observing or imaging. So far, the best one for me has been the Skywatcher Wifi Synscan controller, which has worked a treat with my Android phone - I use the Synscan app to complete alignment and GOTO stars/planets/DSO etc, or Stellarium_plus after completing alignment. This removes the need for the Synscan Handset and any USB cables to the mount altogether. But I don't know if this will work for guiding.
      That then brings me to my issue on mac - connecting USB(A) between Macbook and Handset, I've attempted to control the mount through Stellarium. Trying each of the available connections (/dev/tty.usbsetial-1420, /dev/cu.usbsetial-1420, and just for sake of it, the /dev/tty.Bluetooth-Incoming-Port and /dev/cu.Bluetooth-Incoming-Port) in the dropdown menu under DeviceSettings/SerialPort, I cannot get the mount to connect (well, more like selecting the telescope and clicking the "Start" on the TelescopeControl just results in the spinning icon and I have to Force-Quit Stellarium and start again with the same result each time. Annoyingly (for fellow mac users!), Parallels/Windows/Stellarium connects and controls the mount fine! As the mount is the newer "pro" type, I also have a USB connection directly under the hand-controller RJ45 and AutoGuider ST4 sockets, but using this still results in the same issue. Another issue I have seen is that when I unplug the USB from the computer when connected to the handset, the date on the controller jumps significantly - for example, last night at ~23:30, I was transported through the local wormhole galaxy to Jan 2048 according to Synscan! Obviously unplugging isn't going to happen during a genuine session, but just wondering if this is a possible issue somewhere?!
      Any other mac users connecting USB directly to the SW 'Pro' mounts?
      Software wise, would folks generally suggest steering away from Stellarium towards KStars or SkySafari(Plus) for controlling the mount?
      Can the Wifi dongle be used for controlling mount from computer (any OS) or do I need to go USB either to handset or directly to mount?
      Is there an issue in using Mac USB to the telescope compared to 'straight' Windows (i.e. PC/laptop with Windows instead of virtual)?
      Anyway, back to topic... I've a Nikon DSLR to use for primary camera at this stage, which would be triggered independently from guiding software. PHD2 is my hopeful choice of guiding software (is EKOS with KStars similar?), with T7C guide-camera on 240mm f/4 guidescope, and at this stage, I can confirm PHD2 at least connects to the camera on OS-X. There is an ST4 port on the camera, but having read several topics, I think I want to pulse-guide directly - is this correct or is ST4 best for this setup? This sorta comes back to software and connections - my understanding is one of the following cable setups for guiding (as a minimum) :
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => SynscanHandset => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => USB(A) => AZEQ6
      Guiding-camera => USB(A) => Macbook => PHD2 => Wifi => SynscaWifi Adapter on AZEQ6
      [using ST4: ST4_on_AZEQ6 => Guiding-camera => USB(A) => Macbook => PHD2] (no additional connections needed if ST4 is used)
      Additionally, I'd like to use an observatory package, say Stellarium/KStars/SkySafari, to select objects and drive the mount, then use guiding software to keep good 'tracking'.
      Where in this train does EQMac fit in, or when is it used?
      What about the 2019 addition to EQMod (ASCOM Alpaca)? Can this be used or is it already in other packages?!
      For Windows users, how does EQMod fit in (if I go down route of getting Windows laptop for controlling things, is the setup similar to above?
      There may be bits in the above that repeat, and for that, I'm sorry, just want to get across the message that I'm new to the guiding but haven't quite settled down into the software/hardware I'm expecting to use for 'goto' and 'guiding'
      TLDR:
      For a mac user, what setup and software are folks using for guiding and observatory softwares for the newer USB-on-mount 'AZEQ6/EQ6-R Pro' mounts from SW?
    • By Marsto
      Hi
      I am looking for help and advice on my SynScan EQ5 pro problem which i am struggling with. Everything was working fine and as expected. I have never updated the firmware and thought while i had everything connected i would update the Hand Controller and the skywatcher WiFi dongle. 
      Everything updated first time without issue and i was pleased to be up to date. However i loaded SynScan app on the pc which connected fine through the handset and USB/Serial adaptor cable. I clicked on the movement arrows and nothing happened, i then went in to a random 1 star alignment and again no response from the motors. 
      I powered off again and instead of the PC i tried the hand controller, i tried a 1 star alignment and the hand controller was displaying the slewing but again no response from the motors. in panic i then did the same with the WiFi dongle and phone app, same thing the software is showing movement but the scope remains still. 
      Knowing all was well prior to firmware updates i reverted back to the previous firmware version and no difference, i tried it again in Lo mode and still nothing. I then noticed a firmware update for the Motor Control so thought i had nothing to loose i updated the Motor Control firmware and again no sign of life from the Motors. I have swapped the cables around, checked that they are all inserted correctly, the power is from mains not battery and the power source is plugged in to a a Power Filter and Surge protector. 
      I have little experience of circuit board electronics, i was struggling to find similar experiences online other than voltage issues due to batteries which is not the case. I have opened it up and no obvious loose cables of solder loose, but this was straight after the firmware update which seemed to have installed and updated very smoothly no crashes etc. 
      Any help would be really appreciated. 
       
    • By Eichan
      Hi all,
      I own a NEQ6 mount and EQDirect cable, but the RJ45 version. The NEQ6 uses a DB9 port, so I got an adapter but I need to wire it myself. See attached picture of my adapter + EQDirect. I am quite unsure how to wire my adapter. The first diagram here should tell me how, but I'm still not sure I get it. If I look at the EQDirect adapter (see attached close-up), it looks like on pin 1 & 2, when the diagram says there should be ground there. Also someone in an INDI forum told me I could ignore the 12v pin as it would be supplied by the mount, but the RJ45 actually seems to have something on those pins.
      It's tempting to just look at the wiring of both adapters and trust the colors, but I'm afraid making mistakes here might damage the mount...
      Any ideas?
      Thanks
      EDIT: I own this RJ45 to DB9 adapter. Would any of the proposed wirings in this document work for my need?


    • By Mick the Lob
      Hello all fairly new to this  astro photography malarkey and seem to of jumped in above my head. I have a eq/az Skywatcher mount..i have set the cords into the hand set and it was about 90 degrees away from target,looks like I somehow mixed the lat and long having rectified that the mount appeared to slew to the correct position but when I set it up on one of the very few favourable nights I find it still is not in the ball park . I have further noticed I had set the ground elevation to minus 25 metres when it should of been plus 8 metres so a good 33 metres  out of wack, going to try again tonight just hoping this does the trick if it don't, will be needing help. Would this error in elevation cause this sort of error.
      Regards Mick 
       
    • By MattsGazingAgain
      Hello all,
      First post since my initial hello message due to a lot of cloudy nights and a small wait until I could afford my very entry level camera. I would like to apologise straight away for my lack of knowledge and the poor quality of my images. The framing is terrible and they're out of focus, but I'm also completely over the moon with them. I'm very eager for you guys to rip them apart and tell me all the ways I went wrong but I will always love these 4 images as they are the very first successful AP images I've taken
      My equipment is as follows
      skywatcher 150pds on a eq3-2 pro synscan mount
      Polar scope
      Canon 2000d
      Super coma corrector
      I have tuned the motor drives for the mount but haven't stripped down and cleaned and greased the mount itself yet but plan to. Also plan to upgrade to a heq5 Pro asap. I have no guiding other then synscan. Again something else I hope to change as soon as I can but for now its an oppurtunity to learn.
      None of the images are stacked, they're single 30 sec exposures. I very slightly adjusted the raw files by placing a slight s curve on the linear channel but will leave any further processing if I bother until after a good nights sleep. I've included both the before and after image.
      The first image is just of vega, I took it while star aligning. A awful pic for many reasons, especially the flare coming from the star, but my first so will keep it for sentimental reasons. The second I was very happy to catch some light from the ring nebula, and was equally happy to catch the dumbell nebula a little. The fourth is the globular cluster. All really bad framing but was suprised to catch the nebula on just a 30 sec exp with my light pollution. 
      Can't wait for your ideas,suggestions and criticisms. My apologies for a very long post but feel very hyped up even after such awful results.
      Many thanks and clear skies
      Matt
       








×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.