Labview communication balance ohaus

Bonjour,
Je travaille sur labview 7.1 et je n'arrive pas à communiquer correctement avec ma balance (ohaus arc120).
Pour comuniquer j'utilise un cable rs232 croisé que j'ai fabriqué à partir d'un cable droit et un adaptateur usb/rs232.
Lorsque je récupère les données de la balance via le bouton print de la balance, tout marche, j'ai la bonne valeur.
Mais lorsque je la commande avec le pc, je n'ai pas toujours de signal. Lorsque j'en ai un, la valeur que je recois est éronnée. le nombre d'octets lu n'est pas constant et il y à des erreurs de cadrage: il manque une partie de la valeur (ex: 2,3g au lieu de 2,83g) ou m'indique totalement autre chose ( caractères spéciaux, lettres...)
De plus je ne recois aucun signal si dans mon VI je ne répète pas 7 fois l'instruction écrire dans une boucle. Pour la tare c'est pareil, je dois répété l'instruction 5 fois.
Pour réussir à écrire puis à lire il faut que j'ouvre un session visas pour écrire, que je la ferme, puis que j'en ouvre une nouvelle pour lire. Sinon il n'écrit pas.
J'ai aussi essayé de communiqué directement en rs232. je recois la bonne valeur en appyuant sur le bouton print, mais je n'arrive pas commander la balance.
J'ai vérifié les paramètres de transmissions, ils sont correctes.
Pouvez-vous m'aider ?
Merci beaucoup
Cordialement
Solved!
Go to Solution.
Attachments:
arc120.pdf ‏129 KB
balance avec deux sessions visas.vi ‏129 KB
capture d'écran.doc ‏79 KB

Try this PIN out for RS232 cable :
Below are the two cable configurations that will work with 9 pin and 25 pin serial ports. You will notice that pins 2 and 3 are not crossed in the 9 pin but are in the 25 pin. In any case pins 5 and 6 have to be shorted at the balance end of the cable. One cable type will work with both balances.
Ohaus Part number - AS017-09 Used with AP, AS, C, CT, E, G, GT, I5, TP, TS, MB200, Adventurer, Explorer, Voyager, Navigator and Scout.
Cable - balance to PC
9 pin(F) to 9 pin(F)
Balance pin -----to----- PC pin
PIN 2 (TXD) -----to----- PIN 2 (RXD
) PIN 3 (RXD) -----to----- PIN 3 (TXD)
PIN 7 (GND) -----to----- PIN 5 (GND)
For balances other than Adventurer pins 5 & 6 must be shorted together at the balance and NOT connected to the computer. This is not required in the Adventurer balances.
CLA 2014
CCVID 2014

Similar Messages

Siemens S7 300 PLC and Labview Communication

Hi,
I am attempting to communicate between Labview 7 and a Siemens S7 300 (CPU 314) PLC. I would prefer the communication to be over Ethernet or RS 232. Could you help me out with this implementation and let me know what additional hardware/software I may require for doing this.
Thanks,
Shameek

Shameek wrote:
I am using a CP-343 communications processor to connect the S7 300 to industrial ethernet.
Now can I commnicate directly from Labview to the PLC?
I still havent figured out where the OPC server comes in and whether it is an option or a necessity.
Using OPC is an option.
Siemens has an the add-on ($$) library/FB that includes code for enabling Modbus communication with S7 300 CPUs. I've never used it, but info is here.
<snip>
Our solution
With its MODBUS function block (FB) and the CP343-1 and CP443-1 SIMATIC S7 communications processors, Siemens can supply a proven solution for the integration of SIMATIC automation systems into other system landscapes. This function block enables data to be exchanged easily between MODBUS-compatible devices from different manufacturers and SIMATIC S7 stations from S7-300 and S7-400 systems.
</snip>
=====================================================
Fading out. " ... J. Arthur Rank on gong."

Labview : Communication série avec un périphérique

