Command of PGFP5 with Labview

I have a problem to configurate the PGFP5 programmer with Labview, I want send Hex File to PGFP5 with serial port by using the command lod with Labview, I receive this message response from the PGFP5:
lod
preparing storage ...... PASS
NOW loading.....
Aborted in line :16
I think that the command Visa Write From File don't terminate execution.
Any help?

Hi Bill,
it's not a solution.
It's a hint to not post the same question in several threads across the forum. We are all volunteers (atleast most of us) and we don't like to answer questions already answered in other posts. To prevent this situation a posted a link to your original question…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

Req any examples of how to use a USB midi controller/keyboards with Labview TIA

Req any examples of how to use a USB midi controller/keyboards with Labview TIA

Hi,
To access the MIDI ports you will need to call the Windows SDK. To send MIDI commands is relatively easy, here is an example that shows you how to send data to a MIDI controller or keyboard.
As far as input goes, this is the hard part. There are a series of functions that you need to call to open up the device, set some buffers and and possibly a callback to get notifications on the incoming data.
Reading MIDI data will not be an easy task, your best bet will be to implement this in a DLL and call that DLL in LabVIEW, there should be some code available o the web.
= "http://msdn.microsoft.com/library/default.asp?url=/library/en-us/multimed/htm/_win32_multimedia_... is a link to the Windows multimedia functions that you could use for MIDI input.
Let me know if you have any further questions.
Regards,
Juan Carlos
N.I.

Unload All Modules sometimes doesn't work with LabVIEW

TestStand's File >> Unload All Modules (and its RunState.Engine.UnloadAllModules() function) sometimes works and sometimes doesn't (with LabVIEW). When it doesn't, I have to quit LabVIEW to make TestStand unload LabVIEW VIs, otherwise I can't edit them.
Is there an "Unload All Modules" command that works all the time?

Hm, i assume that you have callbacks defined which do call those modules. Possible callbacks to look first are: SequenceFileLoad/Unload, FrontEndCallback.
Another possible reason is that there are components running in the LV RTE (runtime engine) calling into the VIs you try to debug/modify in the development environment.
Can you pinpoint the "lock" to specific sequences/modules? Do they lock only after specific sequences/modules have been executed?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

I have got a 1500 Kinetic Systems CAMAC crate and 3922 controller. I want to use it with LabView inst

alled in PCI-bus IBM PC, which does not have GPIB interface. Which way would be easier for developing my own instrument driver: a new GPIB controller + interface or 2915 Kinetic Sys. PCI-bus in-slot interface? Can the latter interface be used with LabView?
Many thanks.
Victor. I have got a 1500 Kinetic Systems CAMAC crate and 3932 controller. I want to use it with LabView installed in PCI-bus IBM PC, which does not have GPIB interface. Which way would be easier for developing my own instrument driver: a new GPIB controller + interface or 2915 Kinetic Sys. PCI-bus in-slot interface? Thanks

alled in PCI-bus IBM PC, which does not have GPIB interface. Which way would be easier for developing my own instrument driver: a new GPIB controller + interface or 2915 Kinetic Sys. PCI-bus in-slot interface? Can the latter interface be used with LabView?Victor,
I couldn't find an Instrument Driver for the 3932 crate controler. There is a driver for the 3988: http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/045f8392cc4d1b01862568ab005fbb49?OpenDocument
If you look at the driver it isn't too complex. Well ... actaully there are certain differences when using the 3988 GPIB controller that the driver takes care of that relate to correctly passing commands (FAN).
If the 3922 controller is similar then maybe you can use the 3988 driver and modify it to meet your needs. I'm not familar with the 2915 Kinetic system so I'm not sure what would be easier.
If you have a GPIB board, then you could try using the 3988 driver with your 3922 controller and see if you can modify the driver to get things to work.
I
've only used the 3988 and that was quite three years ago but it might be worth a try.
Best of luck,
Kamran - NI

SpaceX is looking for engineers with LabVIEW experience in Hawthorne CA (LA area)

