ke485

[Husain111]

I am tring to use the example in ke485 driver to control keithley 6487 picommeter using LabViwe 2013. the installation was O.K. and MAX detect the instrument but when I run the example no errors show but it does not take control of the keithley. The concern I have is that the driver  inveroment  was 2012 but I use 2013. Is this an issue. any solution or suggestions

[Dennis_Knutson]

You've started multiple threads and they have conflicting information. Now you say that MAX does detect the instrument. I can't look at the code now but I would expect problems using a driver for s different instrument. The code you are using is very old. Are the error out terminals even wired?

[crossrulz]

What address is the instrument set up to use?  I also question using a driver for a different model.  You need to make sure the commands are the same.

[Husain111]

I am tring to work from two pC and have different issue that is why I opened multipule threads. Are you aware of better driver I can use. What sort of errors I expect when I use the wrong drivier.

Thanks allot for your patince and support

[Husain111]

I am tring to work from two pC and have different issue that is why I opened multipule threads. Are you aware of better driver I can use. What sort of errors I expect when I use the wrong drivier.

Thanks allot for your patince and support

[Husain111]

I set up the instrument to  GPIB to 22 and write 22 in the adress only. I am using GPIB USB HS controlor.  The figure show how I wrote the GPIB aderess in the string and how MAX give the adress.

[crossrulz]

There is no error handling in that driver, so looking for errors could be difficult.  You might want to go into the driver and add some error handling to see if any errors are being generated.

And again, make sure the commands being sent are what the instrument expects.  You need to do this simply because the driver is for a different instrument.

[Dennis_Knutson]

And you haven't wired the address to the first function.

[JÞB]

---

@crossrulz wrote:

There is no error handling in that driver, so looking for errors could be difficult.  You might want to go into the driver and add some error handling to see if any errors are being generated.

And again, make sure the commands being sent are what the instrument expects.  You need to do this simply because the driver is for a different instrument.

---

As a matter of fact the commands are not interchageable The 485 was never 488.2 compliant (SCPI) the newer models are.

[crossrulz]

---

@JÞB wrote:

---

crossrulz wrote:

And again, make sure the commands being sent are what the instrument expects.  You need to do this simply because the driver is for a different instrument.

---

As a matter of fact the commands are not interchageable The 485 was never 488.2 compliant (SCPI) the newer models are.

---

There you go.  The drivers chosen will not work.  Either go find the right ones or start writing your own (assuming you can find the command set).