DMM MAS345 via RS232 serial comunication

i have a problem almost like u,and i want to know if there is someone who can help me.I want to send data from a DMM MAS-345 via Rs232(my data settings in labview are baud rate=600,data bits=7,parity=none,stop bits=2,flow control=none,delay before read=10000ms) ,and i don't know why does it showes an error when i try to run the application(error -1073807202).I use like example VISA configure serial port,and i don't know if is wrong!!!I will appreciate if someone can help me.
Attachments:
Basic Serial Write and Read.vi ‏34 KB

Here is some help for you
MAS345
data format: 7n2 at 600 baud (7 bits, no parity, 2 stop bits).
Control lines:
   DTR and RTS lines are used to power the TX line: RTS is clear
   for -12 supply; DTR is set for +12 supply. Data transmission is
   solicited sending whatever character to the RX line.
Data string format:
   MAS-345 sends a 14 bytes string with:
         <mode>< ><sign><value>< ><units><return>
   <mode>: two bytes with the oerating mode: DC, AC, OH, CA, TE ...
   <sign>: one byte with - or space
   <value>: five bytes with four digits and one decimal dot.
   <units>: four bytes with the units: mV, A, kOhm, nF ...
   <return>: '\r'
   One space is inserted between <mode> and <sign>, one between
   <value> and <units>.
   The data string (without the '\r') is sent to the output device.
The next question is of course How Can I Control the DTR and RTS Serial Lines in LabVIEW? It is easy take a look here
http://digital.ni.com/public.nsf/allkb/1ECEFAA7AD52994986256966005356EA
Good luck
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Similar Messages

Fluke PM6304 controlled with LabView via RS232

Hi,
we're going to control our Fluke RCL Meter with Lab View via RS232.
Does anyone has experience and show sample code?
I failed already to make a terminal connection between my PC and the PM6304
Thanks for comments, maximint.

Okay, here goes. Once upon a time there was just serial and gpib. Each used completely different hardware,protocols, etc. and there were separate drivers for each. Years ago, a new instrument type was introduced. Based on a VME backplane, these were instruments on a card called VXI (VME with instrument extensions). So, a whole new low level driver was required. The makers of VXI, realizing that the first VXI instruments were the same as their GPIB instruments without a display or power supply, thought that it would be nice if the software that had been developed for the GPIB instruments could also be used for the VXI version. Several vendors, including NI, came up with something called VISA (Virtual Instrument Software Architecture). This was an API that united GPIB and VXI. If you wrote an instrument driver with VISA Writes and VISA Reads, it would work with either type of instrument. The VISA driver itself would determine the actual type of bus and handle all of the low level details. One of the goals of all these vendors was to also make it easy for users to change from GPIB to VXI instruments. While this didn't really happen, the idea of VISA caught on and became very popular and sort of a standard in many places. Eventually, other common forms of instrument busses were added to VISA. Among those are serial, ethernet, usb, pxi. All of the instrument drivers written by NI now use VISA.
I downloaded the driver for the instrument you need and had a look at it. It really doesn't have much, it's very old, and uses the GPIB functions (not VISA). Since there were so few functions, I went ahead and replaced the GPIB Reads and Writes with VISA Reads and Writes. That will give you a start. You will also need to add some code to initialize the serial port. A great place to look to see how this is done is with an example that has shipped with LabVEIW for years. The HP34401 DMM driver that is on the instrument driver palette is a VISA driver with special support for serial. All of the serial setup is done in the initialize subVI. The type of interface is determined and if serial, baud rate, parity, etc. are setup. Another important setting is a termination character. Serial instruments usually require a CR or LF at the end of each command. You will need to determine what your instrument requires.
Attachments:
flpm6304.llb ‏141 KB

How to communicate via RS232?

I am trying to program an sbRIO-9606 to communicate with a Matrix Orbital LCD display via RS232. I have NI-VISA 5.4.1 and NI-VISA Server 5.4.1 software installed on the sbRIO. But I am not seeing any COM ports to use to communicate. Is there other software I need? Or is there a resource where I can find some instructions about this?
Solved!
Go to Solution.

