LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting between BK PRECISION 8500 with LabVIEW

Hi!

Thanks for last time helping!

I am currently connecting BK PRECISION  8500 model with LabVIEW, but I got to say it is not working. I already went through the datasheet and manual of the 8500 and downloaded the driver of the adapter. When I try to run the example code of the instruments, the code works fine with no errors but there is no response between the LabVIEW and the instrument. (no instruments detected) Anyone knows why is that?

Here I attached the code I was using.

Thanks in advance!

0 Kudos
Message 1 of 8
(4,956 Views)

Looking at the code you posted (without the driver installed) and a brief description of the instrument from the manufacturer's page (here), I'd say that I wouldn't necessarily expect to see anything.

 

What are you doing to diagnose a problem, and what do you want to have happen instead?

 

To check a quick possible problem, I'd point out that the controls are only read when you first start the VI (not during the VI's running), so if you change the controls during the execution nothing will change. You need to run the VI with the new control values (I'd guess that perhaps you added the While loop to prevent it stopping, and wanted to change the controls during that time?).

 

In that case, try using an Event Structure with a Value Change event CC Control and the "Configure Constant Current" in that case - that sounds like it might be what you want.


GCentral
0 Kudos
Message 2 of 8
(4,930 Views)

I am trying to do the full remote control between 8500 and LabVIEW, in this case, I'd like to set the current or resistance in the LabVIEW to control the instrument. However, this VI can only turn the instrument mode on and can't set the value into the instrument. (even not in the correct mode, for example, the instrument is currently in the current mode, but you can't set this to the resistance mode once the current mode is being chosen on the instrument)

In this VI, it would be fine once I can set the value into the instrument, no matter if I want to control during the execution or not.

Thanks for your reply. I add a few things into the VI, you may have a look.

0 Kudos
Message 3 of 8
(4,927 Views)

A couple of things to check.  Make sure you have the same baud rate selected on the 8500 and LabVIEW.  The 8500 is not a fast talker and defaults 4800 baud.

 

Also, make sure you are using a compatible cable.  The 8500 uses TTL serial and a DB-9 connector.  Most of the serial adapters we keep in the lab are RS-232 12-15 volt variety instead of the 5V TTL signals the 8500 uses.  It is a bit too easy to damage the 'serial' port.

 

I was able to get the demo code to work in LV 2014 after making sure I had the cables and baud rate correct.

0 Kudos
Message 4 of 8
(4,903 Views)

Hi MHawk,

 

Thanks for your reply.

I already set the baud rate to 9600 and the IT-E231B cable which is required in 8500 (in manual) is used in the communication. So I am not sure what is going on now...

0 Kudos
Message 5 of 8
(4,896 Views)

Hi guys,

I just tried to use the CR mode to test if the instrument can be set to other modes or not except CC(constant current mode). But even if I used CR mode and icon, the instrument will still be set to CC mode somehow. I checked the datasheet, there is no such description of this problem.

Here I attached the vi.

0 Kudos
Message 6 of 8
(4,869 Views)

I don't have my 8500 handy but when I tried to run one of the driver examples without one connected, it didn't give me any errors. Not promising for troubleshooting.

 

In any case, disconnect the adapter from the 8500 and see if you can use a jumper to make a hardware loop-back by connecting the TX and RX lines together.  Then use a terminal program like PuTTY to see if things are working.  If they are, you will see each letter you type appear on the screen, twice if local echo is enabled (not a default behavior).  After that works, put together a quick Test VI to change the state of the DTR and RTS lines so you can use a DMM to check that they are working with a DMM.

 

If that works, then you probably have a unit that needs service before you'll be able to communicate with it over the serial port.

Message 7 of 8
(4,850 Views)

Thanks for your reply.

 

I will try your solution. I appreciate it.

 

Best wishes

0 Kudos
Message 8 of 8
(4,847 Views)