Cirris

[rajeevan@1978]

Hi FZbel,

Hope you don't mind if I asked to share your code so that I can compare with mine here.

Regards, 

[FZbel]

Hello Raj,

I haven't started coding yet , since i am still trying to figure out how to execute what i have in mind. As i said before the CIRRIS team recommended to use CTLwin and CTL commands but weren't clear on how to do so . Therefore , i have been asking you about your experience with it before i can moce forward. 
I hope you don't mind answering my questions , because i am really interested in how you have done it.

Thank you 

[FZbel]

Hello Diginous,
May i ask you if you don't mind of course , how did you use CTLwin ? do you executes commands there first than control CIRRIS with labview ?

and also did you use report generation toolkit to store your results in Labview or do you just get the count of good cables and bad cables ? 

Thank you ,

[Diginous]

I don't use CTLwin for anything other than editing wirelists.  I might ask if your trying to send your wirelists in the .wir file format?  cut and paste (through CTL Win) it into a text document...  use the serial action engine to send from the code I posted.  We send the wirelist and store them as a text document, not a .wir extension (as labview can't read a .wir file).  That maybe the problem with sending wirelists.  looking back at the coding, VISA does all the necessary things to send long text to the machine.  You have to make sure it's properly formatted (commands to clear the memory and write to it), and send the commands as normal.  You can use CTL win to send commands to Cirris and see the response, then tailor your code to do the same.  I use an 1100R+.  I can't say the easy wire responds the same, but can be tested using CTL win's terminal to verify (although I would expect it to work).  Hope that may shed light on this..

[FZbel]

hello Diginous , 
Thank you for your answer , it was helpful .

Yes i was trying to send the wirelist throught CTLwin .
I have asked the CIRRIS technical team about the possibility to control the device and they said the only way to do  it outside the standalone test systems is  by sending  CTL commands and running them via CLTwin (after configuring terminal port)