ERROR - 1073807178

[guangdew1]

I'm having a very similar problem with same error code. I'm very interested to see some more posts on this issue. I will also post it here if there's any progress.

[denslen]

Thanks again to all who have participated. Here is the latest update regarding this issue. I uninstalled the Kikusui software and made sure that the NI VISA software was installed correctly. After attempting to reinstall the Kikusui software and force it to find the NI VISA, I now have a nonworking system. I attempted to backtrack and uninstalled the Kikusui software, then reinstalled it according to their instructions and now I am unable to attach the needed USB or VISA driver to the device. The current thinking from Kikusui is that the two VISA drivers are in conflict (Kikusui and NI). I have been given a new set fo instructions from Kikusui and will try that now. I'll be back later with another update.

[denslen]

I have followed Kikusui's instructions for resurrecting my PFX system and it still isn't working. I've attached some instructions from Kikusui to show you what their suggestions are. I finally deleted every Kikusui registry entry I could find and followed the instructions again and was able to get all of their software to install without any error messages but it still won't connect to their machine.

[guangdew1]

I think I found what is wrong here. As I mentioned earlier, I have the same kind of problem and working on it. The error message mentioned "incompatable bcdUSB value (expected 0x110 or greater)". I talked with our firmware guy here with the specific problem. He later increased the hareware/firmware version to usb.1.1.0 even though the actual hardware is lower. Then I went through the installation process and I can talk with the device now. I know this is only a trick and we may have problem ahead, at least we know where the problem is.

[Makoto]

Hello all,

One important thing is KIKUSUI PFX2000 USB box is ***NOT*** USBTMC compliant. The device is far from the USBTMC spec.

The BPChecker2000 system only communicates with the device through its "device-specific" driver, and you can't replace the working driver with VISA USBTMC.

As USB RAW driver from NI-VISA, it may be possible to host the device as a generic "vendor-specific" USB device if you want to control the device from your own custom app. However, the device does not understand any SCPI command strings (including *IDN?), instead, all the control commands are BINARY block and not public for users.

Makoto Kondo, KIKUSUI ELECTRONICS CORP.

[denslen]

Hello Makoto,

Yes, I discovered I was wrong about that. In my installation it shows up in the USBTMC class in device manager but states that it is Non USBTMC. It seems to be a bit confusing.

I have decided I do not need to control the BPchecker 2000. I just need to observe the traffic on that port and watch for the impedance test (with the channel #) to occur. This will be used to trigger test instruments. I'm assuming I can look for the the binary command for that test (as shown in the PFX SPY window) and that will be good enough for us.

Thanks,

Dan

[denslen]

Adam, I tried the tulip passport suggestion and it didn't work. I've recovered my system back to where I was about the time you replied with this suggestion before. Do you or anyone else have any other suggestions regarding monitoring the Kikusui unit on the USB port that it is connected to? The machine is using a WinUSB driver but I think I would cause myself more headache if I try to force it to use any other driver. I've tried to Open a VISA session by entering text into the VISA I/O control but I am still lacking a needed piece of information. I think I need an interface ID and or a Serial number code but I don't know. I get the error message of not enough info. to open the session.

One other thing I tried was tracking down the .inf file of the unit, copied it to the C:\WINDOWS\INF folder and created a .pnf file but that didn't help either. As I said earlier I'm leery of installing a different driver for the Kikusui unit.

This has been by far the most difficult thing in LabVIEW i've ever tried and has been a real eye opener exercise in trying to set up an instrument.

[Tanya_V]

Hi Dan,

Since this is a USB RAW device, you will need to get through the VISA Driver Development Wizard to work with the device as a VISA Resource in LabVIEW. Did you try guangdew1's suggestion of changing the bcdUSB value? Also, have you looked at the resources on ni.com that discuss using USB RAW devices? The following article is a good place to start and includes a lot of good links:

How Can I Communicate With a Device Using NI-VISA USB RAW Mode?

Let me know if you are still getting errors while going through the driver wizard.

Take care!

[denslen]

Hi Tanya. I have no idea how to go about changing the bcdUSB value. Is this strictly a USB protocol value? Would that parameter change if I upgrade the WinUSB driver that is currently being used? Also, once I create a USB RAW driver in the wizard, do you know if it is possible to use that driver just for LabVIEW without actually changing the driver that is already assigned to the Kikusui unit? I would really like to avoid altering that if possible.

[Makoto]

Dan,

The bcdUSB values (0x0100) of Device Descriptor is an embedded code in the device firmware, so you can't change it from device drivers.  NI-VISA USB RAW looks like hate any devices that claim bcdUSB value lower than 0x0110. Therefore it may be impossible to host the device with NI-VISA USB RAW.

Assuming NI-VISA could host the device, there is another problem.  BPChecker2000 only communicates with the device through the WinUsb API (via WINUSB.DLL) because the device is hosted by the Microsoft WINUSB.SYS under normal setup.  If it was being hosted by other device driver (such as NI-VISA USB RAW), BPChecker2000 would not be able to access the device.

Seems like you want to detect some operation's events generated by BPChecker2000, such as Charge End, Discharge End, Rest End, etc to control your own custom hardware in proper timing especially around Impedance Measurement events. If so, it may be better to observe the application's events as if BPChecker Event Spy app does.

The Event Spy app is what always observes BPChecker events, then displays logs, sends emails as needed.  The core engine of the "Spy" is built in the "out-of-process" COM server B2kEventLogger.exe.  An application that accesses this COM server (as like as Event Spy app) can detect BPChecker event. This kind of app may be written by VC++, VB6, or probably by LabVIEW or C# as long as they can control the EXE-based COM server.

Makoto