Real Time deployment

Hi SAP Experts,
I would like to understand more details on real-time deployment functionality of deployment. Does real time deployment works for multi-level location scenarios ?
As I understand the real time deployment first runs the SNP heuristics to consider the latest demand supply situation but does it run the heuristics for the entire network for that product or only look at the location connected one level up from the supply location ?
Example:  I have a Markets A, B and C which are connected to in-stock locations X, Y and Z which send the net requirements to the plants A B C.
My supply chain is plant 1, 2, 3 are connected to stock locations X, Y and Z and which in turn are supplying to each markets A, B and C.
If I want to run the real time deployment using supplying plants 1,2 and 3  
  the real time deployment will only deploy receipts to in stock locations X, Y and Z (which is one level up from the plants) or
  Will I see the deployment results at markets A B and C (all through the network upto the markets)
  Does it looks at low level codes in the network while running the heuristics for the product.
Real time deployment at supply locations only look at in stock locations Z, Y Z or when it runs the heuristics it actually runs the heuristics at the market locations A, B C to update all the net requirements at X, Y, Z and then run heuristics at X, Y, Z to calculate net requirements for plants 1, 2, 3 and the deploy in reverse order up the way to markets from supply plants. Does it looks at low level codes in the network while running the heuristics for the product.
Thanks and regards,
Amit

Hi Amit,
Like you i am also exploring real time deployment.
As far as i have understood , real time deployment will run a heursitic between the source and destination location(if specified in SNP02 ) or run heuristic on all t-lane connections between source and all possible destination locations (if dest loc not specified in SNP02) & then take the normal deployment run.
This will be valid for scenarios wherein you want to consider destination locations demand arriving after the last SNP run.
Hope this helps.
Do come back with your testing results.
Regards,
Vinay

