Serial Communication by VISA: what' s wrong ?

[Albert.Geven]

sorry I saw that it is already hex, i keep studying

[gmpony]

Thanks for all time you are spending. Some other info, maybe helpful. The multimeter works also with a software called Mas-View. I monitored the communication with this software too. please fn in the file the output of portmon. The software doesn't use Visa driver I suppose. So that is seems to me that the communicatio is cleaner.

Both Matlab and Mas-View seem to get the answer back from the instrument in a different way. Labview cannot.

Regards

Gianmarco

[Albert.Geven]

Hi

Make the endcharacter hex 0D or in LabVIEW \ code representation \r  (be sure to rightclcik on the string and select "\" codes view
(decimal 13)

this is the real endcharacter
I changed this in your start vi, and modified the config vi but I guess that is not really needed.
Just try.

[gmpony]

Done, but I still get error -1073807339.

I'm not sure I did the right thing. I loaded first the Modified driver in Labview and I tried it. Then I loaded start.vi and I runned it.I suppose labview uses the modified driver already in the memory not the original one I have in the root. I'm not so sure. Anyway, I enclosed Portmon registration.

I also tried to write : D\r but, same result.

Gianmarco

[Albert.Geven]

LabVIEW uses the vi in memory. Even refuses to load it again.
Most of the time that is a feature but only when you rename new vi's.
In this case it is what you want.

I guess that one of the control lines is asserted by the other programs, I try to find out.
I get the same error as you but because I don't get a Velleman kit, it is correct.

maybe someone from the visa development can chime in. Does somebody know why VISA accesses the system so often to set all parameters one by one??

[gmpony]

Hi guys,

after several trials and good suggestions from NI support team (Italy) I finally solved my problem. Please find enclosed .vis for a working communication to:Digital Multimeter DVM345DI ex Velleman (alias MAS34-xx  ex Mastech).

For the beginners like me, I suggest to measure the voltage of each pins in the serial port during a working communication when they want to know what is going on. So I did with the multimeter itself. I understood that the working programs (Mas-view and Matlab) setted the RTS to null instead Labview put it to high. I suppose this is not a very common serial transmission procedure but that is.Thanks to people that helped me.

Gianmarco 

[Albert.Geven]

congratulations

maybe it is an idea to put these vi's on the community pages, that are still experimental and worst of all you need a new userid to get access to those pages.

http://community.ni.com/

or maybe someone from the instrument driver group adds these to drivers available.

[ohgi]

Dear gmpony

Hello. I have same trouble with MAS344 digital multimeter. I found your message today. However, I don't have LabVIEW 8.20. I just have LabVIEW7.1. Could you repost your Vis as older version?

best regards

[gmpony]

Hi, I will be glad to do it but I  don't know how to do it. In the  menu there is a menu "save in a previous version" but the only choise I have are 8.2 ,8.0. Help claims for a tool-kit that should be installed but I cannot find it. Any suggestion from anyone?
Gianmarco

[Albert.Geven]

Every version only saves for the previous
so if someone with 8.0 can save for previous you get 7.1