Error 1074384569 in NI Veristand Custom device while deplying code.

Similar Questions

• Using Set cursor busy Page Veristand Custom device

  I write a device custom in Veristand and tried to use the value busy vi to disable the cursor while I do some tasks on a page of System Explorer.  It seems that the game and vi Unset busy do not work within the environment of System Explorer.  I see that NEITHER offers a way to release the cursor with the Veristand API but I don't see a way to put well filled with the API.

  Am I right in saying these cursor screws do not work the way they would in a normal application? Or is there a work around here that I'm missing?

  Hello

  The idea is good, it works for me, if you open a reference to System Explorer.lvlibystem Explorer.vi (VeriStand 2012):

  

  Best regards

• VeriStand "Custom Device" creation, including the different types of sources of code for simulation only

  Hello

  Before I ask my questions, I want to describe my problem:

  I would use VeriStand on a PXI system for simulation only. The simulation includes different types of sources such as Maltlab-Simulink-models, MultiSim SPICE models and code LabView for FPGAS-programming. Simulink models are available as a dll-file, generated with 'Real-Time-Workshop' and 'Simulation tool Kid. " They need to generate heavy duty, calculated by the modulation of the vector space and model the performance of a special converter. The MultiSim model will be transformed via a special VI in LabView code. I can generate code VeriStand (--> NI VeriStand--> Generate tools...). The PWM duty cycles of this dll matlab above are for LabView FPGA code entry. This will be the entrance of the gate of the tansistors of the MultiSim-model. Means, space vector modulation generates tension of the door and get the FPGA code to the ports of the inverter model.

  I am new in programming with VeriStand and LabView. I don't know how I can handle this. But NEITHER says it's possible. So my questions are:

  Is it possible to use VeriStand with more than one device Costum and simulate as a whole simulation. How can I associate different files.

  If this isn't the case, that I have to build a LabView Vi, where all the different sources of models are included.

  Is a walkthough or a user guide available, that I can use to fix my problems.

  I hope you can help out me. I need it for my bachelor thesis very fast. Thank you for your attention.

  Best regards Andre

  Here is a document describing how to create compiled LabVIEW templates and import them into NI VeriStand:

  http://www.NI.com/white-paper/12785/en

  The following link is a more general page describing several model and their support environments in NI VeriStand:

  http://zone.NI.com/DevZone/CDA/EPD/p/ID/6488

  Some additional modeling environments are supported, but not necessarily listed here since this is a growing list.  In addition, since NEITHER created a strategy of open model interface called NI VeriStand model framework, it would be possible to connect new types of sources of model in NI VeriStand without too much work.  Then the mapping tool, you found, makes the magic of easily to configure the connections of logical data between models.  You can also easily transfer each model to the individual processor cores, which contributes to the speed of calculation for system-level simulations.

• Best way to pass the name of the e/s DAQmx channel Veristand 2011 Custom Device?

  I'm building a custom device that will run a DAQmx task on the target of RT.

  I use VS2011 and alsoSimple custom device tool, which, at this point I'm not sure if it can work under VS2011...

  I created the fine libraries and custom device (a PWM input called InputPWM) has added to the Explorer from the system.  Running it returns the following error when I deploy:

  -----------

  LabVIEW: Type VI reference is not part of connector of VI.
  =========================
  NEITHER VeriStand: Open VI reference in Custom Devices Storage.lvlib-> pen device reference (Interface HW) .vi-> Custom Devices Storage.lvlib:Initialize Device (Interface HW) .vi OR VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi-> NI VeriStand Engine.lvlib:VeriStand Machine.vi engine-> Engine.vi NI VeriStand Engine.lvlib:VeriStand-> NI VeriStand Engine.lvlib:VeriStand .vi engine Wrapper (RT)
  c:\NI-rt\VeriStand\Custom Devices\InputPWM\InputPWM Engine.llb\InputPWM RT pilot VI.vi

  ----------------------

  On the console, it says that the error is 1026, LabVIEW: Refernece VI is not valid.

  I suspect that a potential problem is that I used a DAQmx e/s in the Configuration.ctl and the InputPWM RT pilot VI.vi in the framework can not deal with this type. So my questions:

  -What is the easiest way to pass the names of e/s to the custom device? For a quick test, I could go to hard code, but a more generic solution would also. Should be based on the address for the e/s MAX? Do I have to create the ctr under the DAQ hardware in VS?

  - or said by the way, is there a way to review these screw frame to see where the questions is, as you would with LV - RT?

  THX.

  L.

  If you use the tool of easy custom device, just put everything you need inside the cluster configuration data and these data will be in the home page of the custom (for the user to set) device and be available at runtime in the RT device custom code.

  You could have them type the name of the DAQ card and have an array of names for the channels to use. You then create the task running. or something like that. You like.

