LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SME1203 controller not responding to NI-VISA read command

Solved!
Go to solution

Hi everyone, we are having an testing machine in which the surge test values are returning as zero. Instrument is connected to PC through com port , mode of communication is RS232. Checked the hardware wiring part and also changed the com port same issue is coming.I have configured my instrument in com port -1.When i checked the instrument through NI-MAX(using Input/Output fn) using Query function- Timeout operation error coming . What could be the possible reason? I went through the forum, tried several things , found no results.Since i m new to labview , i am not able to proceed  in the correct path. So kindly guide me. Also if any more details required, kindly reply me,,

0 Kudos
Message 1 of 5
(617 Views)

Hi Melchizedek,

 


@Melchizedek24 wrote:

 What could be the possible reason? I went through the forum, tried several things , found no results.Since i m new to labview , i am not able to proceed  in the correct path. So kindly guide me. Also if any more details required, kindly reply me,,


What does the manual of your device tells you about communication with the device?

Does it need specific COM port settings?

What about the used communication protocol?

Do you have another 3rd party tool to verify the communication (like HTerm or similar)?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 5
(615 Views)

Device manual is saying RS232-C communication protocol is possible. Also when we trigger command thru labview, instrument is getting triggered.

 

No specific com port settings are needed.

Used protocol is also RS232-C

Hterminal means Hyper terminal. No i need to verify it with hyperterminal

0 Kudos
Message 3 of 5
(531 Views)
Solution
Accepted by Melchizedek24

That device needs a baud rate of 38400.  Did you set that in LabVIEW?  Did you set it in NI-MAX?

 

Can you post some code (screenshot OK, VI file backsaved to 2019 or so better)?

0 Kudos
Message 4 of 5
(522 Views)

Sorry for the late reply. Identified the root cause. We are using RS232 to USB Moxa converter for serial connection. That particular hardware has caused the trouble due to its failure. After replacement, the values are getting read .Thanks for the feedback and responses.

0 Kudos
Message 5 of 5
(490 Views)