Found it!
I also needed the NI-Serial RT 4.0.0 installed on the sbRIO.

Need to control waterbath temp using labview via RS232

HI,
I am new to labview. I have labview 6.1. I need to control a thermo RTE7 water bath temp. controler using labview.
The water bath has to be connected to computer via RS232 port and the commands have to be given via binary values.
The users manual for the bath has "hex" bytes that are to be converted
to binary values to be passed to bath. If anyone has done this before
or anyone can help me on this please let me know. Thanks,

Use simply the recommandations given in the RTE manual. You don't have to convert to binary : that's something done by the hardware.
For instance, to send the temperature setpoint to the controler, you have to send a byte string such as
CA 00 01 F0 02 01 2C DD, where CA 00 01 is a header specific to the type of serial link you are using,
F0 is the set temperature command,
02 is the number of bytes expressing the temperature that you are about to send
01 0C is the temperature in tenths of degree (here : 30°C = 300 tenth = 010C$
DD is a check sum byte.
The corresponding labVIEW program is as follow :
Of course, do not forget to initialize the serial port before writing the string !
Message Edité par chilly charly le 10-21-2005 06:21 AM
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Water bath.png ‏4 KB
Water bath.vi ‏28 KB

Comment envoyé une donnée via rs232 avec labview

Salut, comment envoyé une donnée via rs232 avec labview ?
Hello, how given sent via rs232 with labview?
Solved!
Go to Solution.

You can use the LabVIEW example for "Basic Serial Write and Read." In the English LabVIEW it is found here:
Vous pouvez utiliser l'exemple LabVIEW pour "SerialBasic écrire et lire." Dans le LabVIEW anglais, il se trouve ici:
Zach P.
Product Support Engineer | LabVIEW R&D | National Instruments

Forcing Relays via rs232

Hello everyone,
I’m new to Labview and i would appreciate it if someone could show me how to make, or use an existing Labview VI to operate via RS232 (ASCII or Modbus) an external Power Relay Output (Advantech ADAM 4069), in order to switch on and off a vacuum pump.
The problem is that no Labview VI or driver exists yet from Advantech. However, according to the manual I have to send simple hex command like 0x01 for Set and 0x00 for Reset, through a serial port.
Product Page of Power Relay Output:
http://www.advantech.com/products/8-ch-Power-Relay-Output-Module-with-Modbus/mod_1-2MLDJ5.aspx
The event which will set or reset the relay is a dc voltage reading acquired by an internal PCI Multifunction Card, for which several VI’s exists.
Thanks in advance for any help!
Regards,
John

Hi Sebastian,
Have you tired contacting the manufacturer to see if they have drivers for LabVIEW and the particular model you are using? We do not have drivers available on our Instrument Driver Network but we do offer resources that can help you develop the drivers. Please refer to the following links for more information.
Developing LabVIEW Plug and Play Instrument Drivers
Development Tools and Resources
You can also submit a request for a particular driver.
Thank you,
Simran K
National Instruments
Applications Engineer

Communication via RS232 with a Kollmorgen Servostar 300 using LabView.

Hello,

Sorry I am new posting a message here and I post it before I was able to describe my problem.
I have a Kollmorgen Servostar 300 to control an AKM24F motor and I would like to send the instructions to the controller via RS232 using LabView. I think I had achieved communication from a PC to a Servostar 300 using LabView via the serial port.
So far I have setup in LabView the configuration of the RS232 (8 bit, no parity, baud rate 38 400), the address of the servostar (ADDR 0), the way the servostar should respond to the host (PROMPT 1) and the error flag (MSG 1), and no error had been detected when I run the program. I should mentioned that after I sent an instruction such as ADDR 0 terminated with a carriage return, I set a delay time of 150 ms, then I read the amount of bytes that are in the buffer, and then I read the buffer, as I mentioned no error message has appear and the ADDR 0 instruction is read from the buffer. Following the same procedure I sent an instruction to move the motor but nothing happens.
So far I am not sure if the way I am trying to communicate with the servostar is the correct or if I am missing something, any guidance that anyone my give would be greatly appreciated.

Communicating via RS232

Hello,In my project I have to log data from ABB SENSORS,communication is via RS232.As iam beginner,Please let me know how can I do this, any examples are welcome.
Thank You

Navigate to C:\Program Files\National Instruments\LabVIEW 7.1\examples\instr or wherever you have Labview installed. Look for smplserl.llb. In this library are several examples on how to use the serial port. This should help you get started.
- tbob
Inventor of the WORM Global

HP34970A configuration via RS232

How do you get LabVIEW to talk to and configure and HP 34970A datalogger via RS232 connection?
We are new to LabVIEW and need basic help with getting it to work with our equipment.

First of all, do you have the LabVIEW driver? If not, go to http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/e4c553c139f78062862568ab005fba3c?OpenDocument and get the driver that matches your version of LabVIEW. Next, make sure you have the right serial cable. Next, configure either the instrument or HP34970A Initialize.vi so that the communication parameters are the same (i.e. parity, baud rate, etc.). Next, pick a VI under the Getting Started pallette of the instrument driver. Pick one that similar to what you need to do and what kind of hardware is inside the box. Next, change the instrument descriptor to be ASRL1::INSTR (if connected to comm 1). Next, run the VI and see what happens. I use a lot of these things but they're all GPIB because
I'm not masochistic enough to enjoy serial communications. I do seem to recall seeing a post that the instrument driver has the wrong termination character for serial. If you can't get the LabVIEW driver to work, try talking to the instrument using hperterminal. Good Luck.

Sending binary file via RS232 connection

Hi,
I want to send a binary file via RS232 connection but I have troubles reading the .bin file and then converting the data to string in order to send it via RS232. Any ideas how i can deal with this?
Thanks in advance,
IG.

It is hard to help then you do not post any code. I suggest you go to the toolbar then help. Then you select Find Examples. Search for files. Also since you are new to Labview always have context help enabled. Both tools are important if you want to learn Labview. Feel free to post again if you are stuck.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Agilent 34401A multimeter to PC with Labview driver via RS232

Hello!
I am trying to measure a voltage with Agilent 34401A multimeter connected to PC via RS232 cable. I installed the driver. When I am starting Read Single Measurement.vi. It gives me an error:
Error-1073807346 occured at Visa Open in Agilent 34401.lvlib: Initialize.vi->Agilent 34401 Read Single Measurement.vi
Possible reason(s):
Visa: (Hex 0xbFFF000E) The given session or object reference is invalid.
I would like to ask, how can I adjust my system to use RS23 with Agilent 34401A, if it is possible? If not, should I get GPIB card and cable?
Thank you!
Yulia.

LabVIEW already comes with a driver for the 34401 pre-installed, so I'm not sure I understand what you installed. The pre-installed driver is in the Instrument I/O >> Instrument Drivers >> Agilent 34401 functions palette.
As for the control that Dennis is referring to, it's the VISA control.
As for the VISA version, you should have received a set of driver CDs along with LabVIEW. That will have the minimum VISA version required. Don't remember off the top of my head which version it is. Probably something like 4.1.
Attachments:
visa.png ‏42 KB

I bought photoshop elements. Im trying to activate it via the serial number, says it is invalid. I know its valid, as I've already used this version on my PC. Im on MAC at the moment.

I bought photoshop elements 11 on disc. Im trying to download it to my MAC via the serial number, says it is invalid. I know its valid, as I've already used this version on my PC. Im on MAC at the moment.

I bought from Amazon. The PC disc works fine on my PC, but when I try to load the MAC version on my iMac, it says the serial number is invalid. It's Elements Version 11 by the way.
Sent from my iPad

I'm having trouble communicating with a transducer (Keyence LS-3100 laser scan micrometer) via the serial port. It works in Hyperterminal. Any suggestions?

Its not a simple baud-rate or parity error. If I issue the command to send data (X1) in hyperterminal I start to get data. If I then switch to Labview I still get data. However if I try to issue the send-data command via Labview I get nothing (i.e. I can read from the device, but not write to it).
I am on a Windows 98 (version 2) PC, running Labview 5.1.1

Try adding a carraige return to the end of your command.
"djb" wrote in message news:[email protected]..
> I'm having trouble communicating with a transducer (Keyence LS-3100
> laser scan micrometer) via the serial port. It works in
> Hyperterminal. Any suggestions?
>
> Its not a simple baud-rate or parity error. If I issue the command to
> send data (X1) in hyperterminal I start to get data. If I then switch
> to Labview I still get data. However if I try to issue the send-data
> command via Labview I get nothing (i.e. I can read from the device,
> but not write to it).
> I am on a Windows 98 (version 2) PC, running Labview 5.1.1

