Serial labview

i can´t write in my microcontroller a mega32 with labview but i can read (only number)
In visual basic work Ok tx and rx and in the terminal of codevision
no puedo mandar lo que deseo de labview a un microcontrolador(numeros)
del microcontrolador a labview si puedo y hasta lo garfico pero solo recibir
no creo que este mal mi programa del microcontrolador por que lo probe en un programa en visual basic y jalo bien al igual que en una terminal en codevision. funciona bien en estos rx tx
[email protected]

I don't know what else to say that isn't explained on the front panels of the examples. If you use the basic example, be sure you do not delete the \r\n controls characters that are in the 'string to write' control. Those are the Carriage Return/Line Feed control codes. You haven't explained anything at all of how you've programmed the micro. Does it expect a CR or LF at the end of a command? Does it expect it to receive text?
I have no idea what you are refering to when you say 'visual basic example'.

Similar Messages

Puerto serial labview

HOLA QUE MAS ,
ESTOY REALIZANDO MI PROYECTO DE GRADO DE INGENIERIA ELECTRONICA ,DICHO PROYECTO SE BASA EN UN PIC 16F874a QUE REALIZA MEDICIONES ANALOGAS A TRES SEÑALES DIFERENTES Y LUEGO LAS TRANSMITE AL PUERTO SERIAL DEL COMPUTADOR ,YA HE REALIZADO PRUEBAS EN LABVIEW Y RECIBE BIEN LOS DATOS DEL MICRO PERO TENGO UNA INCONVENIENTE QUE LOS DATOS NECESITO QUE LOS LEA EN UN ORDEN ESPECIFICO, YA LE COLOQUE CARACTERES PARA SEPARALOS EN LABVIEW PERO NO SE QUE PASA CON EL PUERTO SI SE BLOQUEA O NOSE PERO EN UN MOMENTO NO LEE NINGUN DATO O LA CADENA DE DATOS SE CORRE Y NO ES FIJO LA LECTURA , LA IDEA ES RECIBIR LOS DATOS EN EL ORDEN ESPECIFICO PARA VIZUALIZARLO EN DIFERENTES GRAFICAS PERO NO PUEDO POR EL PROBLEMA ANTERIOR, YA HIZE PRUEBAS EN HIPERTERMINAL Y RECIBE BIEN ,,,,,,,,,,,,,,,CONSULTE Y ME DIJERON QUE ERA EL BUFFER DEL PUERTO SERIAL ENTONCES NO SE DONDE ES EL PROBLEMA SI EN EL PIC O EN LABVIEW EN EL"PUERTO SERIAL"
AGRADECERIA SU COLABORACION EN ESTE ASPECTO............

Hola,
Me imagino que tienes algún problema en tu código. Si lo adjuntas será más fácil ayudarte.
Algunas otras cosas que podrías revisar:
La cajita que recibe los datos tiene una opción de terminaton char, deshabilitalo si no lo estas usando, ya que no te interesa que un valor de voltaje 0x13 sea confundido con un carácter de terminación y te de un comportamiento inesperado.
Si tienes etapas de alto consumo de potencia (como motores eléctricos) trata de separar la alimentación análogica de tu parte digital, y utiliza un condensador cerámico de 0,1uF lo más cercano a la alimentación de tu micro.
Mantener un pin intermitente, te permite visualizar a través de un led que tu micro no se ha colgado, y en labview tambien pudieses hacer lo mismo.
Saludos.
Luis A. Mata C.
Ing. Electrónico
Anaco - Venezuela

Serial Labview VI's for contorlling a Yaskawa SMC-4040?

Hello All!
Just wondering if any has or knows where there might be any Labview VI's for a Yaskawa SMC-4040 controller using the serial port?
Thanks,
Greg Newsome
Test Engineer

Greg--
      I just want to verify, this motion device doesn't need a controller. It is essentially a stand-alone instrument where you'll just send commands for whatever motion you need it to preform. Is this correct?
      If so, the driver that will allow you to send commands to your ports is NI-VISA. I think what you are looking for, or the best option, would be if there is an "Instument Driver" for this device. Instrument drivers are packages of all the commands you would send using VISA. I've looked and cannot see one on our website. If we do not have it, your best bet is to contact the manufacturer and see if they have anything.
      If you cannot find an instrument driver, you will still be able to communicate to the instrument manually using the VISA VI's and the command set for your instrument. The best way to see how to do this is to open an example from the NI Example Finder in LabVIEW. Go to "Help>>Find Examples" then Navigate to "Hardware Input and Output>>Serial" folder. I would suggest looking at the code for "Basic Serial Write and Read". If you have any questions let me know.
