Compiler/EV2300: EV2300 Protocol

Hello,

We do not have a public specification for this interface.

Best Regards,
Dominik.

Hi,

Thanks for the response.  Do you have any recommendations?  I need to either automate the logging of battery data so I can interrogate the log, but without the GUI (I can't have the bq software at the front of the screen, so can't manipulate the mouse to the relevant places on the screen), or receive the data directly (i.e. not from the log).

Kind Regards,

Johnny Beardsmore

Hello,

You can start a log file in bqStudio (Registers->Start Log) and leave bqStudio in the background. You can parse the text file that bqStudio creates with a custom program and extract the information from the gauge from this file (the file gets updated periodically).

Regards,
Dominik.

Hello,

Does bqStudio work with the EV2300?  When I start up bqStudio, it detects device 0100_0_06 but there doesn't seem to be a corresponding .bqz file.  If I select the 010_0_16-bq34z100G1.bqz (this has the most similar name to the device), the values bqStudio reads seem correct, as I can change them and see the change reflected on the dashboard.

Is there a way to automate the starting of a log file for a register?  Is there a way to automate the selection of the device when bqStudio is initiated?  What I really need is the ability to start logging completely automatically.  Presently I use bq Evaluation Software, and force the mouse pointer onto the various parts of the GUI.  This is automatic, but doesn't allow other programs to run as modal (at the front of the screen), until the logging process has started, as any other program would obscure the screen, and therefore inhibit the mouse pointer from making its selections.

Cheers,

JB

The bqStudio program does work with the EV2300, it does not support the original bq34z100 device. The program supports the bq34z100-G1 device. You will need to use the older bqEvaluation Software tool with the bq34z100. You can upgrade your bq34z100 firmware to bq34z100-G1 using bqStudio and the new firmware is available for download on the bq34z100-G1 product website. Here is a link to help with the upgrade.

e2e.ti.com/.../1595705

That worked perfectly first time. The bqStudio now starts up and recognises the device automatically. Many thanks.

So, is automatic logging possible? i.e. with no mouse or keyboard clicks?

We do not have automatic logging, but you can start logging by pressing the "Start Log" button located near the top right corner of the Registers screen.

OK. I feel like i'm kind of back to square one here. I started this process to enable me to automate logging. I've since moved across to bqStudio (from the bq evaluation tool), and have updated the firmware of the EV to work with bqStudio, but can still not automate logging. Is this a facility which will ever be made available? Could i be implemented into bqStudio? Or could the details of the protocol be made available, so the data can be interrogated at source?

Maybe there is some confusion as to what automatic logging is. bqStudio will log data automatically, but you have to tell it to start by pressing the "Start Log" button. It will save the log file to you computer. The bqEVSW program will do the same. Are you trying to log data to run the optimization cycle?

I agree.  The logging happens automatically once it's started, but requires a manual start.  Its that bit of automation I was hoping to obtain, as the functionality of bqStudio is the same as bqEVSW from a logging point of view.

The purpose of the logging, in my application, is so the logged data can be parsed, and passed on to the user to provide real-time updates of battery voltages, etc. , via a secondary application.  The main issue I have, is that start-up is not very clean, as the bq software has to remain at the front of the screen, to start logging (using automated mouse clicks, etc.), before the secondary application can be initiated. If logging could somehow be started in the background, this problem would go away.  That's why I has hoping for an API of some kind.

Our tools do not support such an automated logging feature. You could design a uC (host) system that can read and log the data that you want to collect.

Thanks for the response. This uC (host) seems promising. Could you supply a link to some documentation please? My search has only revealed certain product specific queries which people have posted.