LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Setting up an instrument

Solved!
Go to solution

You incorrectly appended the characters '\' and 'n' because you did not right click and select '\' Codes Display. This is a very common mistake for beginners. If you look at the serial interface section, the termination character is already set to a line feed (\n). No need to modify the actual write string and certainly no need to modify the expected string as you did.

0 Kudos
Message 11 of 27
(1,175 Views)

Hi Dennis,

 

In the serial write and read vi the command is *IDN?\n  the Codes Display is already selected and i get the reponse. However I dont get a response with *IDN? even if i change the setting to normal display.

 

When you say expected string do you mean the regular expression input for the match pattern? should I have TET,\sARGOS\s500\s1200V/0.5A,\s1042500338,\s1.4\n as my instrument ID response.

 

Is it a problem with the fact I created a new instrument driver with a template for a power supply?

 

Should I start from scratch and build the vi s myself?

 

If i go to instrument finder, it scans for my device it finds TET>ARGOS500 1200V/0.5A when i double click on the device it returns the name in the additional keywords field but because NI does not recognize the manufacturer i cant advance.

 

Am i on the correct lines by using the template which results in the error code or what would you suggest?

 

Regards

 

Damien

 

 

 

0 Kudos
Message 12 of 27
(1,169 Views)

You see: Post the code and you get the best help 🙂

Here a picture of what the knight said:

 

 

changes.png

 

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 13 of 27
(1,168 Views)

@Damien129 wrote:

Hi Dennis,

 

In the serial write and read vi the command is *IDN?\n  the Codes Display is already selected and i get the reponse. However I dont get a response with *IDN? even if i change the setting to normal display.

 

When you say expected string do you mean the regular expression input for the match pattern? should I have TET,\sARGOS\s500\s1200V/0.5A,\s1042500338,\s1.4\n as my instrument ID response.

 

Is it a problem with the fact I created a new instrument driver with a template for a power supply?

 

Should I start from scratch and build the vi s myself?

 

If i go to instrument finder, it scans for my device it finds TET>ARGOS500 1200V/0.5A when i double click on the device it returns the name in the additional keywords field but because NI does not recognize the manufacturer i cant advance.

 

Am i on the correct lines by using the template which results in the error code or what would you suggest?

 

Regards

 

Damien

 

 

 


You don't have it set correctly in the initialize function and both your write and expected read are incorrect because you blindly made some changes without understanding what happens. You simply cannot paste a \s  or \r or \n into a string with normal display and hope it will work the same as when it is set for '\' Codes Display.

0 Kudos
Message 14 of 27
(1,162 Views)

Hi Guys,

 

I have followed the steps accordingly in the initialize.vi as in i selected diplat style nd have changed to the codes display. I still get an error code -1074003951 when i highlight execcution at error custer from error code vi and results in a timeout error. Again i have the serial configuration correct along with the query command. Am i overlooking something else?

 

Damien

0 Kudos
Message 15 of 27
(1,149 Views)

In fact the error is just -1074003951 so it does not identify the instrument.

 

Damien

0 Kudos
Message 16 of 27
(1,147 Views)

I am applying these changes in the vi example under my ARGOS project

0 Kudos
Message 17 of 27
(1,137 Views)

The best way to make sure that we are able to help you with any code that you have problems with, is to share this code with us.

Whenever you change your code and still have trouble, then post the new code, so that we can see what you have changed,  and that we are also looking at the latest code.

 

Or take a picture of what you have changed, so that we can guide you.

0 Kudos
Message 18 of 27
(1,133 Views)

Hi,

 

Thanks for the reply this is a link to the project.

 

Regards

 

Damien

0 Kudos
Message 19 of 27
(1,131 Views)

That is only the project file. All the vi's are NOT in the project file, but stored seperate on you hard disk.

You need to zip them together and share them.

0 Kudos
Message 20 of 27
(1,128 Views)