SpaceX is looking for engineers with LabVIEW programming experience for our Launch group. Our responsibilities include:
Controlling launch pad equipment via PXI/LabVIEW
Commanding and monitoring our Falcon 1 and Falcon 9 rockets via a LabVIEW-based Vehicle control system
Commanding and monitoring our Dragon capsules via a LabVIEW-based Mission Operation system
Ocean recovery of Falcon 1 and Falcon 9 stages after liftoff and Dragon capsules after splashdown
Cargo configuration of Dragon capsules going to resupply the International Space Station
Maintenance of Mission Control Centers with the help of our IT department
With the exception of the launch pad equipment program, most of our LabVIEW programs do not interact with DAQ hardware (unusual, I know). The Vehicle control and Mission Operations software get their data via Ethernet from 'black boxes' that connect to NASA & Commercial RF ground stations. We also create several utility programs in LabVIEW that also don't interact with hardware. So, this is mostly a software gig, not a hardware/software gig.
Ideal candidates will have the following qualities:
CLD-level LabVIEW experience
A good understanding of basic computer networking (TCP/IP, UPD, firewalls, VPN)
Must be enthusiastic about space (What year did we land on the moon? How many men walked on the moon? How many Space Shuttles do we currently have? etc.)
Must be willing to travel. Common destinations include Houston (NASA Johnson Space Center), McGregor TX (test site), Cape Canaveral FL (launch site), Kwajalein Marshall Islands (launch site)
Must be able to work without supervision. We have a very flat management structure, no one will be telling you what you need to do. If you don’t know, ask. If you do know, get it done.
About the job:
Job is located in Hawthorne, CA in the Los Angeles area.
This is not a 9-5 job. There will be some late nights.
You won't be LabVIEW only. Everyone chips in as needed. Our group has done Javascript, C++, MATLAB, configuring of TELEX comm systems, cutting of metal with bandsaws, welding, Unigraphics CAD, etc. If we need it and you don't know it, grab a book and learn.
We are only hiring full time employees. Contractors need not apply.
To conform to U.S. Government space technology export regulations, SpaceX hires only U.S. citizens and U.S. Permanent Residents.
Apply at SpaceX.com. Click the Careers button and fill out the general application. Mention this posting in the cover letter field. Don’t reply to this forum. You need to go to SpaceX.com to get your information into our system.
Message Edited by Lavezza on 03-31-2010 03:59 PM

There is a job posting up now at SpaceX.com. Go to the careers tab and search for LabVIEW.
Look for the position called: Mission Control Software Engineers (LabVIEW).

Develop a command-line application using LabVIEW

Hi,
Is it possible to generate a command line(CLI) executable using LabVIEW? This CLI exe will be called with certain command line arguments by another application (written in Visual Basic). The LabVIEW Run time engine can be installed separately on the host PC.
Thanks for your help
Siddharth
Solved!
Go to Solution.

There is an example that ships with LabVIEW that shows how to read the command line arguements from an application. THe name of the VI is CommandLine.vi. It is extremely basic though. The power of command line arguements really comes from how you define and parse them. I recommend allowing your command line arguements to be order independent and that they require a label. For comand lines I prefer to use a single letter for the label. Full words are nice but then your command line gets very long. For the applications that we write we allow both the '/' (DOS/Windows style) and the '-' (Unix/Linux style) to designate a command line label.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Interface with LabView

I am a very new to LabView--
We are developing a board to interface with LabView devices- (ideally, the board would have a GPIB connector). We would like to use LabView to simulate various conditions on the Interface board by controlling switching (board MOSFETs) and then use a GPIB controlled multimeter to read voltages coming out of the Interface Board).
Since the Interface Board we are working on does not have an "address", is it possible to use LabView to communicate with it (send output signals to the board and read signals from it)? What is often done to have LabView controlled devices communicate with external circuitry ?
Thanks,
Alex

Alex00 wrote:
What would be an advantage of an interface controller (such as 4823) over a DAQ card (such as PCI-6013)? If we only need about 6-8 inputs (Digital I/O) and maybe about 6 Analog outputs, wouldnt the 6013 be sufficient to interface with our PCBA?
In your original post, you indicated that a GPIB interface would be ideal. ICS Electronics makes various models of controllers that provide a GPIB SCPI command interface to digital and or analog I/O. This controller can be placed inside the instrument rather than inside a PC and would use GPIB to connect (as you requested).
I have personal experience with the 4823, which can be used to control/monitor TTL devices on a byte-wise basis. Since you have digital and analog requirements, you could look at the ICS 4807 DAQ board. It may not have enough analog outputs though...
The only reason I originally responded was your GPIB requirement.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Interacting with labview with my own developed scritpting language.

Hi all,
I am Divya.
My aim :
I need to develop a programing language to interact with Labview such that the script should call labview front panel, execute the given task and front panel shold give back the result to the script.
I want to achieve this by using my own developed programing language (Valid reasons are there why not to use already exixting scripts which I dont want to discuss here as it is not relevant).
My idea :
As developing a new scripting language is a big task I am planning to start with Python scripting. I am trying to interact with labview using python script for now.
My problem :
As I am fresher to this field I dont know the possible ways to interact with Labview using python scripting. (Except using Labpython). If there is any way to achieve this please guide me on this.
Thanks in advance

