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.

sgl_imaging_challenge_banner_lunar_landings.thumb.jpg.b50378d0845690d8a03305a49923eb40.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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By PlanetGazer
      I was hesitant to write this earlier, but I wanted to try all possible ways to get my new SkyWatcher 250P GOTO allgined, but to no avail.
      I have followed the instruction manuals of both the synscan and SW, and managed to get the message "alignment successful" multiple times on the handset or the app. The closest I got when I tried to dial a different star was a 20 to 25 degrees off on the azimth axis. Most times it's off by a margin on both axes.
      I have tried aligning around 30 times on more than 5 diffrenet occasions, different locations as well. I end up ignoring the thing and switch to navigating manually as the eager friends want to observe instantly, but we ran out of objectes and the planets are not close anymore, so I figured it's time to get deeper DSO's and sort out the GOTO.
      Here is what I do:
      • I level the scope to the zero reading on top of the base
      • I make sure the base is level with a spirit level I bought recently
      • I point the scope northish, but latley I bought compass to pinpoint north
      • I plug all equipments in and then switch on the power from a lead acid battery
      • I enter the date ( US fromat, month before day 😕 )
      • enter correct time zone obviously
      • the coordinates in the format of E 000 00 , N 00 00 
      • As for  elevation I use "my  elevation" app, not sure if it's accurate. Does this entry have to be that accurate?
      • I tried both brightest star and the 2 star align methods on the handset (which seems to be the same thing apart from the brightest method having an extra menu asking for which direction you are pointing at)
      I even used the synscan app and the synscan pro, and tried the 3 star align method. The app uses location and enters all data automatically
      •I use the top and right arrows as the last press before centring the star in the eyepiece as  recommended by the manual
       
      These are the steps I follow when I align , is there anythung I missed? Your kind help is much appreciated.
       
      Update: issue solved, check the reply in the second page
       
    • By Oslet
      Sooo...I'm getting quote frustrated here. This spring I tested my HEQ5 with guiding. The synscan controller was connected to the computer trough the USB plug on the hand controller. This worked like a charm in my living room. On the new controllers you dont need the rs cable. But when I tried the whole thing with guide cameara for some live shooting, it just did not work. I get something wrong with the com port in decice manager, driver not working. I have tried 3 different drivers. The whole thing responded, connected and was guiding when i did a dummy test before the summer. So setup is pc-synscan via usb for pulse guiding. Can it be a problem with windows 10? What t h.... just happened? Where can I find a driver that works? And believe me it worked 5 months ago, argh. Thanks for any respons and support
    • By tooth_dr
      I scrapped all the Oiii and Sii data I previously took during a full moon (about 15 hours worth) and retook it all when the moon was a bit smaller at 76%.  Ha was taken during 98% and 67% moon.  All the lights were taken on the following nights: 12th, 19th and 20th September 2019.
      Integration times, all in 600s subs unbinned:
      Ha = 28.33 hours
      Oiii= = 5.67 hours
      Sii = 5.67 hours
       
      The Ha data is really nice, and unsurprisingly the Oiii and Sii is not as strong (or nice).
      I'm missing that (vital) step in my processing routine of getting the Sii and Oiii properly stretched to match the Ha, before combining.  I dont really know how to deal with the weaker data properly.  Any pointers would be appreciated.
      What I do currently:
      All the data is loaded into APP into separate channels/sessions.
      The data is stacked and registered against the best Ha sub
      This produces individual stacks of Ha, Sii and Oiii that are all registered
      Each channel is processed with DPP in APP and then saved as a 16bit TIFF
      Each is opened in PS
      Stars removed with AA and any remnants removed and tidied up
      I then open a blank RGB document in PS
      I paste Ha into Green, Sii into Red and Oiii into Blue
      Adjust the selective colour settings to get 'Hubble palette'
      Adjust levels, curves, saturation until looks ok
      All the Ha Sii Oiii data is then combined together in a single 'super' stack in APP using quality weighted algorithm to create a 'luminance'
      That luminance layer is adjusted using levels, curves, and NC tools such as local contrast enhancement and deep space noise reduction (using masks to apply as required)
      The luminance is pasted onto the above colour layer, and incrementally added using gaussian blur
      Cropped and saved.
       
       
      Here it is anyway   I haven't intended on any more exposure time for this one, but will consider it, if the expert opinion dictates otherwise!
       
      CS
      Adam
       


    • By Phillips6549
      With several clear nights over the past week,  I've been playing with the Synscan Pro app (Android) in conjunction with a Synscan WiFi adapter on an EQ3Pro mount.  I have to say I'm generally quite impressed.  Much cheaper than buying a traditional handset.  
      However,  this evening I was trying to "creep up" on the Andromeda Galaxy by star hopping towards it via Mirach,  Mu Andromedae and Nu Andromedae.  Mirach was no problem but the other stars were not available for selection in the app.  Am I missing something?  I couldn't find any way to enter an SAO number or any other catalogue number to find the minor stars.  
      Is this a limitation of the app?  Or the adapter perhaps?  Or is it me? 
      Clear skies, 
      Mark. 
×
×
  • Create New...

Important Information

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