• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 62 subscribers
  • Views 406 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

EV2200-4- Evaluation system for bq2040 gas gauge - data entry problem

Harry Trietley
Prodigy 80 points
Other Parts Discussed in Thread: BQ2040

EV2200-40 evaluation system for bq2040: When I enter new data on the screen to write to the eeprom, I have a problem with Charging Voltage and EDVF. On both, as soon as I enter even a single number or character an error message pops up, "Run time error "13". Type mismatch." When I click "ok" (the only choice) the program just ends and drops off the screen. All other entries except these two work ok.

  • 0
    TI__Guru 73830 points

    Harry

    This looks like a tools mismatch with the device. Have you tried rerunning the setup program to see if it was corrupted? Have you seen it occur on more than one EVM?

    Regards

    Tom

  • 0 in reply to ThomasCosby
    Prodigy 80 points

    Thanks, Tom,

    I have not found the cause, but I did find a work-around. It seems that I get the error message only if I delete the existing number in either of the two fields. If I enter my new number without first deleting the old one it works ok. For example, if the field comes up with the number 8000 in it, and I delete the left-most three digits but not the last zero and then enter my new number (such as 7530) it accepts it ok.

    I have not been able to find a definition or explanation of "Run time error 13 - Type Mismatch".

    I have two EVM systems. Both are using Windows XP.  Both behave the same. The first is several years old and is on a very old Toshiba laptop which has a DB9 RS232 connector. The second was purchased this month and is running on a 3- or 4-year old Dell laptop. It is connected to the EVM through a USB to serial converter.

    I get the same result whether the computer is connected to the EVM and otherwise running correctly, or if it is not connected.

    The work-around has solved my problem, but if you or anyone can shed any light on this I'd still like to know.

    Thanks for taking the time to respond.

    Regards,

    Harry Trietley, JH Technology, Inc.