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.

bq80xRW.ocx Crashing VS2013

Other Parts Discussed in Thread: BQEVSW

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

  • Pete,

    It looks like there may be an issue with the EV2300 development kit installation. This link may help.

    Tom

  • Tom,

    Thanks for your input. I have reloaded Windows to make sure no other programs were affecting the installation and only using the latest development kit. the problem remains. As I stated before, the bqEV software will work and my compiled software will work that uses the bq80xRW.ocx ActiveX control but Visual Studio will not load the control and crashes. Keep in mind the applications that work, were previously build on a WindowsXP machine and Visual Studio 2005.

    -Pete

  • Any resolution to this at all? I have a similar issue with this control?

    Not sure why TI doesnt make everyone life easier and just release the icd to comm directly to the EV boxes over usb.

  • Michael,

    See my post here: bq80xRW.ocx Crashing VS2013

    This is my attempt at answering this question. I did not find root cause but a work around.

    I found that the AxHost in VS2013 will not work with the bq80xRW.ocx ActiveX control until it is first wrapped in an earlier Visual Studio IDE, i.e. VS6 or VS2005. I did not try VS2008 or VS2010.

    -Pete

  • Pete- 

    thanks for the response, so basically a DLL or program to talk to the final DLL.....not very efficient....I am guessing TI doesn't actually have the source code and know what the current DLL is actually doing....I could sniff USB out I guess and create my own ICD, but what a waste of time. 

    Mike

  • Mike,

    Yes, you can create an extra DLL or wrapper but you only need to run the program once to fool the Visual Studio AxHost.dll (ActiveX Host). You can then add the bq80xRW.ocx to your new project as normal and abandon the wrapper. I still think it is related to how the TI bq80xRW.ocx manages its license file and is incompatible with the new AxHost for Visual Studio. However, I don't have time for a science project to take it to root cause.

    -Pete