• Custom device error VeriStand-307603: no specified main page?

  I get the 307603 error when I try to add a custom device, I developed a VeriStand project on a client computer.  The message error window States:

  «Error 307603 occurred at Custom Devices Storage.lvlib:Initialize New Custom Device.vi > Custom Devices Main Page Data.vi Storage.lvlib:Get.»

  Possible reasons: NI VeriStand: the required custom device doesn't have a specified master page. Contact the creator of custom feature to correct the error. »

  I get this error when you add the device custom VeriStand on my development computer; only on the client computer.  I tried to copy the custom device built on top of the client computer and the custom device of source based on the customer's computer.  I also have three other devices custom that I developed that work fine on the same computer, so I don't know why it does not work.  I checked the specification of the build configuration to ensure that the VI home page is included in the source files, and to generate test preview shows only the custom device LLB and the XML from the file in the build directory, as expected.  The XML file is also oriented the correct path for the homepage VI and the GUID in the XML is the GUID file matches in overall search GUID variable.  I can't think of anything to check.

  Development computer:

  Windows 7, 64-bit

  LabVIEW 2011 SP1

  VeriStand 2011 SP1

  The client computer:

  Windows XP SP3, 32-bit

  LabVIEW 2011 SP1

  VeriStand 2011 SP1

  Everybody knows such a question or give me additional troubleshooting tips?

  I got it to work, but I don't know exactly what the problem was.  I made a copy of the part of the XML file that adds the device custom menu right-click and commented of the original, then edited the part I copied it to give the device custom a different name in the menu.  It worked fine on my development computer at the time I made the change, so I thought it was OK.  I just went and restored the file in the original version and now it works on my customer's computer.

• Deployment of a custom device error...

  I posted this question here:

  http://forums.NI.com/T5/NI-VeriStand/time-out-error-while-deploying-custom-device-with-can/TD-p/3288...

  However, being that it is created with LV, I'm also posting it here.

  Does anyone have any experience with this kind of problem?

  I know how to deploy DBs with XNET DB Editor. The question was related to the deployment of a custom device. I found a viable solution based on work done with the Addon J1939 VS.

