Communication PIC-SERVO/LabVIEW

someone could help me Im working in the control of the motor using the PIC-SERVO board, to comunication using the SSA-485v2 adapter board and the functions for this in LabVIEW2014, using USB interfaz. but to run the program(PIC-SERVO TESTER) I have a trouble to comunication I installed the driver to SSA-485v2 to Windows 8.1 I using this. To run the Vi I have this error:
I set the port COM3 and is ok
I review the Measurement & Automation Explorer and
I found this the COM3 is ok but there the error view this picture
 Someone can hep me
thanks for your support

Duplicate - http://forums.ni.com/t5/LabVIEW/PIC/m-p/3158198#M910626

Similar Messages

  • Not getting output from pic-servo board

    Greetings everyone and thanks in advance. I wish to use a Pic-Servo SC controller  board (http://www.jrkerr.com/) to control a single stepper motor, using LabView. Here's what I've done so far:
    -I already have installed 32 and 64 bit LabView (2011) and tried the test program in both
    -VISA controller is properly installed
    -USB to Serial FT232R converter is also installed, and configured in 19200 baud rate
    -COM3 port is shown as the assigned port for the controller, and selected as such in LV
    So far, I have managed to get the test program to run without communication errors, but upon sending any commands to the motor, it is completely unresponsive and behaves like it has no current or controller attached, despite it being configured in the basic 1-motor setup specified by Jrkerr site.
    Any help, comment or suggestion about how I could manage to get the motor moving will be welcome.

    Van you attach the manual? I get an error every time I try. I'm not convinced that it is RS485 from the brief product description. It talks about buying a RS232-RS485 adapter to communicate to multiple controllers.

  • Comment flasher un pic à travers LabVIEW

    Bonjour,
    je suis entrain de programmer un microcontrolleur STM32w108 (sous IAR). Est-il possible de flasher le pic à travers LabVIEW? 
    Merci,

    There is no native way to flash a processor from LabVIEW.  You'll either need to call an external program to do it (if you have access to such a program, you can use System Exec to run it), or you'll need some code already on the processor that can receive new code over some interface (serial, CAN, etc) and write it to the processor's flash memory.  I've seen sample code for this for Microchip's dsPIC processors, perhaps similar sample code exists for your system.
    If you happen to have access to the LabVIEW Embedded Toolkit, and it supports your processor, then there may be an easier way to do this.

  • Help me about communicating PIC microcontroller with Labview

    Hi everybody!!!!!!!!
    I have a few issues about data acquisition in Labview,so i need your instruction.
         Right now,I want to practise a project about the serial communication with PIC16F877A microcontroller ( a microcontroller of Microchip,40-pins,already integrated 10 bit A/D module,with 8 channels)  ,developing the user interface in the Labview 8.0 software.
         My goal is data acquisition from multiple sensors:such as LM35 temperature sensor and a pressure sensor,analyzing and display the data-time graph in Labview
         I intend to use ANx-pins (analog input pins,having 8 pins) in PIC16F877A,connecting to data-pin from sensors,then I use the TTL outputs of the PIC in combination with a MAX232 serial driver chip.As you know,the mAX232 simple converts the TTL outputs to RS232 outputs and forword them on.
         It is of no use to be able to collect various sensor readings into the PIC if there is no-way to transfer that data to a location where a user can use it.To solve this problem,I choose to implement a standard RS232 serial link between the PIC MCU and my personal computer (using DB9 COM terminal)
         This meant that I would need to initialize the A/D converters each time I want to read from a different A/D sensor because the two sensor dit not share a common configuration.
         My troubles is how to transfer data from sensors through PIC MCU to Labview,using RS232 standard,how to program for Labview,which I have to use:files of Serial communication in Serial.VI,or DAQ funtions in DAQ pallete?
       P/Sorry,my English is not good,expecting your sympathy!
       If it is impossible,you could send me an instruction or the same examples in detail,my mail:[email protected]
    THANK YOU VERY MUCH!!!!!!!!

    It would be best if you were to re-post this to the LabVIEW forum.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • BSOD controlling Nanotec servo (Labview+visa+Daqmx)

    I'm using a set-up where I control a servo with Labview. I run the VI, set some speeds to the servo, and within minutes, Windows gets a BSOD. I would like to know the cause of the problem and a fix please.
    What am I using?
    - Windows 8.1 (and windows XP before)
    - Labview Student Ed 2014
    - NI Visa
    - NI Daq mx
    - USB to RS-485/422/232 Converter
    - Nanotec servo
    - Nanotec Labview example: http://en.nanotec.com/support/application-notes/labview-example/
    What happens?
    I open the VI, set the com port. Run the VI and set some motor speeds. Within minutes windows 8.1 gives a Blue Screen, with the error MULTIPLE_IRP_COMPLETE_REQUESTS. In Windows XP, this gave the error IRQL_NOT_LESS_OR_EQUAL. After rebooting, windows 8.1 shows Automatic Repair. 'Automatic repair couldn't repair your PC', and refers to C:\WINDOWS\system32\Logfiles\Srt\SrtTrail.txt.
    This is 'Startup Repair diagnosis and repair log'. This gives some actions that take 0ms, untill finally:
    Boot critical file c:\windows\system32\drivers\nipbcfk.sys is corrupt.
    Repair action: File repair
    Result: Failed. Error code =  0x2
    Time taken = 8546 ms
    Opening that file in notepad shows this: http://pastebin.com/dwp2X5er
    Can anyone spot why Windows goes into a BSOD, and how this can be prevented?

    It sounds like the installation of some NI drivers failed on your system. Can you please re-install those? I recommend to uninstall the current installed ones first.
    Also, please try to install the latest driver versions. If you are using old drivers (e.g. from an out-dated driver DVD), it is possible that you have drivers installed which were never tested with Windows 8.1.
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Communicating USB using Labview VISA

    I have a USB RAW device that I am trying to communicate with using labview VISA. I have had success with setting up the driver and I am able to get information from the device such as serial number, etc. When I try to use the VISA read and write commands, I have no success getting the information I want. The commands are simple: R SP<CR><LF> is a read set point command. The only thing I do get back for every command I try, is a 2 byte message "01 60"hex.
    If you have any suggestions, I would appreciate it, thanks!
    [email protected]

    Hello Chris, I do not receive any errors and yes, I am including the termination characters in the string.
    Here is what I get when I use a USB port monitor when I send out this string.
    Thanks!!
    [94] URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (SUCCESS/0x00000000) 20101119150318.131 (+0)
    Pipe handle: 0x87696D6C
    Transfer flags: 0x00000002 (USBD_SHORT_TRANSFER_OUT, USBD_SHORT_TRANSFER_OK)
    Transfer buffer MDL: 0x88C47208
    Transfer buffer length: 6
    Bytes transferred
    0x0000: 52 20 53 50 0D 0A (R SP.. )
    [94] URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (SUCCESS/0x00000000) 20101119150318.147 (+16)
    IRP status: 0x00000000 (STATUS_SUCCESS)
    Pipe handle: 0x87696D6C
    Transfer flags: 0x00000002 (USBD_SHORT_TRANSFER_OUT, USBD_SHORT_TRANSFER_OK)
    Transfer buffer MDL: 0x88C47208

  • How to use GPIB communication check in LabVIEW

    There is one power supply in our office from Agilent. How to develop software for that Power supply using LabVIEW we should be able to change the
    voltage via GPIB interface.

    If you have the GPIB commands for your Agilent device in its product manual and a GPIB card, just go to Block diagram functions-> instrument i/o-> gpib and you have a set of GPIB functions.
    Also look at attached VI ( taken from labview examples shipped with labview) to get an idea on how to do GPIB write
    Regards
    Dev
    Attachments:
    LabVIEW_GPIB.vi ‏44 KB

  • Communication lost between labview 6.0 opc to rslinx

    I am reading i/o tags from an allen bradley 5/05 through rslinx using ethernet settings. Everything works fine, I read and write to the tags all day. However, If I go online through the ethernet it seems like all the bandwidth is used up and labview displays an error. maybe opc times-out. When labview is retrieving just i/o through opc, it works fine. But if it is retrieving i/o and gathering analog data from a MIO card and you try to get on the plc it faults out. Anything would help. I have attached i/o read/write vi
    Attachments:
    NEW_OPC_Digital_Functions.vi ‏134 KB

    You could try accessing the i/o on the plc using the 'Server Explorer' program. If you do not have that program you can download it at: :Server Explorer. Server Explorer is a utility that allows you to view and interact with available OPC servers. You might also try accessing the PLC from two different computers at the same time to see if it is a problem on the PLC side. There are not any known issues with DataSocket OPC like this so you might also contact Allen Bradley about the issue.
    Regards,
    JR A.
    Application Engineer
    National Instruments

  • Eurotherm 2416 communication problem in LabView 8.5.1 via COM1

    I have downloaded the latest version of a driver ET24xx v from NI site, and it is not working. I am getting Time out error from VISA. I think, the controlled is hooked up properly on my COM1 port. Visual Basic software is able to reach him and to communicate with the controller.
    Please help.
    Joe
    My email is: g e m b a r @ t p r l dot co m (slightly changed for spammers)

    Howdy Joe,
    Several things can cause a VISA timeout. Improper message termination most frequently causes timeouts. Also, which VI in the E24xx driver package do you try to run that times out? After extracting the ET24XX driver to your labview\instr.lib directory, you should be able to access its examples by navigating to Instrument Drivers»ET24XX»Examples in the Functions palette. (Make sure to select the proper COM port on the example's front panel).
    Going back to the issue of improper message termination--verify that each message you send to the instrument has a termination character such as \n, \r, \n\r, etc.
    Let us know!
    Warm regards,
    pBerg

  • Communicating Between Multiple LabVIEW Executables on different computer using Shared Variables

    hi,
    I need to develop some executables which will be launched on different computer of a LAN. Some DATA are common. I need to share the data using shared variables.
    I usually used LabVIEW so I 'm familiar with shared variables but in this case, the RT target is a part of my
    project.
    I do I need to procceed in my case?
    thanks

    Ok but it's not my configuration and I haven't found my answer in the tutorial.
    You speak of a case where there is a computer and a RT target under the same LabView project. As I said earlier, I often use labview RT and shared variable between computer and RT target. But I assume here it's different.
    My question is : how do you acces to the SVE from 3 computers (without any RT target)? 
    1. If I create 3 labview projects using the same Shared Variable, do I need to use the same .lvlib on each project?
    2. Is it possible? 
    3. How can I configure where the SVE should be? When I use a RT target, It only depends where I put my Lvlib. But here there is 3 projects. 
    James
    Attachments:
    Sans titre.JPG ‏9 KB

  • No SDO Communication Using CAN over EtherCAT (CoE) with 3rd Party Slave

    Dear all
    We are trying to establish an EtherCAT communication between a cRIO 9024 as EtherCAT master with a 3rd party frequency comverter (bmaxx 4432) as EtherCAT slave. CanOPEN over EtherCAT is industry standard.
    The slave device has a CAN in Automation (CiA) configuration 402, i.e. motion and drives. Thus it has a well configured address range, input/output parameters and the like. The frequency converter remains in INIT mode and waits for a PDO definition, sent via an SDO communication. 
    In LabView, adding an EtherCAT master in the cRIO system works fine. Adding targets and devices on the configured EtherCAT master also works fine after we imported an XML description of our third party EtherCAT slave. LabView detects the slave type and the version correctly. Thus, there must already be a rudimentary EtherCAT communication working between LabView and our 3rd party slave.
    The problem is that we cannot establish a first SDO communication.
    Every description I found was about using CANopen on a CAN bus hardware (e.g. NI 9861) plugged into the cRIO. Descriptions concerning EtherCAT are usually concerning an NI cRIO 9144 extension as slave, which is not what we have.
    The NI CANopen library seems to definitely require the NI 9861.
    Is this correct?
    1)
    Either it should be possible to define a kind of virtual CAN port based on the EtherCAT port, on which we can write to and read from with the NI CANopen library. This would be the preferred solution so we can use the CANopen VIs.
    Is there a way to do this?
    2)
    Otherwise, there should be a possibility to establish a more basic SDO/PDO communication directly based on the EtherCAT interface.
    Are there any NMT/SDO/PDO VIs available to do the programming?
    Is there a manual document which would describe how to start the first communication setup via EtherCAT (CoE)?
    My sincere thanks for any advice you can give.
    Many cheers
     Markus

    Dear all,
    I'm trying to establish a connection between a cRIO9068 and a BM 3300 via CoE.
    I already had a hard time establishing a normal EtherCAT-connection.
    Finally I could set the Scan engine to active, and I was able to get from "ini" and  "pre operational" into "Safe operational" and "operational".
    As I can see, you had similar problems as I do.
    When I add my cRIO to my project (with the EterCAT-master)  I can look for the slave device, and add it to my project.
    Within this slave device, I can add two mods, as seen in the attachment.
    These slots should include all the parameters, the drive provides, but actually I only end up with some "position mode" -parameters, I think those are the SDO's.
    If I add these to a VI, the cRIO scan engine switches to configuration mode, but can't switch back to active mode.
    Actually, the Baumüller slave device should be able to provide multiple parameters for read and write.
    I can see them, wehn I go to "online device state" in the rightklick menu of the slave device (Parameter.png), but there's no way I can actually use them.
    I can't add these "slots" on every computer.
    On some computers it's possible, on some it isn't.
    Thanks for any advice, you can give.
    Yours sincerely
    Karl
    Attachments:
    slot 1.PNG ‏6 KB
    slot 2.PNG ‏9 KB
    Parameter.PNG ‏46 KB

  • How to transfer file from PC to PC via serial port using labview

    I need to transfer files(.txt, .doc, .xls) from PC to PC via serial port using LabVIEW. Is it possible to transfer files, if so how to transfer?
    Solved!
    Go to Solution.

    Yes, it is possible to transfer files with the serial port using LabVIEW.  Files are just collections of bytes and the serial port is pretty good at shipping bytes from one PC to another.  You need to connect the serial ports together with a null modem cable.
    First, take a look at the example for serial communication.   In LabVIEW, go to the Help menu and select "Find Examples...".  From there you can search for "serial" or navigate to Hardware Input and Output >> Serial.  Select the "Basic Serial Write and Read.vi".  Experiment with that example to gain confidence on the serial communication methods.
    Next, it's time to learn about how to read and write files.  For that, the examples could be somewhat confusing since they all deal with files that are presumed to have data of a specific type in them.  I would recommend just getting familiar with the functions on the File I/O palette.  Specifically, get to know the following functions.
    Open/Create/Replace File - On your destination side, you'll need to create the copy of the file that you are trying to transfer
    Close File - When you are finished reading from or writing to a file, you should close it.  It cleans up the memory being used and finalizes any write operations that are still floating in the write buffer.
    Read From Binary File - The best way to read from a file when you do not really care what type of file it is.  In your case, you just want to get those bytes read and sent out so they can be written down at the destination.
    Write to Binary File - At the destination side, this is what will store those bytes to the file you created with number 1.
    Get File Size (under the Advanced File Functions sub-palette) - You need to know how big the file is so you know when you are finished.
    OK, so once you are able to create files, write bytes to them, and read bytes from existing files you can move on to transferring.
    The basic method I would suggest is to have the user specify a source file on the source PC and a destination folder on the destination PC.  Then, find out the size of the source file using number 5.  Divide that size number by the number of bytes you feel like transferring at once.  The serial buffers are usually around 32k (if I remember correctly) so do not exceed that.  Now begin sending data by reading some number of bytes and wiring that string output to the VISA Write function.  On the destination side, you'll want to be monitoring the serial port for bytes and reading them when they arrive.  Wire that string to the Write to Binary File function to add them to your destination file.
    That is the basic outline of how to do it.  You have to be careful not to overload the write and read buffers on the serial ports.  Initially you can use delays on the sending side to make sure the reading side has enough time to digest.  To get things moving faster, you can bring in some flow control.
    If all that sounds a bit intimidating, there are Alliance Member companies out there (such as PrimeTest Automation) who can write such code for you and even provide a turnkey solution for you.
    Happy wiring,
    Dan Press
    Certified LabVIEW Architect
    PrimeTest Automation

  • Is there an easy way to know if a vi within a LLB not being use by a Labview Application

    To All,
    I have developed a Labview application over a year that contains a number of LLBs.  There are significant number of VIs within those LLB files that were written but have not been called  by the application.  I am trying to optimize all LLB files to exclude those unused VIs.  Because there are many of them, the task to find out which Vi is being used and which one is not become very tedious.  First question: Is there a way to automate the process?  Second question: Does a compiled Labview application include all used and unused Vis from the LLBs in the .exe file?  I am very appreciate any inputs from this community.
    A Labview User  

    Ben wrote:
    In pre-LV 8 you could do a "Save with options..." and choose development distribution, single prompt preserve hiarchy and LV will pick-up all of the used VI's and plomp them down in a new location leaving all of the used behind as well as fixing up a of the linkages to point at the new location.
    In LV 8 and beyond you can create a Source Distribution in the project and acoomplish the same thing.
    In LabVIEW 8+, you can get something similar to the first option by selecting "save for previous" and then pick the existing version (yes, it's there!).
    LabVIEW Champion . Do more with less code and in less time .

  • PIC16F877A+UART for Display of Measurements LABVIEW

    I need to send four measurement parameters to the PC for display and storage purposes. The software for this aim is LABVIEW. I am new to PIC and Interfacing, but by putting so much effort and asking questions from experts, i could have accomplished the acquisition of all the data till today.
    I could also transmit a character "HELLO" through RS232 with my UART to USB converter and the result in hyperterminal was observed as well.
    I am quite happy that i could have reached up to this stage. but on the other hand, unfortunately my knowledge is absolutely poor about LABVIEW.
    I have heard that if i have control over the format of the data from PIC to LABVIEW, it is not that difficult.
    Please find the attached pictures of the design for better understanding.
    Questions:
    1- can you please explain what is exactly meant by format of data?(I also don't know the format of data i sent through USB)
    2- After specifiying the format, what would be the next stage?
    3- If it is possible, please provide me with some sample codes for Hi-tech C, and LABVIEW as well.
    Solved!
    Go to Solution.
    Attachments:
    PIC16F877A+UART for LABVIEW_page1_image1.png ‏587 KB
    PIC16F877A+UART for LABVIEW_page2_image1.jpg ‏72 KB
    PIC16F877A+UART for LABVIEW_page3_image1.jpg ‏71 KB

    void read_adc(void)                                                                 ////This function generates the average reading value of ADC
        unsigned short i;
        unsigned long result_temp=0;
        for(i=2000;i>0;i-=1)                                                            //looping 2000 times for getting average value
            ADGO = 1;                          //ADGO is the bit 2 of the ADCON0 register
            while(ADGO==1);                    //ADC start, ADGO=0 after finish ADC progress
            result=ADRESH;
            result=result<<8;                       //shift to left for 8 bit
            result=256*result|ADRESL;            //10 bit result from ADC
            result_temp+=result;
        result = result_temp/2000;            //getting average value
    unsigned short read_temp(void)                                                        ////This function stores the generated value by ADC into the variable "temp"
        unsigned short temp;
        temp=result;
        return temp;
    ==========================================================================================================
    //Since only 8 bits at a time can be sent with USART and the ADC value is 10 bits.
    //How to recombine the Lo and Hi 8-bit values to get 10-bit value?
    do {
    for (i=0; i <=7; i++) {
    myarray[i]=read_temp();
    for (i=0; i <=7; i++)  {
    putch (Lo(myarray[i]));               //send the lower 8 bits of ADC reading
    putch(Hi(myarray[i]));                 // Send upper 8 bits of ADC reading
    ===========================================================================
    Please let me know your feedback about this code?Is it sufficient for sending analog measurement values?
    do {
        USART_Write(255);
        an0 = ADC_Read(0) >> 2; 
        an0 = (an0 - 1);                                     / 1 is taken away from the value of ADC read, because if Voltage In is 5 volts ADC value
        USART_Write(an0);                                 / will be 255 and labview will mistake the data as the start byte. Data can read from 0 - 254.   
        an1 = (an1 - 1);
        an1 = ADC_Read(1) >> 2; 
        USART_Write(an1);       
        an2 = ADC_Read(2) >> 2; 
        an2 = (an2 - 1);
        USART_Write(an2);       
        an3 = ADC_Read(3) >> 2;
        an3 = (an3 - 1);
        USART_Write(an3);       
        an4 = ADC_Read(4) >> 2; 
        an4 = (an4 - 1);
        USART_Write(an4);        
    How about this?

  • How do I store front panel values on LabVIEW RT

    I have a program that auto launches on a PXI. Is there any way to store the front panel values, so that the program starts up again with the last values that were used? The ini file method will not work because I am using LabVIEW RT.
    Regards,
    S G
    Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor

    The best way to initialize inputs in RT is to use constants, or use the Communication Wizard in LabVIEW 7.0 to create a VI that initializes communication to the code running on the RT target. This becomes your user interface. One final suggestion is to use the Operate>>Make Current Values Default feature that is available in RT also.

Maybe you are looking for