Regards,
John H
Applications Engineer
National Instruments

Serial LabView - 16bit microcontroller communication

I'm trying to make a Man - Maschine Interface (vizualization) between LabView and Infineon 167CR microcontroller. Communication between the both works fine, but I'm trying to figure out nice and convenient way to recognize the datas sent and to sort them so that I know whether it's engines temperature or engine speed data. Maybe someone already did something similar ???? Thanx in advance

there are a variety of ways of doing this depending on how much flexibility you need. if the data packet contents are constant, define a 'start of message' character or sequence of characters. convert your datavalues into single-precision and convert to hex. append all these 4-byte strings and put your start of message at the beginning of the whole thing and transmit it. at the other end the receiver scans for the start of message and (after stripping it off) takes the remainder, breaks it up into 4-byte chunks and converts each chunk back into a single precision number. a number's position in the message defines the value it represents.
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 serial VI for LakeShore Temp. Monitor #208

Hi folks,
does somebody have a ready-to-go serial LabVIEW VI to control the
LakeShore temperature monitor model 208 or know a source for download?
The National Instruments website doesn't support any serial-driven
LakeShore Instruments (GPIB driven well).
Thanks in advance - David

While I don't have any experience with the LakeShore devices, don't give
up on the GPIB drivers. Very often manufacturers of instruments with
multiple control interfaces will use the same command structure and
protocol for all the interfaces (to keep their firmware simple probibly).
If such is the case for LakeShore the conversion to serial could be very
trivial. For example, if NIs GPIB version uses the VISA drivers all you
might have to do is change one initialization string because VISA can do
serial IO as well.
Mike...
David Rabanus wrote:
> Hi folks,
>
> does somebody have a ready-to-go serial LabVIEW VI to control the
> LakeShore temperature monitor model 208 or know a source for download?
> The National Instruments website doesn't support any serial-driven
> LakeShore Instruments (GPIB driven well).
>
> Thanks in advance - David

Is it possible to choose the serial port if only the run time engine is installed

I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
the different ports. Any suggestions?

Hi Daniel,
Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
I have attached a Small VI to Illustrate this.
Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
I hope this Answers your Q!
Good Luck
Mache
Good Luck!
Mache
Attachments:
Serial_Port_Select.vi ‏36 KB

How to configure visa to adquire dat from serial port and then converted to numeric value from a home embedded device

I already stablish communication with my serial port using VISA, selecting COM1 as the resoure name.
After that, I tried to read the data from the port (as we know the data was in string format )but I need to convert the data to numeric value to hadle it (no arrays).
Another main thing is that I'm develoing a new based Embedded design and tthe info that will trhow out from the device to the PC is binary.
How can I solved the problem, and if I want to make bidirectional communication with my system how can I do it? The VISA intructions as *IDN? and so forthetc can be recognize by the external system if the COM1 port is recognized by NI Max as ADSRL1::I
NSTR1?

Hello,
For an example of bidirectional serial communication in LabVIEW, please see the shipping example LabVIEW <-> Serial.vi. This can be found from LabVIEW by going to Help >> Find Examples. From the example finder, select Hardware Input and Output >> Serial >> LabVIEW <-> Serial.vi.
Once you are able to read the string data in, you can use the VIs in the String/Number Conversion palette to convert the data to numeric format. To access these, right-click on the block diagram >> All Functions >> String >> String/Number Conversion.
Let me know if this does not help.
Regards,
Sean C.
Applications Engineer
National Instruments

Labview to communicate over usb with an Danfoss VLT Automation Drive FC 302 adjustable frequency drive

Has anyone used Labview to communicate over usb (or RS232/RS485) with an Danfoss VLT AutomationDrive FC 302 adjustable frequency drive ?
Thanks
Hierromovil

Duplicate - http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Labview-to-communicate-over-usb-with-a-Danfos...

Animatics dll calls