• Read VeriStand channel from inside the custom device that are not part of the custom device?

  Is it possible to read VeriStand channels from within a custom device VeriStand (RT Driver) that are not part of this custom device?

  For example, suppose I want to be able to configure a channel in my custom device to always be twice the value of a string of material that my user selects (I know, better/more simple ways to do this, but this is just a simple example ).  Can I do this from the device custom without programmatically create a mapping of the system? (I've done this before and it is messy and VERY prone to error of the user).

  Thank you!

  good point

  the channel ID (U64s) are not the same in the engine config of vs. Instead, you must set 'references to dependent item' in the config and then get these references in the engine.

  See the source jarrod linked, which makes it

• Why my custom device break only when VeriStand trying to run it?

  Hello

  I have a custom device, he worked for some time now, today, I made a few changes to add some features more and now VeriStand tells me the RT pilot is more executable.

  I have not change my build configuration or add any functionas that could bring in an external DLL, or something that could link incorrectly.

  Any ideas of how I could go on this shrinking.  The problem is that when running in VeriStand.  Built LLB has no problem, the source of the development has no problem, it's only when VeriStand tries to deploy there is a problem, so there must be something that is not bound correctly Yes?

  The system isn't RT, it's just deploy on Windows using a SMU.

  I am not sure the exact cause, but I ended up simply remove parts of the code piece by piece pilot to refine what was causing the problem. It turned to be a VI of debugging I used several times before in various projects, but which contains the string "call" LabVIEW primitive, but set apart from that, it's just a simple string manipulation.  So I don't know if it was just a few cases of random edge that occurred when running under code basic LabVIEW VeriStand clean, but for some reason, he broke the driver VI.

  So, solved the problem, but the cause, I can't really say.

• Asynchronous custom device fails to stop

  While I was developing a custom asynchronous device, I came across a problem with the cancellation of the deployment of the .nivsproj I created to test the custom device.

  The custom device would send the error: -307730 Error Message: NI Veristand: one or more asynchronous custom devices did not close correctly and has been abandoned by the Veristand engine.

  I decided to do some troubleshooting for what could be wrong with the custom device by creating a separate custom device using the custom device model. I left completely intact model and it has deployed to our machine pharlap. When I canceled the intact custom asynchronous device it gave me the same error as above.

  I use Labview 2010 Professional version 10.0f2 development system, NI Veristand 2010 for a complete system of development and deployment of the .nivsproj on a licensed machine Pharlap.

  Sorry for the late reply.

  Zach-H by using simple device custom you provided I was able to create a custom asynchronous device that was able to stop. This allowed me to insert instructions printed in the two devices to help out what was causing the unit to raise an error when stopping.

  The culprit seems to be the NI VeriStand - Get loop Type.vi. The type of loop is never defined in the initialization.vi or the main.vi of the device model tool customized. So, when the RT pilot ran VI.vi the Type.vi loop get it would exit always false for the clock of the device to use and never use the correct name of the device clock. Without the name of the unit's clock he would never get a reason for reactivation.

  I forced the vi to use the clock of the device listed in the custom device model tool and I was able to shut down properly.

  TimothyA, you are right about the features of the measuring device. Even with the error of abnormal termination, the meter continues to operate normally after each deployment.

  Thanks for pointing out the problem with no channel being added to the measuring device. I'll make sure the custom device I develop handles the case where no channel, input or output, are added.

  Thanks for the help.

• I have problems with of the Subvi after the use of customized device model

  I used to start my machine personalized customized device model and I got success in the deployment until I started to do more complicated the Subvi.   I am currently trying to convert low FPGA and high ticks to the duty cycle, but for some reason when I add it to the RT VI "Data read of HW" driver, it seems to cause a downtime... ideas? Is a circuit agree? I have added a time delay but I am still having problems. It is a device online, so I'm suspicious of it hogging resources, but am not sure.

  Attached images are meant to be read like this:

  1. the case of the RT pilot ReadDataFromHW

  2. it's the Subvi calling ToDutyCycle SIMStimPWMSubVI

  3 ShiftRegister.PNG is inside the Subvi.

  As a robotician I celebrate early and often (usually by a failure or two...), but it seems that the answer was to transform fundamentally the While loop for a loop with a count of 1 and then remove the additional elements to ensure that each shift register has that one and then right click on the shift registers and convert at the Feedback node...
  I was able to deploy to VeriStand as a custom device and it runs and calculates the factor of use with no problems. WOOHOO! Where - what is celebrate button!

• The value of custom device entry

  Hello

  In fact, I create a custom (asynchronous) device that controls a climate system. It consists in adapting a functional code LabVIEW to create custom device. Unfortunately the LabVIEW code uses a lot of FGVs that act as input and outputs at the same time (this means that the system can change the value of an entry).

  So, I would like to know if there is an easy way to set the value of an entry in the custom device engine code. I tried the following without success:

  • Written in the FIFO of the entrance channel.
  
  
  • 'Set channel use value' of the API of NI VeriStand-> I get the error 307970.

  Yes, is there something I can do to facilitate the creation of my custom device? instead of "Rethinking" all the code which is a real pain in the * the complexity of it?

  Thanks in advance.

  Pen

  We solved that by using part of inllne to only update the channel and postponed the real asynchronous threads treatments with exchanges of data through FIFOs.

  ++

• create an alias for a custom device page

  Is there a way to create an alias for a custom device page?

  I wish that a button on the home page of my device custom (in solution system Explorer) allow the user to create an alias and linking this alias on a channel of the system. My Vi is the following:

  

  This VI returns the following error:

  "Error 1172 to error creating instance of aliases in the assembly NationalInstruments.VeriStand.SystemDefinitionAPI.Alias, NationalInstruments.VeriStand.SystemDefinitionAPI, Version = 2012.0.1.0, Culture = neutral, PublicKeyToken is a6d690c380daa308, (System.NullReferenceException: determined reference is not set to an instance of an object.).

  Is there a solution?

  Hmmm... good point. You can change my original solution to configure the alias using the basic underlying storage system node type. It should work regardless of the type of channel. As for your second question, custom devices written for 2012 should be recompiled in 2013 of LabVIEW with the support of 2013 VeriStand installed. You don't have to change your code, but you must recompile the LLBs.

  

  In this workaround, you start by creating an alias that links to nothing. Then, you update the alias to set the DependentNode property, which connects it to the channel. You should not do it this way, but this will work around the original bug.

• Rename a custom device

  Hi all

  I made a custom device that perform some operations with the associated DAQ card.

  In the Solution Explorer system Veristand, to manage several boards, it is possible to add multiple instances of it. The name of each instance must match the associated with a DAQ card, he is asked once and is never changes (in the camera custom XML file, I added the entry 'true').

  Demand for the name is made just after the addition of the instance in the tree Explorer (right click on the entry "Custom devices") system. In particular, the name is invited to call a VI that I put in the "Initialization.VI" of the library of device configuration custom. Unfortunately, this approach I am not able to change the name because ot the property of DisallowRenaming and an error is raised.

  How can I work around this problem? Is there an event as described in the "Custom Device" Guide (OnDelete, OnLoad,...) which can be pulled before the call of the "Initialization.VI", but after the addition of the instance in the system Explorer tree?

  Thank you

  aRCo

  I recommend to remove this label of your item custom main device. its best practice to rename the custom feature set.

  In addition, you can store the name of the physical device as a separate property rather than use the custom device node name.

  Finally, in 2012, we have added a "force rename" bool entry to the item to rename API to work around this problem.

• Use of Custom Device or lvmodel real-time Module utilities

  Hello

  I tried to understand how to use the RT Set processor pool inside of a custom device or lvmodel vi. My idea is to use one of my multiple devices customized to configure CPU pools in the VI Init. I added my custom for the device project PXI chassis, but does not know how I can put these functions in my custom device. Otherwise, I thought I could use a RT project and then to generate a model for VeriStand since VI, but this does not work either. LabVIEW impossible to compile the VI containing the RT module functions.

  My question:

  How can I use the utilities of RT in A) a custom device or B) a lvmodel?

  Thank you

  Brent

  Assumes that the solution is quite simple. All I had to do was go to C:\Program Files (x 86) \National Instruments\LabVIEW 2011\Targets\NI\RT\vi.lib and add the library to the project.

  Note If you add an RT target to the project and create screws under the lens of RT and move to the top of the library is automatically added... with a few errors of path of difficulty.

  Still familiarizing myself with labview course.

• Multi-threaded custom device

  Is it possible to create a custom multithreaded device?  I want to create a client-server architecture, somewhat like the http://zone.ni.com/devzone/cda/tut/p/id/3098 example in a custom device.  The only difference would be that I would like to make the series of read/write in the high priority task.

  Thanks for the help!

  -Ryan

  Hi Ryan,

  This should be possible if you use a custom asynchronous device. The curls will then run in their own thread and do not affect the execution of the primary control loop. Make sure that there is enough time sleeping in your loop of high priority. Note, however, that put communication series in the loop of high priority will negatively affect your determinism.

  For more information on the Veristand engine and the custom device types you can choose one, please see the following:

  Understand the VeriStand engine

  Creation of custom devices