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.

Programming with bq80xRW.ocx

Other Parts Discussed in Thread: EV2400

Hi all

I have programming with bq80xRW.ocx in VB6 for many applications.

But I have a question about that bq80xRW.ocx.

Every time i want to use it for multiple process. I have to make an ActiveEXE for reference.

So that i can open multiple EV2300's at a same time. If not doing like this as using ActiveEXE.

I can only using one EV2300. At the same time I can not open another EV2300's in the same application.

I have ask our FAE engineer for more information. But didn't get any response.

Please provide more information of using multiple instance of using bq80xRW.ocx

Thanks for advance.

  • Sammy,

    There can be only 1 instance of bq80xrw.ocx per process. It is implemented as an ActiveX control.

    In order to open up multiple EV2300 each connection must be in a separate process.

    An ActiveX exe utilizing bq80xrw.ocx is the easiest solution. You can expose an interface from the ActiveX exe and then your application can create multiple instances of the ActiveX exe to communicate with multiple EV2300s.

    Regards,

  • Hi Shirish

    Thanks for reply.

    I have already done this way about 2 years ago in my production line.

    I just want more convenience and easy way to using EV2300.

    BTW. Thanks !!!

    Sammy

  • Is direct access to multiple EV2300/2400's now available?

     

    Dave

  • Would really like to find out if this is ready?
    I have EV2400 and EV2300 that I need this function.

    Thanks!

  • Hi Shirish,

    I am having some issue trying to use the Bq80xRW.OCX in vb.net (VS2008).  When I add the Bq80xRW Control to the form, the following error message pops up: "Failed to create component 'AcHost'.  The error message follows: 'System.AccessViolationException: Attempted to read or write protected memory.  This is often an indication that other memory is corrupt. ..."  Could you please release a new Bq80xRW Control for the .NET environment? 

    Thanks,

    Al 

  • Al,

    Please install the EV2300 customer kit

    http://e2e.ti.com/support/power_management/battery_management/f/180/t/57807.aspx

    The error you see is usually caused by an incorrect development environment. Installing the kit should fix any environment related issues.

  • Hi Shirish,

    I have a Windows7 PC and the EV2300 customer kit has recommended that "this only be used with computers running Windows 2000 or Windows XP".  Because Windows XP is no longer supported by Microsoft, that's why we are migrating our software from Windows XP and VB6 to Windows 7 and VS 2008. 

    Please let me know what to do next.  

    Thanks,

    Al 

  • Did you ever receive an answer for this issue? I am having the same issue.
  • I can't post them here or I would, but there are TI drivers out there. We have downloaded EV2300 Win7 64bit and EV2400 Win7 64bit versions.
  • I have same EV2300 drivers installed as you provided in the link and is does not work. Does the application need to be built against a specific .Net framework version or some other special configuration?
  • Thanks for your help.

    VS2005 still throws the error below and VS2013 simply crashes. The AxHost I know is how the .Net wrapper is created to use the COM component on a Windows Form. I find it very odd. Did you have to do anything special to get it to work? I even manually created a wrapper using the AXImp.exe and still no luck.

  • The only thing I know is that you can't use a USB hub. If that isn't your problem try a different computer or a different USB cord.
  • The image didn't go through. The error is:

    Failed to create component 'AxHost'. The error message follows: 'System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
    at
    System.Windows.Forms.Design.DocumentDesigner.AxToolboxItem.CreateComponentsCore(IDesignerHost host)
  • I also want to point out the TI Eval software works perfectly and talks to my eval board. I can also use the ActiveX control successfully using VB6 on the same computer. This problem seems like a licensing problem with the control but I don't see how
  • All,

    Although I do not have a root cause, I found a work around. I created a wrapper ActiveX control with VB6 that contains an instance of the TI bq80xRW.ocx. It has nothing more than a button that activates the AboutBox of the bq80xRW. The wrapper control does not have the Require License feature activated (unchecked) when built. I added the wrapper control to a new VS2013 Windows Forms Application by dragging it from the toolbox to a new form and it loaded without issue. Note: it takes a few moments for the AxHost to create the .Net wrapper for the ActiveX (COM) control. Next I executed the application, clicked the button and the AboutBox appears as expected.

    After adding the wrapper control to the form I then tried adding the TI bq80xRW control the same form. After a few long moments, VS created the AXHost wrapper and the control appeared on the form as it should. I then deleted the wrapper ActiveX control I created from the form. I can now use the TI control normally and do not see any issues. I closed the project, deleted it and created several new ones to see if the problem was gone and had no problems. I verified this method on 2 PCs. One Win7x86 and one Win7x64. Both now work like they should.

    I don't have a clear idea on what the root cause was but I still suspect some incompatibility with the license is implemented on the TI control and/or perhaps some Windows security feature blocking VS from loading the control. Nevertheless, I am surprised no one else seems to have experienced this issue. Especially since it has been a problem for us on several new installations of Win7 with bone stock configurations. It could be related to the Internet Explorer version and its security policies but I have not pined it down yet.

    I think the best solution to this would be to beg TI for a dll and just keep the ActiveX control for VB6 projects.

    -Pete

  • Thank you for the feedback Pete.