Bonjour,
Sous Labview, j'essaie de communiquer via un port série à un périphérique. En parallèle, j'essaie de recevoir et d'envoyer des données. Je voudrais me placer en mode écoute (Activer la réception sur ce port : Visa read) puis envoyer une commande (Visa write). De ce fait, en se plaçant en écoute avant l'envoie de la commande, je suis sûr de recevoir la réponse du périphérique.
Je veux donc envoyer un caractère tout en écoutant sur le même port com la réponse de mon périphérique (J'ai déjà un doute à ce sujet. Avec un port série, on peut lire et écrire en même temps ? )
Mon problème est le suivant : En lançant ce programme sous Labview, il se place en écoute mais n'envoie pas le caractère de commande (montage en parallèle). Après le timeout de l'écoute (Visa read), le programme écrit bien le caractère (Visa write) comme un fontionnement série.
Comment réaliser des tâches multiples en parallèle sur LabView ? Auriez-vous un exemple ou plus d'information à ce sujet ?
Merci,
Jérémy

Bonjour,
je confirme le fait qu'un UART ne peut pas travailler en "parallèle".
Pour dialoguer avec un équipement, il faut envoyer une commande "Write" si besoin, pour que le produit te réponde.
Tu récupères ensuite la réponse avec un "Read".
Pour dimensionner le nombre de données à lire, plusieurs méthodes par la suite se présente à toi.
- Attendre un certain temps : Interruption de la lecture sur timeout
- Attendre un caractère de terminaison \A : 0xD par défaut.
- Lire un certain nombre d'octet : Utilisation du noeud de propriétés nbre de bytes sur la liaison fortmeent conseillé.
Si après une manipulation simple, tu ne relies pas de données, n'hésites pas à mettre une temporisation de 100 ms entre ta requête et ton écoute, il n'est pas rare d'avoir des équipements avec un temps de réponse de l'ordre de 50ms sur port série (spécification présente dans la documentation de l'équipement en général).
Bonne journée,
Michael

Local SQL Database & Labview communication

I created an sql database with sql server 2008 R2. I wish to be able to insert data to this database locally. Can someone please tell me if this can be done, and if it is possible, could someone give me the steps I have to follow?
Thanks.
Solved!
Go to Solution.

Another source of information would be a 3 part series on databases (check the link in my signature). The process is largely the same regardless of the DBMS you are accessing.
With SQL Server you will need a user I'd and password. Did you install the SQL Server yourself?
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

Using existing c code for usb-hid communication in labview

Hello,
I want to write a simple temperatrue logger using labview and a external hardware which communicates over usb-hid. The external hardware uses an ATMEL 90USB162 µC and DS18B20 sensors.
Link to the hardware:
http://www.diamex.de/dxshop/USB-Temperatur-Sensor-Tester-fuer-DS18B20
The source of a a simple command line tool is available (see attachement), which reads out the temperature value of the connected sensors.
Is it possible to include this c-code in the labview application to simplify the communication?
Thanks a lot and best regards,
Michael
Solved!
Go to Solution.
Attachments:
CMDLINE.zip ‏17 KB

I'm not that experienced at this personally (in terms of compiling C code into DLLs), but I believe the process you need to go down to call your C code in LabVIEW is to compile the C code into a DLL which you can then call from LabVIEW using a Call Library Function node (or you can try to use the "Import Shared Library" wizard to automatically generate SubVIs).
There's more information here:
http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

PLC Communications with Labview

How do I view and record data from my plc to labview, currently we are using autmation directs DL205 with the 260 processor

If the DL 205 communicates through the Modbus protocol, you could use the Modbus library. This library consists of a bunch of VIs which can be used for Modbus communication. Think of them as advanced Serial read/write VIs. However, if you are looking into monitoring, datalogging and controlling the registers, then I would recommend the LabVIEW Datalogging and Supervisory Control Module. Using shared variables, you can then easily bind, control and talk to the registers and most of the work is taken away from you.
If the DL 205 doesn't communicate throught the Modbus protocol, then you would need an OPC server (like the NI Industrial Automation OPC Servers) and the LabVIEW DSC Module. You can then communicate from the LabVIEW DSC Module with the OPC server.
Message Edited by Adnan Z on 03-15-2007 10:27 AM
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Serial Communication problem in LabVIEW 7.0

I recently upgraded my test computer from a 450 Mhz machine to a
Del 2.8 Ghz Pentium 4processor with 512meg's of ram using Windows 2000 for the operating system running LabVIEW 7.0.
I use the serial port to communicate with a piece of hardware,
Rs232, 115200 baud, 8 bits, 2 stop bits. NO hardware or software handshaking
The hardware is capable of receiving data from the computer at a full 115200 baud up to 65k transfers at a time with no extra delays.
The problem that the serial data coming from the new Dell computer will send out 2 bytes then waits 2 to 3 milliseconds and sends 2 more bytes.
I generated a separate serial VI that will jest shove data out the serial port.
The VI is a VISA configure serial po
rt, into a while loop that contains 6 VISA Write VI
And on the backside of the wile loop a VISA close.
The above VI will generate the serial data stream as stated above
EXCEPT when I put a PROBE on each of the ERROR OUT of the 6 writes, then the serial port will generate a continuous serial data stream with no millisecond breaks.
I have changed the FIFO Buffer settings (all the possible combinations) of the serial port in Windows 2000, and that has hade no effect.
Any help would be greatly appreciated
James Zumstein
E-mail [email protected]
Attachments:
Serial_Test_1.vi ‏45 KB

Greetings!
Serial port commucations problems can be a real joy, can't they? Have you tried communicating with your instrument with Hyperterm? Usually Hyperterm is capable of operating with almost no overhead, so you can see if there's any strange symbols being transmitted that might be holding things up. There might be an extra CR being inserted, or something like that, which will show up as heiroglyphics in Hyperterm. See if all your symbols coming back are valid. This is where I usually start.
Hope this helps.
Eric
Eric P. Nichols
P.O. Box 56235
North Pole, AK 99705

What communications protocols does LabView support?

A customer of mine is using LabView. He has asked me if I can communicate to it using a PLC. Either GE Fanuc or Allen-Bradley. I need to know what methods of communication that LabView has available to talk to these PLC's.

The short answer is: whatever protocol you want to talk...
I have developed applications talking to AB stuff, modbus (which will cover most PLCs) and even TI's old proprietry PLC protocol. There are lots of tools for making the connection in lots of ways.
What are they specifically needing--or do they know yet?
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

Labview data communication c borland builder ram memory

I have data generated by labview and I want it send to borland c++ builder as variable. but I dont want use the hardrive. how can I communicate with C++. the communication must be fast.
greeting paul

There are two ways to do this:
1.Pass the data value or pointer of the data that generated by LabVIEW vi to your c code using "call library function"
2. Have your C code to call LabVIEW using LabVIEW activeX server and get the data from the vi.
You can find examples in NI website, search for key words like "call external routine in LabViEW" or "call LabVIEW in C"
Irene
[email protected]
www.hytekautomation.com

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.

Interprocess Communication C++ - LabView

Hi,
I have a C++ *.exe file wich is grabbing images with a Matrox framegrabber. This program ist startet via "system exec" from LabView. I want to do a kind of time measurement with this program so i need the exact time when the grabbing of frame starts. At the moment I dont know how long the *.exe file needs to initialize the framegrabber (something about 500-1000ms).
My idea is to start a continous grabbing but start saving the images when another command via LabView will be send to the C++ application. But I don't know how to send this command! It should be a kind of a "wait until key pressed" controlled by LabView. Maybe a global bolean or something like that.
I hope somebody can help me!
(programming with LabView 7.0 and Visual C++ 2003.NET)

Hi,
What
you are looking for is called an “inter-application communication”.
There
are several options to realize it. LabVIEW supports TCP/IP, ActiveX or UDP to
communicate with another application. So
it’s not as simple as using a “global Boolean”
as you mentioned.
I advise you, to use the LabVIEW
examples which shipped with the NI example finder to get some programs as
reference. Search for keywords like TCP/IP, ActiveX and UDP.
Attached
you’ll find a link to a knowledgebase.
Hope this helps.
How Do I Use LabVIEW to Communicate with Other
Applications?
http://digital.ni.com/public.nsf/allkb/B3959ED76D55A9E586256965004D8092?OpenDocument
Regards,
Ulrich
AE NICER

USB RAW Control Communication in LabVIEW

Iam trying to open the zipped file by NI "USB RAW Control Communication in LabVIEW".The VI is attached below.It recognized my raw device in VISA Resource Name.Iam using a pendrive.But while running it shows an error 'VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot currently access it.'I learned this problem from some discussion forums in labview,but can't find a solution.Plz help.Post your valuable suggestions........Also in that example how we will give the request,request type,value,index etc:-.What does it indicates?
Thanks as kudos only
Attachments:
USBRawControl.vi ‏152 KB

STOP creating multiple posts for your question!
http://forums.ni.com/t5/LabVIEW/Requirements-to-read-from-a-USB-port/td-p/1959445

Labview : No USB communication with the DLN-2 adapter board.

Hi,
I am trying to use a Diolan DL2-N USB to I2C/SPI/GPIO adapter (https://diolan.com/dln2). This manufacturer provides Labview drivers for the board as well as example VIs. I just want to use them to access to all interfaces via Labview. After that I will design a test setup for our last product line using this adapter board.
What i did:
1) Fresh install of Labview 2014 (evaluaton version). System: DELL Precision M6800 (i7) , Windows 7 Professional SP1.
2) Install NI VISA drivers and NI-488.2 drivers (14.0).
3) Install manufacturer drivers as explained in NI website.
4) Run Labview. I can see instrument driver VIs under the Function Palette and run example VIs. So far, ok (I guess)
5) Run NI MAX. No USB ports listed. Only COM1 and LPT1 (printer port).
6) I ran some windows test apps provided by the manufacturer to access to all the interfaces of the NXP microcontroller in the DLN2. Everything works. I can read analog/digital inputs, force digital out values and use the SPI and I2C (I see the SPI/I2C frame sin a scope).
I have spent one day going through different links in NI website (have watcheing almost every demo video on the site) and still are not able to guess why Labview can't see my USB device.
Any hint?
Regards,
Jose
Solved!
Go to Solution.

