LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error VISA and Pirometr Marathon MR1S

Good everyone, I want to ask for help in obtaining data from the MR1S pyrometer (Documentation attached).

 

1) If we talk about connection, I use the following approach - the pyrometer has a terminal block with TxD+- RX+ contacts- I connect to them via Female DB9  RS-485 and from it to Male DB9 which connects to the PCIE-1622B board. (I also made adjustments to work with RS-485 on the board)

Connected.png

Then, through the Device Manager, I started configuring COM ports to work correctly with the pyrometer.: 

Baud rate 38400, Data bits 8, Stop bits 1, Parity None

 

2) Before coding in LabVIEW, I decided to check the conclusion via MAX. I get an error during testing: 

Read Operation Error VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

Снимок экрана 2025-03-13 153546.pngСнимок экрана 2025-03-13 144204.png

Снимок экрана 2025-03-13 142548.png

I've already tried different pinouts many times, because as far as I've been able to Google the RS-485 pins, I get my own, so I need to test and figure it out, but no matter how much I try, I get errors. 

 

Can you help me sort out the documentation for my pyrometer? (since I am not very good with English, I may be mistaken somewhere or understand something wrong). When viewing appendix B (approximately page 103 of the PDF), the codes and examples of settings are indicated, but I honestly did not understand anything about how to connect this to VISA, since I had never worked with this before and this is my first experience in connecting and debugging a device not from LabVIEW. 

 

I hope for your understanding and help, and thank you in advance for your reply.

Sincerely, Seraphim Seth 

0 Kudos
Message 1 of 13
(356 Views)

You are missing the termination. Try adding termination resistors at both ends.

 

ZYOng_1-1742001678754.png

 

 

RS485 Termination

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 2 of 13
(302 Views)

Hi,

 

additionally it might help to cross Tx and Rx of master and slave...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 13
(291 Views)

And what kind of "threads" should I pull the pyrometer to, for example, take temperature readings from it in LabVIEW?

I found an example of working with VISA - Continuous Serial Write and Read.vi but so far I don't quite understand how to set up work there.

0 Kudos
Message 4 of 13
(251 Views)

    Good afternoon, everyone, please tell me how to get the temperature values. I get a string, as I understand it, of pyrometer protocols from which I need T(value), then use them in the XY Graph to visually see the current temperature on the pyrometer in LabVIEW.

Снимок экрана 2025-03-19 114210.pngСнимок экрана 2025-03-19 114539.png

    I would also like to ask what aspects should I take into account in my case when setting up sending/receiving commands? How are such commands described in the pyrometer manual generally used? (the message above)

0 Kudos
Message 5 of 13
(236 Views)

Hi Seth,

 


@SeraphimSeth wrote:

I get a string, as I understand it, of pyrometer protocols from which I need T(value), then use them in the XY Graph to visually see the current temperature on the pyrometer in LabVIEW.


Search for "T" in your string and ScanFromString the numeric chars after the T. Then do with that 2401 value what you want to do.

This is basic string handling/parsing: there is a whole string functions palette!

 


@SeraphimSeth wrote:

I would also like to ask what aspects should I take into account in my case when setting up sending/receiving commands? How are such commands described in the pyrometer manual generally used?


All the commands and the possible responses should be explained in the manual of your device.

You "just" need to follow that manual…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 13
(232 Views)

Your command *IDN?\r is a typical SCPI command for T&M measurement devices, but outside of manufacturers like Agilent, Tektronix, Keithley, Rhode & Schwarz and similar T&M companies fairly seldom used. Your manual documents the actual programming protocol in Appendix B and that has absolutely NOTHING to do with SCPI.

 

The list of commands is from page 96 but in a very typical way for such manuals that makes only really sense if you are able to experiment with a real instrument to try out what exactly happens to the various commands.

 

 

Rolf Kalbermatter
My Blog
0 Kudos
Message 7 of 13
(228 Views)

Hi, GerdW

Using ScanFromString, I get this error when reading from VISA Read

Снимок экрана 2025-03-19 140345.png

 

I tried to follow the instructions and give the command to the pyrometer, but to no avail. I've tried different commands with different line endings(\r \n \r\n)

What it shows me now is how I understood the protocol $=UT.. <CR>, but even changing it, I don't get anything new, just the old command.

Снимок экрана 2025-03-19 163629.png

0 Kudos
Message 8 of 13
(219 Views)

Hi Seth,

 


@SeraphimSeth wrote:

Using ScanFromString, I get this error when reading from VISA Read


You failed in showing how you use ScanFromString!

Additionally you now receive messages containing "TEUUU", which clearly does not contain numeric values - which you wanted to analyze from your messages…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 13
(215 Views)

Sorry for the inaccuracy in the previous answer.

This is how I used Scan From String:

Снимок экрана 2025-03-20 091022.png

 

I decided to try other implementation options.

 

 

But I encounter a number of problems

1)Probably due to the fact that there are drawdowns during data transfer, which is quite noticeably displayed on the graphical part. I would like to fix this somehow, but I don't know how to do it correctly. 2)Again, due to data loss, ScanFromString will give an error at some point in time, which is a problem when VI is running.

 

Can you suggest ways to solve this problem?

 

I also seem to take quite a lot of data packets, which is why the pyrometer readings in LabVIEW do not correspond to its actual physical parameters on the device (Data is updated with a delay)Снимок экрана 2025-03-20 100026.png

 

SeraphimSeth_0-1742467895558.png

 


Снимок экрана 2025-03-20 100106.png

0 Kudos
Message 10 of 13
(148 Views)