I've created Serial labview drivers that communicate with Animatics motors
(via RS-232) but was wondering if anyone's created a labview program that is
based on their SMI engine (SMIengine.dll) using Call Library Functions?
This would allow more flexibility such as compiling, error-checking and
loading a file directly from labview without having to do it through their
separate stand-alone application, SMI.
One issue I'm having in using CLF is that I can only "see" 4 function when
connected to their dll (SMIEngine.dll). Their manual exposes a slew full of
function but i'm unable to see them....
The only ones i can see are:
DLLCanUnloadNow
DLLGetClassObject
DLLRegisterServer
DLLUnregisterServer
anyone know why only these are exposed? I'm pretty new
to CLF's so maybe i'm
missing something?
If you've worked with Animatic Smart Motors in the past, I'd like to hear
your experiences.
If you're interested in seeing the DLL, email me or you can download the
SMI engine here: http://www.animatics.com/web/smi.html
Regis

The solution to using COM (Component Object Model) dlls instead of Standard
Dlls is treat them as ActiveX components. You can access them through:
1) register the DLL using the command prompt "regsvr32 smiengine.dll"
2) placing an Automation Refnum on the front panel.
3) Right click on the Icon and "Select ActiveX Class" ---> "Browse..."
4) You should be able to find your Component registered here in this list
(along with many other components)
5) From there, you can most likely use the "Invoke node" and "Property
node" to access the function calls....
Regis
"rl" wrote in message
news:[email protected]...
> Found out information from Animatics... Their SMIengine.dll is a "COM" dll
> and not your standard dll. That is why its not fully exposed when using
the
> CLF. Couldn't get more LV specific info since they have no expertise
> there....
>
> Anyone know how to access functions from a "COM" dll as oppose to a
> standard dll?
>
> Regis
>
>
> "rl" wrote in message
> news:[email protected]...
> > I've created Serial labview drivers that communicate with Animatics
motors
> > (via RS-232) but was wondering if anyone's created a labview program
that
> is
> > based on their SMI engine (SMIengine.dll) using Call Library Functions?
> > This would allow more flexibility such as compiling, error-checking and
> > loading a file directly from labview without having to do it through
their
> > separate stand-alone application, SMI.
> >
> > One issue I'm having in using CLF is that I can only "see" 4 function
when
> > connected to their dll (SMIEngine.dll). Their manual exposes a slew
full
> of
> > function but i'm unable to see them....
> >
> > The only ones i can see are:
> >
> > DLLCanUnloadNow
> > DLLGetClassObject
> > DLLRegisterServer
> > DLLUnregisterServer
> >
> > anyone know why only these are exposed? I'm pretty new to CLF's so maybe
> i'm
> > missing something?
> >
> > If you've worked with Animatic Smart Motors in the past, I'd like to
hear
> > your experiences.
> >
> > If you're interested in seeing the DLL, email me or you can download
the
> > SMI engine here: http://www.animatics.com/web/smi.html
> >
> > Regis
> >
> >
>
>

Control Temperature of WATLOW using RS232..Got vi ? to begin with?

Looking for vi which can help me conrol the temperature inside my little chamber (WATLOW) using RS232 port

If you are looking for generic serial example programs, go to Help»Examples»I/O Interfaces»Serial»LabVIEW<->Serial. Enter the com port and set both dip switches in the up position.
If you are looking for a instrument specific driver, you may want to contact the manufacturer to see if they have a LabVIEW driver for their instrument. If they don't, you can easily create a low-level driver by configuring an I/O assistant VI for each function in the manual. I/O assistant is one of the many new features of LabVIEW 7 and will parse instrument responses for you, which makes creating an instrument driver much easier. Once you have this low level driver you can just combine functions to make higher level VIs.

DA100 darwin yokogawa data acquisition unit

i'm using Yokogawa DA100 for measuring temperature and relative
humidity and sending out alarm to operate relays of ventilation fan.
But the problem is my DA100 have no such a calculation option within
it, so what i'm trying to do is using labview to apply this function
into. But i who just start using labview and also DA100, have no idea
how it could be done. so the main two problem i have now,
1. Communicating by receiving measured data from DA100 to computer and
then calculating and finally using that calculated value to operated
relay is what i have doubt could this be realized???
2. i try to operate normally the labview file which provided by both
ni.com and yokogawa, but i found that there are some errors occur when
i
want to start measuring or even set range,though i already
initialized RS232c. Do anyone ever try Vi provided by both ni.com and
yokogawa?
Best regards
Areemit