Hi Dennis_Knutson
I am doing the same as the original question I have asked. As I have mentioned in my question I am starting off with a small addition (or any basic mathematical operation) function using Python script.
And yes the basic idea is to call Labview from script not the vice versa. To achieve this I need to pass the parameters from the python script to Labview and output from Labview to Python. For this purpose I am developing a small VI which vil take Python commands and carry on furthur operations.
I can explain with an example.
I have a command in python as sum=x+y. I want to take this command and send 'x' to a numeric control, 'y' to another numeric control and 'sum' to a numeric indicator and at the same time back to script. In between numeric controls 'x' and 'y' I need to carry out '+' operation. Say if the command is sum=x-y I need to carry out '-' operation(Where identifying '+' or '-' or any other operation is the job of labview).
I have developed a VI which can take the command from python and give it to Labview as a string. I need to know how to bifurcate that string to numeric controls, operands etc.

Can I programmatically control USB with LabVIEW?

I have a requirement to test a USB device. The test includes powering several of the devices off and on, i.e., power cycling for several hours. My plan is to accomplish by using a USB hub, breaking out the power circuit and running it through a relay inside of a DAQ. A neater solution would be to programmatically turn the USB device off and on. I know that the computer communicates with the device under test via USB and not the USB port itself. So I’m wondering if it’s possible with LabVIEW to accomplish this.
Thank you.

I'm not exactly sure what Eric was referring to as far as ActiveX. If it's with respect to the operating system, you're not going to find any ActiveX interface with the OS to do this. Unless he was referring to software programmability of the hub? Don't know.
With respect to power-cycling, a USB port can be disabled using OS calls. Thus, if you want to just turn off the whole hub you can disable the USB port that the hub is connected to. On Windows you can use a command-line utility called devcon to do this (search the forum as this has been mentioned before). The limitation is that devcon is not redistributable. This means that you cannot include it if you're giving this software to a customer. If, on the other hand you need to selective turn off the ports on the hub (i.e., to test individual devices), then you'd have to go back to the manufacturer of the hub and find out if they have a software interface to do this. Otherwise, it's the external power on/off approach via a relay or via a regulator as suggested by SnowMule.
EDIT: Additional caveat: devcon may not work under Windows 7. You did not indicate what operating system you're using. However, the OS calls that devcon makes are still there.

Warner/superior electric's SS2000PCi motion controller interfacing with LabVIEW 6i

Sir,
In our application, we are controlling the movement of X-Y arm on the X-Y table. For this we are using superior electric products:
(a) Slo-Syn SS2000PCi Programmable Step Motor Controller
(b) MD808 Motor Drive
We are using two such controllers and motor drives to drive two 2 Amps Sanyo Denki Stepper motors: one each along X-axis and Y-axis. Along with the arm movement a data acquisition also has to be carried out. So, the motion control and Data Acquisition has to be synchronized by means of software. The problem now is to program the controller. Though MCPI Version 4.41 is there, we want to program the controller in LabVIEW 6i so that we can synch
ronize both motion control and Data Acquisition.There is no driver which is compatible to LabVIEW 6i.
Is there any 32-bit DLLs for this controller? If any one has these dll's please let me know. My E-mail ID: [email protected]
So that i can call these DLLs in LabVIEW 6i and program it.Or else send me at least the detailed low level command sets of the controller in pdf format so that i can develop our own drivers.
Regards,
Nagendra

Nagendra,
Unfortunately, I was unable to find any helpful resources for you based on a cursory web search. I recommend that you contact the manufacturer of the hardware and ask them if they have a driver (DLL) that you can use to interface with LabVIEW.
Good luck with your application, and have a good day.
Sincerely,
Darren N.
NI Applications Engineer
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

How to compile COM 1 data with LabVIEW?

I have a device connected to my COM 1 port. How do I input data with that into labVIEW? The program that comes with it is really elementary, it only shows me the data that the comes straight from the device, no analysis. Its like labVIEW and MAX dont recognize the device, but my device manager says its connected and works fine. How do i input that data and compile it with labVIEW?