The sampling rate of Multimeter Protek 508 via RS232

Hi everyone. I have the multimeter Protek 508. I want to take the data from it via RS232. The default detail of RS232 is:
Baud rate: 1200
Data bit: 7
Stop bit: 2
Flow control: None
I write the code and get the data from it. But i only have the sampling rate is 2 data per second, that mean 500 ms per data. I want the sampling rate more than that. Can anyone help me to solve this problem.
Thank you.
Attachments:
186148720-Multimeter-Protek-506-pdf.pdf ‏553 KB
Protek 508 RS232.vi ‏35 KB

You are probably getting everything out of this device that you can. First, it is old, make that, very old. Back in the day, it might have been quick, but that was then. This is now.
Second it's a multimeter. Very often meters like that would do running averages to make the reading appear more stable. That averaging slows down the rate at which you get new data.
How fast are you needing to acquire data?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Applet- RS232 serial communication

Hi,
Can any one tell how to do applet -RS232 serial communication?Do i signed applets? any secuirty policies to incorporated?
Thanx
/JP

you need to install the jre, and place the win32.dll at JavaSoft\JRE\1.3.1_06\bin, that properties file place at JavaSoft\JRE\1.3.1_06\lib, comm.jar at JavaSoft\JRE\1.3.1_06\lib\ext\
and in ur code try to use it to open ur com port
public String test() {
String drivername = "com.sun.comm.Win32Driver";
try
CommDriver driver = (CommDriver) Class.forName(drivername).newInstance(); driver.initialize();
catch (Throwable th)
{* Discard it */}
drivername = "javax.comm.*";
try
CommDriver driver = (CommDriver) Class.forName(drivername).newInstance(); driver.initialize();
catch (Throwable th)
{* Discard it */}
portList = CommPortIdentifier.getPortIdentifiers();
while (portList.hasMoreElements()) {
portId = (CommPortIdentifier) portList.nextElement();
if (portId.getPortType() == CommPortIdentifier.PORT_SERIAL) {
if (portId.getName().equals("COM2")) {
//if (portId.getName().equals("/dev/term/a")) {
try {
serialPort = (SerialPort)
portId.open("SimpleWriteApp", 2000);
} catch (PortInUseException e) {}
try {
outputStream = serialPort.getOutputStream();
} catch (IOException e) {}
try {
serialPort.setSerialPortParams(9600,
SerialPort.DATABITS_8,
SerialPort.STOPBITS_1,
SerialPort.PARITY_NONE);
} catch (UnsupportedCommOperationException e) {}
int i=0;
while(true)
try {
messageString="hi";
System.out.println(i++);
outputStream.write(messageString.getBytes());
} catch (IOException e)
System.out.println(e);
messageString=String.valueOf(e);
return messageString;
and yet u need to signed the applet
1. Compile the applet
2. Create a JAR file
3. Generate Keys
4. Sign the JAR file
5. Export the Public Key Certificate
6. Import the Certificate as a Trusted Certificate
7. Create the policy file
8. Run the applet
Susan
Susan bundles the applet executable in a JAR file, signs the JAR file, and exports the public key certificate.
1. Compile the Applet
In her working directory, Susan uses the javac command to compile the SignedAppletDemo.java class. The output from the javac command is the SignedAppletDemo.class.
javac SignedAppletDemo.java
2. Make a JAR File
Susan then makes the compiled SignedAppletDemo.class file into a JAR file. The -cvf option to the jar command creates a new archive (c), using verbose mode (v), and specifies the archive file name (f). The archive file name is SignedApplet.jar.
jar cvf SignedApplet.jar SignedAppletDemo.class
3. Generate Keys
Susan creates a keystore database named susanstore that has an entry for a newly generated public and private key pair with the public key in a certificate. A JAR file is signed with the private key of the creator of the JAR file and the signature is verified by the recipient of the JAR file with the public key in the pair. The certificate is a statement from the owner of the private key that the public key in the pair has a particular value so the person using the public key can be assured the public key is authentic. Public and private keys must already exist in the keystore database before jarsigner can be used to sign or verify the signature on a JAR file.
In her working directory, Susan creates a keystore database and generates the keys:
keytool -genkey -alias signFiles -keystore susanstore -keypass kpi135 -dname "cn=jones" -storepass ab987c
This keytool -genkey command invocation generates a key pair that is identified by the alias signFiles. Subsequent keytool command invocations use this alias and the key password (-keypass kpi135) to access the private key in the generated pair.
The generated key pair is stored in a keystore database called susanstore (-keystore susanstore) in the current directory, and accessed with the susanstore password (-storepass ab987c).
The -dname "cn=jones" option specifies an X.500 Distinguished Name with a commonName (cn) value. X.500 Distinguished Names identify entities for X.509 certificates.
You can view all keytool options and parameters by typing:
keytool -help
4. Sign the JAR File
JAR Signer is a command line tool for signing and verifying the signature on JAR files. In her working directory, Susan uses jarsigner to make a signed copy of the SignedApplet.jar file.
jarsigner -keystore susanstore -storepass ab987c -keypass kpi135 -signedjar SSignedApplet.jar SignedApplet.jar signFiles
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5. Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5: Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
In her working directory, Susan uses keytool to copy the certificate from susanstore to a file named SusanJones.cer as follows:
keytool -export -keystore susanstore -storepass ab987c -alias signFiles -file SusanJones.cer
Ray
Ray receives the JAR file from Susan, imports the certificate, creates a policy file granting the applet access, and runs the applet.
6. Import Certificate as a Trusted Certificate
Ray has received SSignedApplet.jar and SusanJones.cer from Susan. He puts them in his home directory. Ray must now create a keystore database (raystore) and import the certificate into it. Ray uses keytool in his home directory /home/ray to import the certificate:
keytool -import -alias susan -file SusanJones.cer -keystore raystore -storepass abcdefgh
7. Create the Policy File
The policy file grants the SSignedApplet.jar file signed by the alias susan permission to create newfile (and no other file) in the user's home directory.
Ray creates the policy file in his home directory using either policytool or an ASCII editor.
keystore "/home/ray/raystore";
// A sample policy file that lets a JavaTM program
// create newfile in user's home directory
// Satya N Dodda
grant SignedBy "susan"
permission java.security.AllPermission;
8. Run the Applet in Applet Viewer
Applet Viewer connects to the HTML documents and resources specified in the call to appletviewer, and displays the applet in its own window. To run the example, Ray copies the signed JAR file and HTML file to /home/aURL/public_html and invokes Applet viewer from his home directory as follows:
Html code :
</body>
</html>
<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
width="600" height="400" align="middle"
codebase="http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#Version=1,3,1,2">
<PARAM NAME="code" VALUE="SignedAppletDemo.class">
<PARAM NAME="archive" VALUE="SSignedApplet.jar">
<PARAM NAME="type" VALUE="application/x-java-applet;version=1.3">
</OBJECT>
</body>
</html>
appletviewer -J-Djava.security.policy=Write.jp
http://aURL.com/SignedApplet.html
Note: Type everything on one line and put a space after Write.jp
The -J-Djava.security.policy=Write.jp option tells Applet Viewer to run the applet referenced in the SignedApplet.html file with the Write.jp policy file.
Note: The Policy file can be stored on a server and specified in the appletviewer invocation as a URL.
9. Run the Applet in Browser
Download JRE 1.3 from Javasoft
good luck! [email protected]
i already give u many tips, i use 2 weeks to try this to success, hopw that u understand that, a result of success is not important, the process of how to get things done is most usefull!

DMM MAS345 via RS232 serial comunication

Similar Messages

Maybe you are looking for