With both IE 11 and Chrome (44.0.2403.157) the file downloaded does not appear to be executable. The downloaded file is sluc525m with no extension.
Thanks in advance for any help,
Seth
p.s. I apologize if this is the wrong forum. Seemed like the closes match...
Looking through the bq40z60 datasheet SLUSAW3C I am confused by the naming of components in the charging circuit. Firstly, what is meant by AC Adapter? Is this a wall wart that converts 115vac or 230vac to a lower DC voltage or just converts to a lower AC voltage? AC FET - is this FET so named because it deals with AC voltage? ACP - Adapter input pin, for AC voltage or DC voltage?
The datasheet seems very ambiguous regarding whether to apply AC or DC to charge the batteries. Am I the only one confused by this?
Also, the charging voltage level is not obvious. We are charging a series string of 3 LiFePO4 batteries with a "standard voltage" of 3.2V and cutoff of 3.65V. With three in series we have a standard voltage of 9.6V and cutoff of 10.95V. The datasheet, under section "11 Power Supply Requirements" states "well regulated input voltage supply range 4.0V and 25V.. multi-cell pack, the input voltage should be minimum of 1V above maximum stack voltage." In our case, is maximum stack voltage equivalent to our cutoff voltage of 10.95V? If so, what does well regulated mean in this context, i.e., regulated to what percentage of 10.95V?
Thanks, -mark
Has anyone successfully used the EV2300 ActiveX control in a Windows7 VS2013 Visual Basic environment? I am getting reports from TI, many folks are actively using it but I have had no luck. I can add the COM Component to the Toolbox just fine so it is registered. If I drag it to a form Visual Studio crashes. I have also tried to instantiate the control with code only without dragging the object to a form and get the same result.
I there is a license file** required when using the bq80xRW.ocx control at runtime when running in Window 7. The program will throw a memory access violation exception. I have noticed many other folks have had this problem on the E2E forum but did not get an answer from TI. The only instructions I see are to install the drivers in the customer kit for the EV2300.
I suspect the VS crashing issue may be related to the license file but I haven't found any documentation on how to remedy the problem at design time.
**
EV2300 Customer Kit
The easiest approach to development is
1. Install USB drivers
2. Install any EVSW that uses the EV2300
3. View bq80xRW.hlp and the sample project to start coding in VB.
Its necessary to create a license file for any app that you write. This is a simple text file which is placed in the application folder. It must be named the same as the application, but without any extension. In the file, you place the number of bytes in the application. That can be found from right clicking the application and looking at the properties for the size. It usually looks something like this:
size: 880 KB (901,120 bytes)
The text to put in the license file would be 901120 (no commas allowed).
To ensure that it works on all machines please make sure of the following
1. For a file called "Sample.exe", right click and select properties. Note the size in bytes of this file.
2. Open notepad and type in the size in bytes(without commas). Save this file as "Sample.txt"
3. Rename "Sample.txt" to "Sample"
4. Distribute "Sample" with "Sample.exe"(both files must be in the same directory)
5. Install the bqEVSW on the machine on which you wish to run Sample.exe
I have a custom PCB with a 2.6Ah 4 cell pack. On multiple boards now, over time, I have observed failing (burned out) PCB traces between the battery connector and the VC1 through VC3 voltage sense inputs. I am using 100 ohm current limiting resistors and the traces are 12 mil (0.5oz/ft2). The datasheet indicates that these paths are used for cell balancing and that bypass FETs are used to charge one cell at a time. What is the theoretical maximum current that can flow through these paths?
We have been following the process below with a 4400 mAh battery.
We can successfully complete the first three steps of this process. During step four, VOK is cleared and OCVTAKEN goes high, but UPDATE_STATUS and Qmax never change. We let the battery sit for several hours with no change.
I've attached the log files.
(Please visit the site to view this file)
Thanks,
Allison
Hello,
Can somebody tell me what is the I²C command to reset the BQ2084 as we do in the BQ2084 Advanced Gas Gauge software (in special options)?
Thank you
David
Using our prototype boards and software we are able to enter ROM mode, read Data Memory and exit consistently with out any problems, Then testing out the ability to write data memory we chose a seemingly unused section to write 32 bytes starting at 0x5000 and verified by reading it back. After this we could not get it to exit ROM mode, We could still read Data Memory, but after a day all that we could read back were 0xFF. What did we do to the part and how can we recover?
Is there some document that shows the preferred method to write data memory?
Tony
I am using a bq27425 to gauge a Lithium Ion rechargeable battery that has a nominal capacity of 400mAh and a discharge end voltage of 2.1V.
I set those values into the GasGaugingState table. But, I read bogus values for the Avg Current and Avg Power. Worst of all, I get 0 for the StateOfCharge. It never goes above 0.
It seems that the chip is not measuring the Charge (Q) across the sense resistor. What could cause this failure?
I have an 800 mah lithium cell with a bq27541V200 circuit. Also in the battery is an msp430 that reads the data from the BQ via its HDQ. The msp also connects to, and makes the data available to, the outside world (hosts) via its own I2C. The msp also operates up to 4 LEDs in the battery. The LEDs indicate SOC. One of the hosts is a charger. When charging, the LEDs function. When full the four LEDs draw 15 ma. I have the VSS of the MSP and the VSS of the BQ together at the Cell-' Therefor, at the end of the charge cycle, as the battery sets in the charger, there is a 15 ma load on the cell. Because this 15 ma is returned to the cell-, the BQ is not seeing this load.
My concern is that the BQ will assume the battery is at rest and update the qmax, etc when in reality, there is a small load on the cell. Would this small amount of current have an affect on the accuracy of the SOH?
dpk
Generated a golden file '0510_4_00-bq27510G3.df.fs' using bqstudio. Attempted the upload and filed at line 17 as shown below.
W: 16 00 03 00 00
W: 16 64 03 00
X: 20
C: 16 66 00
W: 16 00 02 00 00 00 EA FF 33 24 FA 33 B8 FA 33 3D FE 33 45 FE 33 FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F FF FF 3F 00 04 3F 58 CB 33 DB 00 08 00 00 00 00 00 00 FF AA 0E FB A7 0E FF A6 0E FF A1 0E FF A0 0E FE A3 0E 77 A2 0E D2 FF 3A FF A1 0E 66 A0 0E FF A3 0E
W: 16 64 1B 35
X: 2
C: 16 66 00
W: 16 00 02 01 00 00 64 A2 0E BD A5 0E 2F A4 0E CA FF 3A FE A1 0E 77 A0 0E FE A3 0E 77 A2 0E CA FF 3A C2 FF 3A D6 FF 33 FF AF 0E 01 4F 03 3F 11 0C CD FF 30 D4 FF 35 2F 10 0C D4 FF 35 FF FF 23 01 AF 14 01 4F 03 3F 11 0C C5 FF 30 CC FF 35 2F 10 0C CC FF 35 FF FF 23 FF DF 0B C4 FF 33 60 F6 39 FE AF 16 C1 AB 0E
W: 16 64 7A 2E
X: 2
C: 16 66 00
W: 16 00 05
W: 16 64 05 00
X: 170
C: 16 66 00
C: 16 04 93 2D 8D D3
Line: 017 Failed response, Expected 932D8DD3 got 00000000
I cannot switch back to firmware mode by executing the flash code sequence.
W: 16 00 0F
W: 16 64 0F 00
I tried a power cycle reboot but still cannot switch back.
Is there any way out of this?
Is there a procedure or process to recover a bricked device?
On a previous question I asked for an explanation of what the undocumented commands within the golden file are doing but have not received an answer. For example in the segment above, what exactly failed?
I am using a bq27425. It does indicate the State of Charge % when the battery is charging. But, it shows 0 when the battery is discharging. What could cause this? And, how can I get a valid reading when the battery is discharging?
Dear all,
I am using BQ34Z100-G1. I can write some of the data flash but not all.
For example, if I want to change Sleep Current in Power subclass, I do the following things.
However, if I want to change FS Wait in Power subclass.
Nothing changes.
Can anyone help? Thanks
Hello. I am hoping to use the BQ34Z100-G1 with a 10S stack of NiMH cells, capacity is 10,000mAh. The exact cell model is not offered on the Chemistry page of Battery Management Studio so I have selected 6103 and set all other registers to suit the pack. Is this sufficient, or do I need to model the pack more precisely ?
Thanks
Richard
Hello,
I have problems with the standard internal balancing configuration of the TI BQ40Z50.
I'm using BQ40z50-R1 Firmware, with 100 Ohm resistors on the circuit. The circuit is adapted from the EVM-Ciruit. The battery is a 4S1P with Samsung INR-18650-29E. The flags for Cell Balancing [CB] and Cell Balancing at Rest [CBR] are enabled (=1). OCVFR Bit is disabled (=0).
As shown on the attached image after a fully charged termination the cell voltages drop down and the device starts with internal balancing. Cell 1 is the one with the lowest voltage. Balancing correctly starts to decrease the voltage of cell 2, 3 and 4. Although cell Voltage 3 has droped down to cell voltage 1 the balancing continues. Similar happens to cell voltage 2. Annotation: the voltage drop at time ~50000 is caused by a 3A discharge.
I would have expected a balancing of the higher cell voltages down to the lowest cell voltage, as described in the TRM.
1) What is the reason for this behaviour? How can i get it under control?
2) In firmware BQ40z50-R1 the [CBM]-Flag is RSVD. I assume it is set to 1 permanently. So, the balancing should switch from cell to cell and not balance several cells at the same time? The image shows contemporaneous balancing of several cells, doesn't it?
Thanks for reply,
Simon
(Please visit the site to view this file)(Please visit the site to view this file)
I am down to what I hope is my last problem in using the bq27425 Fuel Gauge chip. The problem is that I do not get usable values in response to the commands that relate to the battery capacity. Specifically, I get zero (0) for
NominalAvailableCapacity 0x08/0x09,
FullAvailableCapacity 0x0A/0x0B,
RemainingCapacity 0x0C/0x0D, and
FullChargeCapacity 0x0E/0x0F.
And most troubling of all I get 0 (zero) as the value for
StateOfCharge during the first 5 minutes of inquiry (if the battery is charging) and then I get 100% forever after.
In addition, I get 0 (zero) for all inquiries of StateOfCharge always if the battery is discharging when connected to a load without being simultaneously charged.
Furthermore the StateOfHealth 0x20/0x21 always reads 0x100 (even though the spec claims that its max is 0x64)
I am having so many problems related to reading the battery that I feel that I need to speak directly to an expert. I have tried putting my questions on the E2E bulletin board before, but I do not get the help I need. Can I please get connected to an expert.
I am Richard Brisk a design engineer at Kopin Corp.
The phone at my desk is (508) 870-5959 x117
My personal cell phone is (774) 270-0093
My email is RBrisk@Kopin.com
Please call or write with information as to how I can connect with an expert directly.
Thank you,
Richard Brisk
I am not getting valid information about the battery capacity, % and the like. In trying to understand the problem, I see that the Status Word (the Control Status register) indicates that the RUP_DIS bit is always set. The spec tells me that means that my Ra table is never being updated. Is that a problem? Is that something that would cause bad reads of the battery information?
When I compare the EV2300's commands to the bq40z60 to that listed in the technical reference manual I don't quite understand what is going on.
for example, the technical manual says to read chem ID you send (Command: 0x44, Data: 0x 06 00) but what actually sends is (0x 44 02 06 00 12) .
I've come to understand that the second value when sending commands indicates the length of what you're sending. In the example above it is 2 because 06 00 are the two bytes. When I read blocks like 0x71 it will tell me there are 32 values to follow. Am I also to presume that the last byte is some sort of parity byte for the system? It changes with every unique command, which makes me feel like that's what this is.
I'm wondering for when I send my own commands to the bq40z60 through a microcontroller or host of some sort, will I also need to include these extra bytes that aren't mentioned in the technical reference manual?
Hi, I'm writing a library for the BQ27742-G1 fuel gauge, I don't have any problem at all when reading standard commands like Voltage(), Temperature(), etc. but I'm being unable to read back control commands like HW_VERSION, FW_VERSION, etc. Most likely I'm doing something wrong.
For reference, this is what I do to retrieve HW_VERSION:
Issuing the command and subcommand:
- Write: address | 0x00 | 0x00 | 0x02 | STOP
Write control address to read the results
- Write: address | 0x00
Then I read back 2 bytes (for 0x00 and 0x01) but I'm always getting 0x8018 as a result, no matter what subcommand I write. I also noted that If I read the control register without issuing any previous command I get the same value (0x8018).
Any help would be greatly appreciated.
Thanks
EDIT: I detached and attached again the battery from the fuel gauge board and now I'm getting 0x0008 instead, no matter what subcommand I write.
Just wondering of anyone has had any experience with the LTC1760 locking up when the user removes and replaces the battery within a few seconds. This does not happen very often, but I would like to explore why this happens and if anyone may know of a fix. I know this is not a TI part, but many TI users have used this part along with their TI processors to control battery charging. We also use an MSP430 to control the LTC1760. I have not been able to find any reference to this problem on other forums. Any help would be appreciated.