Much better
MAX will not detect instruments connected to a com port. The reason is that there is no standard for serial instruments (unlike GPIB). You should only have your com port listed in MAX. If the instrument is listed in your device manager, then it sounds like the driver you got with the instrument is a little weird. It may be that the driver software has taken control over one of your serial ports. Normally, all you would have to do is use the serial functions on the Instrument I/O palette. However, if the instrument driver has taken control of the com port, you won't be able to do this because the OS will only allow one process access to the port at any one time. You can test this by trying to open a Hyperterminal session to the com port. If you can an error indicating that the port is in use, then that's the driver running in the background. You can uninstall the driver and everything should be okay. You could also try to use the driver as provided. I'm assuming it's a DLL. You could call the functions in the DLL with the LabVIEW Call Library Node function. You will need documentation from the vendor on the DLL in order for this to be done. It's probably simpler, though, just to use the LabVIEW serial functions. You would still need the command set/syntac from the instrument manufacturer in order to communicate with it.

How can I control PIC programmer with LabVIEW

I need to control a PIC Programmer (MPLAB PM3) with LabVIEW. How to do this?

Hi Paul.
I am working on a project that is using LabVIEW to communicate via serial communication with 4 programmers (Com 1, 2, 3, & 4). I am currently using the Microchip PM3 programmer DOS utility PM3CMD.exe to send/receive commands from the system exec.vi in LabVIEW. I am attempting to program simultaneously with 4 programmers, but the PM3 programmers are returning a database error if I try and communicate with more-than 2 programmers at a time. I noticed that you have some experience with some drivers from Microchip and using serial commands.
Do you have any suggestions that may help me.
Thanks.

Accessing to Smart Card Readers PC/SC with Labview

Accessing to Smart Card Readers using Labview
This program is an example that how access to Smart Card Readers (PC/SC) to get some information about a SIM Card, this program is not debuged yet and have some issues.
The point is wear the winscard.dll where all the function to access to this PC/SC readers are defined, I don´t have enought skills as programmer, but I think that it could be help somebody to develope
applications with Labview and SIM cards (GSM, USIM, etc..)
Regards
Attachments:
GETTING_ATR_FROM_SIM_CARD_GSM.vi ‏118 KB

Hello!
Let me first understand your question, Do you want to know wich of 22 DLL´s, that you have, can you use to sent an AT command to retrive the MSISDN on SIM Card?
If you answer is yes, you should be identify all the functions in your dll and found wich of them ara used to sent AT commands like SMS send, SMS retrive, etc.., the same structure of this commands you can use to send another AT Command.
The number should be record on the SIM Card.
AT+CNUM Subscriber Number
Description:
This command returns the MSISDNs related to the subscriber (this information can be
stored in the SIM or in the ME). If subscriber has different MSISDN for different services,
each MSISDN is returned in a separate line.
Test if the command
is supported
AT+CNUM=?
Best Regards.
Enrique Ramos
Telcel Mexico

How can I access CAPI 2.0 methods with LabView ?

I must use CAPI 2.0 (common ISDN interface) method with LabView (graphical interface), the work is to command a ISDN S/T card on PXI Bus, and this card support CAPI 2.0.

This depends upon what type of interface you have to the ISDN. I assume you have either Basic Rate Interface (BRI) or Primary Rate Interface (PRI). Do you have a DLL to control it? If so, you can use the "Call Library Function Node" VI to access this DLL and just make calls to it. If you have an ActiveX Server, you can use the LabVIEW ActiveX Automation VIs to access it.
J.R. Allen

Integrating TortoiseSVN with LabVIEW's Compare tool

I’m trying to set up the TortoiseSVN Diff tool, as described:
https://decibel.ni.com/content/docs/DOC-12175 and
http://digital.ni.com/public.nsf/allkb/3BEC521972301FF2862576EA00609CA6
To configure TortoiseSVN to use LabVIEW’s compare tool I added the following for “.vi” file extensions:
"C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %mine %base -nobdcosm –nobdpos
The links above tell you use “Program Files,” but on my system the LVCompare.exe is located in my “Program Files (x86)” directory.
When I try to run the diff tool (right click on the file in question -> TortoiseSVN -> Diff with previous version), I get the following error:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Any help getting the LVCompare tool integrated with TortoiseSVN to work would be greatly appreciated!
Thanks!
Lauren

Lauren_CPC wrote:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Yes it does. LVCompare is only a simple wrapper executable that eventually tries to run a VI in the LabVIEW installation directory. And this VI will not work if the LabVIEW installation is not licensed as Professional Development system.
Note to the AEs: In the second link of Laura's post, it states incorrectly: Primary Software: LabVIEW Development Systems>>LabVIEW Base Package
This is completely contradictory to the note in the last link, that states that the Professional Development System is required. A documentation correction request seems in order.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Command of PGFP5 with Labview

Similar Messages

Maybe you are looking for