Hi again:
I' m putting pressure on the manufacturer to provide support, but still I have some very basic questions that I think a Labview expert should be able to answer.
Attached are the driver files provided by the manufacturer along with install instructions (which I do not fully understand). I assume the iinstall description is based on a standard procedure to install third party instrument drivers , but still don't know what to do with the dln.net.dll file (I just copied it in the /Labview 2014/instr folder). Any hint?
The manufacturer website says that the driver has been developed for Labview 2012 . I' m using Labview 2014, and assuming backward compatibility. Is that correct?.
One more question: Is there a way of seeing within Labview which third party instrument drivers do you have installed?
Regards
Jose
Attachments:
DlnLibrary.Net.llb ‏574 KB
readme.txt ‏2 KB
dln2_drv.zip ‏338 KB

Serial communication works in hyperterminal but not in LabView

Hello,
I am trying to control an APP Automated Pressure Controller using LabView 6.1 via a serial connection. I am able to control the system with Hyperterminal but not with LabView. I set used the same setup (9600 baud, 1 stop bit, no parity, no flow control, etc) in LabView that worked in hyperterminal.
According the the documentation from the Pressure Controller: "Every character that is sent to the controller is echoed back to your computer so you can check to see everything is working. When a valid command is given, the controller will also send a carriage return (acsii 13) followed by a line feed (ascii 10) to signify the command was executed. Before sending any commands, the program should clear any characters in the input buffer that may be there from previous responses."
In hyperterminal, when I type in a command such as "OA", the Pressure Controller responds (without pressing enter or any other keys) and I can see the "OA" on the screen. As soon as the Controller is done responding, the cursor moves down to the next line (which I assume is caused by the carriage return and line feed) and waits for the next command.
I have tried to use the Serial Communication.vi with no success. Does Hyperterminal add (or Labview omit) a special character or command that I am missing? Do I need to do something special to clear the input buffer in LabView?
Thanks for any help.
Alex