I have not used it, but I did download it from NI's website. Did you get the Serial version from their website? Yokogawa DA100 Serial LabVIEW Plug and Play Instrument Driver and Yokogawa DA100 GPIB LabVIEW Plug and Play Instrument Driver will take you to pages where you can download either the GPIB or the Serial version. Make sure that you use the Serial version and not GPIB (if that is the interface you are using).Message Edited by Molly K on 02-18-2005 11:54 PM
J.R. Allen

Implementar protocolo de comunicação serial UART no LabVIEW

Boa Tarde,
Estou querendo implementar o protocolo de comunicação serial UART no LabVIEW.
A descrição do projeto é mais ou menos essa:
- Uma Interface no LabVIEW para receber o dados enviados pela serial UART;
- Uma DAQ NI USB-6212 irá receber o dado por um pino digital ou analógico (a princípio estou usando um pino analógico);
- Um microcontrolador que envia dados através da serial UART;
- Sistema operacional Windows 7;
Estou querendo implementar o protocolo de comunicação pelos motivos:
- Usei o Visa da comunicação serial e um cabo USB-Serial genérico, mas não consegui taxas de recepção rápidas como eu preciso, quando eu tentava transmitir dados de forma mais rápida, eles chegavam corrompidos;
- O exemplos que encontrei do protocolo implementado usam o LabVIEW FPGA, e pelo que eu li minha placa de aquisição (NI USB-6212) não suporta FPGA.
Tem algum exemplo ou sugestão de como devo proceder.
Desde já agradeço.
Atenciosamente,
Fernando Esquírio Torres

Good morning, Fernando,
Here are some links to help in its implementation. Any questions please contact us.
What Is the Basic Architecture for Serial Communication?
http://digital.ni.com/public.nsf/allkb/E0D95CB9249FB8CF86256C68007B1F81?OpenDocument
Can I Do 9-bit Serial Communication Instead of 7 or 8 bits?
http://digital.ni.com/public.nsf/allkb/3BDC7FF03541F772862564990057F919?OpenDocument
9-Bit Serial Writing in LabVIEW
http://digital.ni.com/public.nsf/allkb/E0D95CB9249FB8CF86256C68007B1F81?OpenDocument
Serial Communication Starting Point
http://zone.ni.com/devzone/cda/tut/p/id/4049
Serial Communication - Basic Serial Write and Read
http://zone.ni.com/devzone/cda/epd/p/id/2669
Enviar ou Receber Dados Binários / Hexadecimais Utilizando NI-VISA no LabVIEW
http://digital.ni.com/public.nsf/allkb/33C1056D66078118862577450061E683?OpenDocument
Sending and receiving serial commands using VISA
http://zone.ni.com/devzone/cda/epd/p/id/2423
Sincerely,
Mauro Vera
Applications Engineer
National Instruments

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Problem on WinXP / Labview 6.1 with VISA (serial port)

There is a problem on WinXP / Labview 6.1 with VISA which i use to poll the state lines of the serial port. The only functions that i use are "VISA Open", "Find Resource", line state properties and "VISA close".
On my own machine (WinME) it works fine as a standalone application (with runtime engine in the same direction), even if i rename the Labview directory so that Labview is not found.
From my VXIpnp directory i deleted all but these files:
directory "Win95",
subdirectory "Bin" containing "NiViAsrl.dll",
subdirectory "NIvisa" containing "visaconf.dll".
When shipping this to WinXP (and copying "VXIpnp" to the root directory), the serial port was not found, so i renamed the direction "Win95" to "
WinNT", but this did not work also.
I installed the VISA server, although it seems not to be required -- no result.
Final question:
What must i do for distributing the program as a standalone application for all windows platforms?

Hey Joachim,
In order to create an installer that includes the VISA Run-time engine for serial IO you will have to purchase LabVIEW 7.x. See screen shot. This packages a small compact version of the run-time that can only be used for serial, but it takes up much less space. The installer that I created has my application, the LV Run-time, and the VISA run-time and it is about 26 MB.
That is much smaller than if I had to include the 32 MB LV 7.1 run-time and the 14 MB VISA run-time separately. It would have been even smaller if I would have uncheck some of the items that I wasn't using.
-Josh
Attachments:
advanced.JPG ‏31 KB

I am trying to reset a serial device through serial port ,MAX is able to do it but the same command is not working in labview

max can do it but labview cant

- Run NI Spy Tutorial
- Reset the serial device in MAX
- Run the LabVIEW code
- Post the *.spy file.
The spy capture will show any difference in function calls to the driver.

Serial labview

Similar Messages

Maybe you are looking for