Similar Messages

  • CompactRIO Real-Time Deployment Requirements

    Hello, I have a few questions regarding the requirement of NI's Real-Time Deployment Option and a cRIO.  I have multiple licenses of LabVIEW 2009, some with the Real-Time option and some without.  That being said, I am wondering what functionality will be missing from the machines that do not have the Real-Time option installed on them.  I borrowed a cRIO from someone and was able to read a voltage from the cRIO without having the Real-Time Deployment, so I am not sure what I am missing regarding functionality and not having Real-Time Deployment installed.  Any information on the subject would be greatly appreciated.  Thank you.
    Michael 

    MSATLAB,
    I see three pieces of software potentially involved:
    1) LabVIEW
    2) LabVIEW Real-Time Module
    3) LabVIEW FPGA Module
    With just LabVIEW, you can deploy a prebuilt bitfile to the FPGA and communicate with that bitfile.  You only need the NI-RIO driver.  (In order to built bitfiles, you need the FPGA module.)  However, without the Real-Time module you won't be able to communicate with the controller portion at all.
    With LabVIEW and the Real-Time module, you can interact with the controller and multiple hardware cards.  If you don't have the FPGA module (to build a bitfile), you can use the Scan Mode interface to the FPGA.  With the Real-Time module, you can also deploy network shared variables to the controller itself.  (Once they're deployed, they stay deployed until you specifically undeploy them or format the controller.)
    An ideal setup perhaps for you would be to do the following:
    On a computer with LabVIEW, the Real-Time module, and the FPGA module, create a startup executable (for the controller), create a bitfile (for the FPGA), and deploy network shared variables (to the controller) that can be read from LabVIEW on any other computer.  Without knowing more about how your cRIO was configured beforehand, it's hard to tell how you got a valid voltage reading.  It's possible that you used the process I outlined here.
    Kevin S.
    Applications Engineer
    National Instruments

  • Real time deployment problems

    Im some having problems deploying my realtime applictation to my RT target.  Im unsing Labview 8.6 in windows and Real time 8.6.1 on an PXI-8110 target.
    When I first deploy the VI after the RT target boots,  The following error appears on the target screen:
    Error loading 'ws2_32.dll':missing export 'RegNotifyChangeKeyValue' from 'ADVAPI32.DLL'
    If I then try running it again, it will work fine without the error, deploys fine and the program runs fine.  Ive been ignoring this problem thoughout the development of this program because I just get the error the first time deploying it after the target boots. 
    Now that my program is finished im trying to deploy it as a built application and set it to run on the RT controller at startup.  The program builds fine with no errors.  When I try to deploy it to the target, it fails to deploy.  There is no explanation in the error, it justs says that it failed to deploy. 
    If I then go into the project explorer, right click on the main VI that the application is built with, select deploy, It deploys without error. after i do that, the realtime application I built will deploy without error.  However it will not run a startup, the controller boots, states it is loading the startup realtime application, then does nothing. Im wondering if the dll error before is related to it.
    Another note, I had this program running fine and deploying fine a few months ago with Labview 8.5 and Realtime 8.5 on a PXI 8106 controller.  These errors started popping up when I upgraded to RT 8.6.1 and labview 8.6.  I have tried formatting the controller and reinstalling everything but I get the same error.

    Mike-
    Take a look at the KnowledgeBase 3UJACBE9: FTP Transfer of Files between Host and Real-Time Targets in MAX.  As far as exactly what you will need on your PXI-8110 for your project, that can’t be defined on generalities.  These controllers are used for so many different applications, modules, toolkits, and different combinations of hardware, it would be impossible for National Instruments to say this is the perfect setup for everyone. 
    ADVAPI32.dll is a System32 dll as described in this forum.  I would suggest taking a look at that thread for more of an explanation. 
    Regards,
    Mike S
    NI AE

  • Pxi 1042 configuration for Real-Time

    I have purchased
    PXI-1042
    controller 8187
    one module for data capturing.
    I want to configure the said pxi for Real-Time purposes,
    so what steps should I follow?
    thanks
    Abbas
    Solved!
    Go to Solution.

    The Real-Time Deployment License is different from the LabVIEW RT module.
    When you purchase a PXI controller, part of what you are buying is the operating system that is installed on it.  If you purchased the controller with Windows on it then you purchased the copy of Windows that came with it.  Now that you want to put the real-time operating system on it, you need to purchase the license for it.
    But that's all legal stuff.
    And you are correct that there is a copy of the RTOS on the controller.  But if your controller has its disk formatted as NTFS you will not be able to use it.   The RTOS requires that the hard drive be FAT32. 
    If your controller is FAT32 then you can boot into BIOS (hit delete while booting), and select Real-Time in the Boot Configuration to make your controller boot into Real-Time.
    If you controller is not FAT32 then you will need to format the controller first, using the disks I have previously mentioned.
    Please let me know if you have any questions.
    Justin Parker
    National Instruments
    Product Support Engineer

  • NI LabVIEW Real-Time for Desktop PCs compatibility!

    Hello,
    I'm pretending to acquire the NI LabVIEW Real-Time Deployment License for Desktop PCs. But before that, I need to be sure that this will work with other boards (not from NI).  
    Currently, I still don´t have all the project details. But there's a possibility of one board be from other supplier. 
    Can anyone tell me this, please. It's very urgent.
    Best regards,
    Paulo Carmo

    Hi Paulo,
    I guess that you will be disappointed but the response is clearly no.
    When you boot a Desktop PC as RT target, it loads with the basic real-time operating system (including drivers for ethernet, for harddrive, memory....). When you want to add drivers on this embedded system, it will be only possible to add National Instruments drivers such as DAQmx, DAQ, VISA ... The possibility to add others drivers (from others providers) is not supported.
    Hope it will help you,
    Regards
    David D. - Application Engineer - NI France

  • Hypervisor: Create Standalone Real-Time Application (Error at deploying: File not found)

    Hello,
    I am using Hypservisor. With "Build Specifications" in the project explore I want to create a standalone real-time application.
    In my first try I only want to print some texts onto the real-time console (HyperTerminal) using the function "RT Debug String.vi". I built the real-time application successfully and got the rtexe-file locally on the windows system. But as I tried to deploy the application to the target system, I got the error: "File not found". Please check the attached file "error.txt" for details.
    I don't understand which file is not found. Or I used "\" as path separators. Is it wrong? I'd appreciate if you'd have any idea of the problem. Thank you very much.
    Regards,
    Scarletice
    Solved!
    Go to Solution.
    Attachments:
    ERROR.txt ‏1 KB
    builds.zip ‏153 KB

    Hello Casey,
    Thank you very much for your reply and your interest in our project. We are using Real-Time Hypervisor for the setup of our test stand. We use the Windows system to show the GUI and the Real-Time system for the real-time machine control and online data storage. We use shared variables and shared memory for the data exchange between the two systems.
    The system works generally quite fine now. But we still have to face new problems at each step forwards. I'm sure, I'll have more questions. I'd appreciate your advices. Thanks sincerely.
    Best regards,
    Scarletice

  • Error -1074384569; NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your database to the real-time system.

    Hello
    I have a VeriStand-Project (VSP) created with my Laptop-Host (LTH) which works with my PXI, while
    deploying it from my LTH. Then I have installed the whole NI enviroment for PXI and VeriStand use on a
    industrial PC (iPC). I have tried to deploy my VSP from the iPC to the PXI but the following error
    message arose on my iPC:
    The VeriStand Gateway encountered an error while deploying the System Definition file.
    Details: Error -1074384569 occurred at Project Window.lvlibroject Window.vi >> Project
    Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
    Possible reason(s):
    NI-XNET:  (Hex 0xBFF63147) The database information on the real-time system has been created with an
    older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your
    database to the real-time system. ========================= NI VeriStand:  NI VeriStand
    Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI
    VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize
    Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * • Unloading System
    Definition file... • Connection with target Controller has been lost.
    The software versions of the NI products (MAX/My System/Software) between my LTH and the iPC are
    almost the same. The only differences are:
    1. LabView Run-Time 2009 SP1 (64-bit); is installed on LTH but missing on iPC. The iPC has a 32-bit system.
    2. LabView Run-Time 2012 f3; is installed on LTH but missing on iPC.
    3. NI-DAQmx ADE Support 9.3.5; something strage on the LTH, because normally I am using NI-DAQmx 9.5.5 and all other DAQmx products on my LTH are 9.5.5. That means NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5.. On the iPC side all three products are 9.5.5.. That means NI-DAQmx ADE Support 9.5.5, NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5..
    4. Traditional NI-DAQ 7.4.4; The iPC has this SW installed. On the LTH this SW is missing.
    In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
    1. LabVIEW Real-Time 11.0.1
    2. NI-488.2 RT 3.0.0
    3. NI_CAN 2.7.3
    Unfortunately the above stated problem still arose.
    What can I do to fix this problem?
    I found a hint on http://www.labviewforum.de/Thread-XNET-CAN-die-ersten-Gehversuche.
    There it is written to deploy the dbc file againt.
    If this is a good hint, so how do I deploy a dbc file?
    I would feel very pleased if somebody could help me! :-)
    Best regards
    Lukas Nowak

    Hi Lukas,
    I think the problem is caused by differenet drivers for the CAN communication.
    NI provides two driver for CAN: NI-CAN and NI-XNET.
    NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
    You wrote:
    In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
    3. NI_CAN 2.7.3
    NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
    Regards, stephan

  • HOW CAN I ACQUIRE AND DEPLOY DATA IN REAL TIME WITH DAQ 6024E?

    HI ENGINEER,
    I'M PROGRAMING AN APLICATION WHICH I NEED ACUIRING AND DEPLOYING AN ANALOGOUS SIGNAL IN REAL TIME.
    I HAVE:
    LabVIEW 7.0
    WINDOWS 2000
    DAQ CARD 6024E
    THE SIGNAL I WANT TO ACQUIRE IS 0-10 Vcd FROM A SENSOR, THE PROBLEM I HAVE, IS THAT I AM ACQUIERING THE DATA AND IT SEEM THAT THEY ARE UPDATING EACH SECOND, BUT I HAVE BEEN MOVING THE PARAMETERS SUCH AS TASK TIMING IN THE DAQ ASSISTANT VI AND NOTHING HAPPENS.
    CAN YOU TELL ME WHICH PARAMETERS I HAVE TO MOVE TO AQUIRE AND DEPLOY DATA IN REAL TIME

    Hi barron,
    If you want to see the data update quicker, you can decrease the value in the "Samples to Read" field of your DAQ Assistant. This number controls when data is transferred from the DAQ buffer to the PC. If the sampling frequency remains the same, but this field decreases, it means the buffered data will be returned more quickly.
    Hope this helps.
    Thanks,
    Lesley Y.

  • Trouble with deploying models in NI Veristand to real-time target

    Hi All,
      I desperately need some help with some application i’m working on. I’m trying to read some accelerometer measurements into NI Veristand but coming up with an error all the time during the deployment stage to the real target which i have atttached. I can’t quite figure out what to do about it. I’m using a real-time device with a PXI-4461 module. I have checked that i can read all sensor measurements in MAX as attached. The error message is as follows:
      Initializing deployment...
    Waiting for the target to report its state...
    Initiating FTP connection...
    System Definition File -> Acquisition.in4
    Restarting system...
    Restarting target into run mode...
    The target encountered an error and reset. Verify that the system definition file and the target resources are valid. You must deploy a new system definition file or reboot the controller to correct this problem.
      Error -200757 occurred at DAQmx Start Task.vi:1
      Possible reason(s):
    Measurements: Sample Timing Type is set to On Demand which is not supported for analog input on this device.
    Set Sample Timing Type to Sample Clock. You can achieve this whlie setting related properties through DAQmx VIs or functions for configuring timing.
    Task Name: Dev6_AI

    Duplicate Post.

  • Having trouble with deploying real time 8.0 vi's

    Having trouble deploying a simple vi to my field point platform.  I am using  FP OS v10.4 and labview rt v8.0.  MAX tells me software installations to the target are good and communication in MAX is good.  I can make a windows VI to read a channel on  my field point and it works well. if I duplicate this VI in real time and try to deploy it to the field point unit, it goes well until it starts to download the "FP read" vi and then the download fails.  I have plenty of memory on the fieldpoint unit for this vi - it consists of a FP channel constant, FP read, numeric constant (for data type to FP read), a numeric indicator, a while loop, millisecond multiple vi (loop timing), and stop control.
    I am stumped - any help would be great.
    Kirk

    Kirk - what controller are you using?  Double check that the
    controller has the following listed under Remote Systems >> (your
    controller name) >> Software:
    LabVIEW Real-Time 8.0
    NI-VISA
    FieldPoint VI Manager
    FieldPoint Drivers 5.0
    sebk1 - The Fieldpoint Read VI includes error handling, if an error
    occurs it takes time to generate and propagate the error.  Check
    to see if your data is out of range for the channel.  If that is
    not the case, I suggest trying an example VI that includes a FP Read VI
    such as Analog Input found at: C:\Program Files\National
    Instruments\LabVIEW 8.0\examples\FieldPoint\Getting Started\Analog
    Input.vi if you installed to the default directory.  I'd be
    interested to hear the results of your tests.
    Regards,
    Micaela N
    National Instruments

  • Difference entre Deployment License for Standard PC's- ETS RTOS et LabVIEW Real-Time Debug Deployment License

    Premier question j'ai develloper suite 2009 SP1.Avec a été fourni le Deployment License for Standard PC's- ETS RTOS sauf que c'est la version Labview Real Time 8.2 Pourquoi ce n'est pas 2009 SP1 ?
    Et la deuxieme question est : qu'est ce que LabVIEW Real-Time Debug Deployment License ?
    Merci

    Bonjour Lunik,
    Merci d'avoir posté sur le forum National Instruments.
    Il n'est en effet pas normal que vous ayez la version 8.2 du module RT si vous possédez la version de Developper Suite 2010 (qui inclus LabVIEW 2009 SP1). Si vous parlez bien du module LabVIEW RT, vous ne pouvez avoir une version antérieure que celle fournie avec la suite.
    Si vous aviez une ancienne version installé, je vous conseille, si ce n'est pas le cas, d'installer tous les modules dont vous avez besoin depuis les disques d'installation de la Developper Suite.
    Pour votre deuxième question, je vous renvois à cette page : ici.
    Ce logiciel permet de déployer une licence pour faire d'un PC une cible RT.
    Cordialement,
    Romain P.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

  • How to download an FPGA vi along with a real time application

    Hello
    I am targeting cRIO 9012, cRIO 9102. I downloaded the FPGA vi on flash memory and then built a real time application and set it as startup.  But there was no signals on the modules IOs which are handled by FPGA vi.
    Also the shared variables of that application when running as standalone aren't accessible. Please provide me the steps that should be followed to access the shared variables of a standalone real time system. Please help me resolve these problems.
    Best Regards
    Mani

    Hi Mani,
    What modules do you have?  What kinds of signals are you measuring?
    Have you deployed your shared variable library on your host PC?
    Regards,
    Jeremy_B
    Applications Engineer
    National Instruments

  • How to install the NI-DAQmx driver on a real time target PC?

    Hi, I’m painful about how I can install a PCI-6363 DAQmx on my real time desktop PC target. The PCI-6363 is directly connected to the real time PC. And I’m using LabVIEW 2011 and MAX 5.0. 
    The DAQmx device driver can be seen in software lIst in the host PC, but it can not be found in the install wizard. Is there something wrong with my host PC? or is that wrong to connect PCI-6363 with real time desktop PC?
    I would be grateful for any advice that I could get here.
    Solved!
    Go to Solution.

    Hi Zhleo,
    If you are about to use the PCI-6363 with the Real-Time Desktop you are right you need to have it installed, and then you need to deploy DAQmx driver software to the real-time target.
    To do that you access your real-time desktop under Remote Systems in MAX and start the Real-Time Software Wizard. There you should see DAQmx listed. 
    In case you do not have DAQmx listed there, see this KB: Deploying DAQmx to a Real-Time Controller or PC?
    Regards,
    Eirikur Runarsson
    Platinum Applications Engineer
    NI Denmark

  • How to create a Real Time Interactive Business Intelligence Solution in SharePoint 2013

    Hi Experts,
    I was recently given the below requirements to architect/implement a business intelligence solution that deals with instant/real data modifications in data sources. After going through many articles, e-books, expert blogs, I am still unable to piece the
    right information to design an effective solution to my problem. Also, client is ready to invest in the best 
    infrastructure in order to achieve all the below requirements but yet it seems like a sword of Damocles that hangs around my neck in every direction I go.
    Requirements
    1) Reports must be created against many-to-many table relationships and against multiple data sources(SP Lists, SQL Server Custom Databases, External Databases).
    2) The Report and Dashboard pages should refresh/reflect with real time data immediately as and when changes are made to the data sources.
    3) The Reports should be cross-browser compatible(must work in google chrome, safari, firefox and IE), cross-platform(MAC, Android, Linux, Windows) and cross-device compatible(Tabs, Laptops &
    Mobiles).
    4) Client is Branding/UI conscious and wants the reports to look animated and pixel perfect similar to what's possible to create today in Excel 2013.
    5) The reports must be interactive, parameterized, slice able, must load fast and have the ability to drill down or expand.
    6) Client wants to leverage the Web Content Management, Document Management, Workflow abilities & other features of SharePoint with key focus being on the reporting solution.
    7) Client wants the reports to be scalable, durable, secure and other standard needs.
    Is SharePoint 2013 Business Intelligence a good candidate? I see the below limitations with the Product to achieve all the above requirements.
    a) Cannot use Power Pivot with Excel deployed to SharePoint as the minimum granularity of refresh schedule is Daily. This violates Requirement 1.
    b) Excel Services, Performance Point or Power View works as in-memory representation mode. This violates Requirement 1 and 2.
    b) SSRS does not render the reports as stated above in requirement 3 and 4. The report rendering on the page is very slow for sample data itself. This violates Requirement 6 and 7.
    Has someone been able to achieve all of the above requirements using SharePoint 2013 platform or any other platform. Please let me know the best possible solution. If possible, redirect me to whitepapers, articles, material that will help me design a effective
    solution. Eagerly looking forward to hear from you experts!.
    Please feel free to write in case you have any comments/clarifications.
    Thanks, 
    Bhargav

    Hi Experts,
    Request your valuable inputs and support on achieving the above requirements.
    Looking forward for your responses.
    Thanks,
    Bhargav

  • Real-Time Application doesn't run; source code works fine

    The short version is I'm programming a cRIO and apparently the RT code isn't running after being deployed and I can't figure out why. This is further complicated that I'm doing all this remotely and I don't have direct access to the unit since I'm 500 miles away. I'm working through a couple of other guys who know some LabVIEW, but neither works at the site so they have to explicitely travel out there every time I have a bright idea.
    I was out there a few weeks ago. During this time I created a simple cRIO code, since I'm new to cRIO, that allowed the user to move a control and change a graph. It worked fine, but I should note it did not have an FPGA component. After that I worked on the real code, which reads some sensors, displays the results on a UI and logs the results. This did have FPGA. I used it in the LabVIEW environment and it worked fine, but I ran out of time before I could complete a release version and deploy the RT as a compiled application. I sent them the release version later, my contact deployed it but got network stream errors when running the UI.
    After hours of looking at network problems and sending over debug versions, I tried creating a log on the RT level so I could see what was going on. The log doesn't even open, even if it's the first command in the code. I pored through the forums and found http://forums.ni.com/t5/LabVIEW/cRIO-Troubleshooting-creation-and-deployment-of-startup/td-p/1956475... which took me in a new direction.
    I had my contact use the RT debug console and when he pulls up the RT front panel, it shows a broken run arrow. He clicks it and nothing happens -- no running, no bug list. If he pulls up the bug list manually, it's empty. Again the RT works fine if you run it through LabVIEW and not as a compiled real-time application. He also noticed that the Open FPGA VI was grayed out on the block diagram. No other icons are.
    So the problem appears to be that the compiled RT application is getting some kind of error but not telling me what it is, and it seems to be related to opening the FPGA. I've recompiled the FPGA and RT. I've had him recompile the RT himself, but not the FPGA because it would take hours. He's downloading everything correctly to the cRIO. The RT is set to run automatically. He's rebooting the cRIO every time he deploys the RT. They have LabVIEW on a computer there but it doesn't have the right drivers to run the code from the LV environment. I'm resisting having them install the dirvers because downloading big files is complicated there due to security restrictions and a lousy network connection at a remote site. Besides that doesn't solve the problem of the RT executable not running the same as the source code, which according to the thread above appears to be a thing.
    The latest thing I'm trying is that I sent him instructions for how to build a source distribution from the project I sent and try deploying that to the cRIO. Even if that works I'm not sure that's an acceptable solution because I assume running the VI rather than the EXE is slower, and they need speed on this project.
    I simply have no idea where to go from here. I probably need to get direct acess to the cRIO and I might be able to convince them to ship it to me so I can figure this out, but I'm not sure where I'd even start other than the standard voodoo debugging of "try stuff at random until something works". I'm open to suggestions if anyone has managed to solve this before.
    Code snippet of the first part of the project is attached, though I'm not sure how much good it will do. I'm really stumped and the client is getting frustrated with how much of the budget is going to fix this.
    Solved!
    Go to Solution.
    Attachments:
    RTMainSnippet.png ‏623 KB

    Have you checked the cRIO error log? Usually I'd access it through the LabVIEW project (right-click on the target, don't remember the exact menu options and I don't have the RT toolkit installed on this machine to check), but it must be stored somewhere on the cRIO as well, although I don't know if it's in a human-readable format.
    Which cRIO are you using? What exactly do you mean by "debug console"? (This may be related to the cRIO - the newer ones have video out, although I don't know if that's what you're referring to.) With a broken run arrow, you won't get an error list unless you're running in the development environment.
    Have you confirmed that the software installed on the cRIO matches the version you're using for development, including patch level? Get someone to connect to the cRIO with Measurement and Automation Explorer, and get a list of the software installed on the cRIO.
    Sounds like the ability to connect with a remote debugger would be helpful here, if you can get the right drivers installed on the machine with LabVIEW that's connected to the cRIO. Make sure all driver versions match what you're using. Any chance you could then do a remote desktop connection from your work site to the remote LabVIEW machine?

Maybe you are looking for