Hello,
Try to run your application in other system (computer),
frequently some PCs configurations are not recognized by LabVIEW serial
routines. I do not know exactly the problem but is not the first time I know
that kind of problem.
Sometimes the problem comes from the serial property called
Termination Character that enables receive buffered data once you have a
Carrier Return or a Line Feed symbol (Hex 0D/0A) character into the buffer. Try
to set it true and assign a 0A Hex Value.
For sending information you need to finish all command
message with an enter symbol concatenating both (Message + Hex 0D0A) using the
special character in the string palette library. This action permits system to
put out buffered data.
Good Look

How can i interface labview to Two way Radio freq (452 MHZ, 450 MHZ) transreceiver for point to point communication?

Transreceiver specications are nearabout
point a to point b message 452 MHZ
and point b to point a message 457 MHZ
transmit power 2 watt
Transmitting 16 bit data

The PXI-5660 RF Signal Analyzer is a PXI-based hardware product from National Instruments that can receive signals from 9 kHz to 2.7 GHz with a 1 W max input power. If you transmit at 2W and after reaching the antenna connected to the 5660 the power is > 1W (+30 dBm), you will need an attenuator in front of the 5660 to bring the signal level down to a point which the 5660 can handle.
As for the Tx side, you can Tx with the PXI-5670 RF Vector Signal Generator at a max output power of +13 dBm, which is ~20 mW. You would need an RF amplifier for sure between the PXI-5670 output and the ensuing antenna.
In both cases, the devices come with software to control them that are LabVIEW-based and quite easy to use. If you already have RF Tx and RX hardware, they
probably have LabVIEW drivers, or some other interface with which LabVIEW can interact with. I recommend contacting NI at 1-800-IEEE-488 and asking for an internal sales representative to discuss your app with. Or, you can post more details here and I can definitely answer your questions.

Labview communicat​ion balance ohaus

Similar Messages

Maybe you are looking for

Labview communication balance ohaus