1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. ABB Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

S4C+ DSQC508​ 3HAC5393-2/XX revival

  • pynting
  • February 19, 2021 at 12:49 PM
  • Thread is Unresolved
  • pynting
    Trophies
    3
    Posts
    4
    • February 19, 2021 at 12:49 PM
    • #1

    Hi, I have the same issue as many, my battery unit DSQC508 3HAC5393-2/XX (07 in my case) is end of life and the counter is at 0, my revision number is below 10, so the whole unit needs to be replaced... This is really wasteful if you ask me, and I don't know what technical reason there is for this very blatant example of planned obsolescence.

    I lifted the sticker on the MCU and saw that the "brain" of the board is a regular old Atmel AT90S8535. It has 512bytes of EEPROM, and my theory is that there is a counter of some sort which value is stored in EEPROM. If this is the case, one could (hopefully) with relative ease flash the EEPROM with another value, breathing new life to the board.

    If the revision number of the board deals with changes in the firmware only, one could perhaps just flash the firmware of the later revision on to an earlier board?

    As of yet, I have not been able to read from the chip, but there is a programming connector on the board (next to the MCU) with at least the following pins exposed:

    PIN CHIP

    1 TXD

    2 RST (prog)

    3 SS

    4 MOSI (prog)

    5 MISO (prog)

    6 SCK (prog)

    7 RXD

    8 GND

    It would be great if someone else was willing to help out with this. It could save people some money if they were able to replace the battery only by applying this fix!

    If we go the "flash EEPROM only" route, the easiest would be to compare the EEPROM of a chip on a board with time left on it and an zeroed out board (my board). Then we can probably see the right address of the counter.

    If we get the firmware of a later revision board, we should probably do a detailed comparison of the PCBs themselves and look for physical differences between the two boards. If there is none, one could presume that it would work flashing the new firmware onto the old board?

    I do not have the board in front of me ATM, but will update the post later today with more details.

    I really hope this could be a solution. If anybody has these boards and was willing to help, that would be great!

    Edited once, last by pynting (February 20, 2021 at 5:11 PM).

  • RobotsSolutions
    Reactions Received
    1
    Trophies
    3
    Posts
    27
    • February 19, 2021 at 2:07 PM
    • #2

    Hello

    We did that kind of researches a few years ago, and, as far as I remember, it's not a timer question.

    The default is kept in memory and won't be erased even if the battery is replaced.

    Because the REV07 is not having the same chip than REV08/09/10, we used to flash the REV07 chip and upload programm without default in memory.

    REV08 and 09 can be flashed with the REV10 program, as the chip is the same.

    It's not possible to "transform" REV07 into REV10.

    To resume :

    REV07 can only be flashed with a programm free of default.

    REV08 and 09 can be transformed into REV10.

    REV10 and higher won't keep the default memory, and allow the replacement of battery only.

    Hope this helps :smiling_face:

  • pynting
    Trophies
    3
    Posts
    4
    • February 19, 2021 at 2:42 PM
    • #3

    Very interesting and insightful response!

    And thanks for letting me know that the work has already been done, saves a lot of time wasted.

    I do not entirely understand what you mean by "default"? It is strange to me that that there is no sort of stored (and changeable) counter value. How else can it know how much time is left until it needs replacement?

    Do you have the binary file for the REV07 chip to reset it?

    And for others that need it, the REV10 binary as well, so that those can be replaced?

    Do you know if the MCU of the REV08+ board are pin compatible with the REV07? In that case, do you think it is feasible to do a chip swap?

    Edited once, last by pynting (February 19, 2021 at 2:53 PM).

  • dzoph666
    Trophies
    1
    Posts
    1
    • December 17, 2023 at 7:22 PM
    • #4

    Hi there, nice to meet you all!

    I have a lot of DSQC 508 rev.10 ATMEGA8A, that I get to modify some rom.

    When I shut the robot, the DSQC 508 stay´s alive, but seems that reset the system and starts again some 3 or 4 times and dont make the backup. Using Lockbits1.
    I have other versions too rev 07/08/09 AT90S8535.
    If someone could help with the rom´s of these versions we can pay for it.

    ASAP please, help!

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Tags

  • Backup
  • Battery
  • firmware
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download