Error 65550: CRio 9802

Similar Questions

• cRIO 9802 error 65000

  Hi all

  I tried the example LabVIEW "NI 9802 RT access (Host)", with which I want to get an SD card. I have to every time to get the error message attached. I've used chkdsk to fix the SD card and there is no errors in this regard. It is not a problem to write the file to the FPGA, but to get result RT of this error.

  I use LabVIEW 8.6. NEITHER RIO 3.0.1 installed on the cRIO.

  Can someone guide me towards a solution.

  

  Thank you.

  Alex

  Hi again,

  I've switched back to NI RIO 3.0 and can run the sample without problem.

  Thank you

  Alex

• Error 200220 CRIO 9081 and data acquisition modules

  Hello

  I try to use a CRIO 9081 with NI9206 modules. Max recognize the chassis, but not the module.

  When I try to add an acquisition of data associated with the NI9206 in Veristand, 200220 error message seems.

  I have the solution, finally he was required to add a custom device to search for new engines and detect modules. Then, it is possible to interact with modules.

  Thank you very much for your help!

• Strange error with cRIO and scan Mode

  I'm scanning two modules cRIO on a controller of 9012 + 9112 bottom of basket 8 channels in scan mode, and I call the function 'read the Variable scanned '.

  I see this error, each a few scans:

  Error -2132869099 occurred at Property Node (arg 1) in PolymorphicModuleScan.vi:7->sampleData2.vi->ZDAQ_cRIO_Target_Main.vi
  
  Possible reason(s):
  
  LabVIEW:  (Hex 0x80DF0015) A deployment transaction is in progress.
  

  The search for this error on NI.com gives no help at all.  This is the first time I see this (I've been running this code for some time without error).  All software is since the dev of August 2011.

  Resolved: I was calling the function "Get the Period.VI of Scan" scan at 1 Hz.  This seems to have caused the 9205 (not the 9237) produce this error.

  I removed the call to the offending function and this has solved the problem,

• error 1003 crio 9114

  Hello

  IM runninng a LV recently installed 14, on a Windows 7, 64-bit, with a crio 9114, RT and FPGA.

  I migrated a project from another computer with a similar system, installed moudles Lv and RT and FPGA, andDevice pilots.
  All elements of project in the aim of RT seem to be ok, but when I get to the FPGA screw, I managed to compile the XIlinx tools, but when it comes to run I get the followingL

  Error 1003 appeared to node invoke in niFpgaRun_LaunchTargetPlugin.vi-> niFpgaRun_InvokeRun.vi

  Possible reasons:

  LabVIEW: The VI is not executable. This error can occur because the VI is either broken or if it contains a Subvi LabVIEW cannot locate. Select file > Open to open the VI and verify that you can run it.

  Name of the method: Run VI

  The VI path: C:\Program Files (x 86) \National Instruments\LabVIEW 2014\vi.lib\FPGAPlugInAG\cRIO-9114\niFpgaOpenAndRun_cRIO-9114.vi

  I tried to make a simple FPGA project with a simple vi, and I get the same error.

  I opened the vi noted in the error message and it seems to be broken, but there is nothing I can do about it.

  I installed the module FPGA and the 15.0 NOR-RIO, but in vain.

  Could someone me hint how to solve this problem?

  Thanks DAvid

  Hi all and thank yo ufor responses

  a. the problem was not the bitfiles compiled, and I would have minded compile again. The problem is that even if I installed the appropriate drivers depending on the version of systems, the actual screw systems (located in C:\Program Files (x 86) \National Instruments\LabVIEW 2014\vi.lib\FPGAPlugInAG\cRIO-9114) were damaged.
  I had to replace manually by copying the files of same from an identical system, I had. This finally resolved the problem and everything is fine now.

  For future reference, I would advise NOT to:

  a. explain more detailed errors (error said that screw in FPGAplugin have been messed up, but were not clear on how to remedy).
  (b) have some sort of a downloadable vi to solve this problem, because if I had other systems I had no way to solve this

  see you soon

• LabVIEW with error FPGA cRIO

  When you try to run a VI that if interface with cRIO I get code error-63191. My cRIO is connected to my computer via an Ethernet cable, the cRIO and mobile LAN are the same IP address. The Project Explorer and MAX are able to detect the cRIO. Project Explorer is able to connect and to deploy.

  I tried to change the IP address in the 168.192.0.11 to 168.192.0.10 Project Explorer as the cRIO-9004 element is connected to the title of the first IP address, Project Manager (which seems to serve as an interface with the cRIO-9103 component) may be intellectual property conflicts. I end up getting a different-63040 error code.

  The first error screenshots are attacted and MAX and connection project manager

  Hello WheelchairDev,

  On this screenshot you just sent to the course, it seems that you do not have your project set up properly. You should have your project-> cRIO target-> cRio-> target FPGA chassis.

  If you want to see an example of this, of the LabVIEW startup window, select the FPGA project in the drop-down menu of targets to create a sample project.

  Once you change the layout, let me know if you have any other questions.

• FPGA reset during power loss? NEITHER 9802 Module

  We have recently started using the NI 9802 on a cRIO system. We get the error-65550 discussed here: http://digital.ni.com/public.nsf/allkb/BD118434E87B9732862575C8006FD7FB

  The article says that the error can be caused by resetting FPGA, while the drive was mounted. "To avoid this error to occur in the future, do not reset the FPGA so that you have an SD card installed, reset before getting the map or after the card is dismantling. Is a loss of power reset the FPGA and will need to reformat the card? We intend to use it as a remote system and the power failure is possible. We would not be able to travel hundreds of miles on the device to reformat an SD card in the case of a loss of power. This is not normal. How could they sell a module that worked like this?

  In addition, must the card be formatted with FAT32 or FAT16?

  rex1030,

  You can make this system more reliable is to wire the battery backup to the secondary entrance on the cRIO.  There is screw allows you to analyze of what energy source is active (I think there are examples, otherwise I can watch it for you) so that you can detect that you have switched to the backup power source and properly remove your SD card.  When the power is restored you can back the card and continue where you left off (and ideally to recharge the battery backup).

  Sebastian

• what disk path is really being checked when grid installation fails with PRVF-9802?

  Update: apparently, it's a false warning, like '... we cannot thoroughly test all combinations of SAN/udev'.

  [grid@rac101: grid] $./runcluvfy.sh stage pre - crsinst - n, rac101, rac102, rac103 - asm - asmdev/dev/prod_ocr1p1, / dev/prod_ocr2p1

  Conducting due diligence to install cluster services

  ...

  Control devices of the ASM...

  ERROR: / dev/prod_ocr1p1

  Storage is not found

  ERROR: / dev/prod_ocr2p1

  Storage is not found

  Checking for shared devices...

  PRVF-5150: / dev/prod_ocr2p1 path is not a valid path on all nodes

  PRVF-5150: / dev/prod_ocr1p1 path is not a valid path on all nodes

  Attributes of UDev search drives ASM began...

  ERROR:

  PRVF-9802: try to get information node udev "rac102" failed

  ERROR:

  PRVF-9802: try to get information node udev "rac101" failed

  ERROR:

  PRVF-9802: try to get information node udev "rac103" failed

  Check failure of UDev attributes for ASM disks

  Devices to check for ASM failed

  ....

  [grid@rac101: grid] $ he 's/dev/prod *.

  BRW - rw - 1 grid asmadmin 252, 6 Nov 10:01 5 / dev/prod_ocr1

  BRW - rw - 1 grid asmadmin 252, 17 Nov 10:01 5 / dev/prod_ocr1p1

  BRW - rw - 1 grid asmadmin 252, 5 Nov 13 10:01 / dev/prod_ocr2

  BRW - rw - 1 grid asmadmin 252, 5 Nov 19 10:01 / dev/prod_ocr2p1

  BRW - rw - 1 grid asmadmin 252, 7 Nov 10:01 5 / dev/prod_ocr3

  BRW - rw - 1 grid asmadmin 252, 5 Nov 16 10:01 / dev/prod_ocr3p1

  BRW - rw - 1 grid asmadmin 252, 5 Nov 14 10:01 / dev/prod_vot1

  BRW - rw - 1 grid asmadmin 252, 5 Nov 21 10:01 / dev/prod_vot1p1

  BRW - rw - 1 grid asmadmin 252, 8 Nov 10:01 5 / dev/prod_vot2

  BRW - rw - 1 grid asmadmin 252, 5 Nov 18 10:01 / dev/prod_vot2p1

  BRW - rw - 1 grid asmadmin 252, 15 Nov 10:01 5 / dev/prod_vot3

  BRW - rw - 1 grid asmadmin 252, 20 Nov 10:01 5 / dev/prod_vot3p1

  ...

  [grid@rac101: grid] $ he 's/dev/map

  Total 0

  CRW - rw - 1 root root 10, Nov 5 236 control 10:01

  lrwxrwxrwx 1 root root 11 5 Nov 10:01--> FSSYSDB1... / FSSYSDB1

  lrwxrwxrwx 1 root root 11 5 Nov 10:01--> FSSYSDB2... / FSSYSDB2

  lrwxrwxrwx 1 root root 11 5 Nov 10:01--> FSSYSDB3... / FSSYSDB3

  lrwxrwxrwx 1 root root 11 5 Nov 10:01--> FSSYSDB4... / FSSYSDB4

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> FSSYSLOG1... / FSSYSLOG1

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> FSSYSLOG2... / FSSYSLOG2

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> FSSYSLOG3... / FSSYSLOG3

  lrwxrwxrwx 1 root root 12 6 Nov 10:47 prod_ocr1->... /prod_ocr1

  lrwxrwxrwx 1 root root 14 6 Nov 10:58--> prod_ocr1p1... /prod_ocr1p1

  lrwxrwxrwx 1 root root 12 6 Nov 10:47 prod_ocr2->... /prod_ocr2

  lrwxrwxrwx 1 root root 14 6 Nov 10:48-> prod_ocr2p1... /prod_ocr2p1

  lrwxrwxrwx 1 root root 12 6 Nov 10:48-> prod_ocr3... /prod_ocr3

  lrwxrwxrwx 1 root root 14 6 Nov 10:48-> prod_ocr3p1... /prod_ocr3p1

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> prod_vot1... /prod_vot1

  lrwxrwxrwx 1 root root 14 5 Nov 10:01--> prod_vot1p1... /prod_vot1p1

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> prod_vot2... /prod_vot2

  lrwxrwxrwx 1 root root 14 5 Nov 10:01--> prod_vot2p1... /prod_vot2p1

  lrwxrwxrwx 1 root root 12 5 Nov 10:01--> prod_vot3... /prod_vot3

  lrwxrwxrwx 1 root root 14 5 Nov 10:01--> prod_vot3p1... /prod_vot3p1

  lrwxrwxrwx 1 root root 7 5 Nov 10:01--> zero... DM - 2

  lrwxrwxrwx 1 root root 8 Nov 10:01 vg_01-lv_home--> 5... DM - 23

  lrwxrwxrwx 1 root root 7 Nov 10:01 vg_01-lv_root-> 5... DM - 0

  lrwxrwxrwx 1 root root 7 Nov 10:01 vg_01-lv_swap--> 5... DM - 1

  lrwxrwxrwx 1 root root 8 Nov 10:01 vg_01-lv_tmp--> 5... DM - 24

  lrwxrwxrwx 1 root root 8 Nov 10:01 vg_01-lv_u01--> 5... DM - 25

  lrwxrwxrwx 1 root root 8 Nov 10:01 vg_01-lv_var--> 5... DM - 22

  I have found no change in rules multipath.conf or udev that changes ownership here.  I have an alias records in my multipath.conf file, which is NOT readable by the user of network:

  ...

  	{multichannel
  	WWID 36000d310007cbd00000000000000002c
  	alias prod_ocr1
  	}
  	{multichannel
  	WWID 36000d310007cbd00000000000000002d
  	alias prod_ocr2
  	}
  	{multichannel
  	WWID 36000d310007cbd00000000000000002e
  	alias prod_ocr3
  	}

  Also tried to add a uid, gid, multipath.conf mode, but no diff.

  A ran kpartx - a/dev/prod_ocr {1 | 2 | 3} on all nodes. Started several times.

  ....

  [root@rac101: ~] # he 's/dev/oracleasm/discs.

  Total 0

  BRW - rw - 1 grid asmadmin 8, 240 5 Nov 10:01 FSSYSDB1

  BRW - rw - 1 grid asmadmin 8: 32 Nov 10:01 FSSYSDB2 5

  BRW - rw - 1 Grill asmadmin 65, 0 5 Nov 10:01 FSSYSDB3

  BRW - rw - 1 grid asmadmin 8, 48-5 Nov 10:01 FSSYSDB4

  BRW - rw - 1 Grill asmadmin 65, 128 5 Nov 10:01 FSSYSLOG1

  BRW - rw - 1 grid asmadmin 8, 64-5 Nov 10:01 FSSYSLOG2

  BRW - rw - 1 Grill asmadmin 65, 32 5 Nov 10:01 FSSYSLOG3

  BRW - rw - 1 grid asmadmin 8, 81-5 Nov 10:01 OCRVOTE1

  BRW - rw - 1 Grill asmadmin 65, 49-5 Nov 10:01 OCRVOTE2

  BRW - rw - 1 grid asmadmin 8, 97-5 Nov 10:01 OCRVOTE3

  BRW - rw - 1 Grill asmadmin 65, 65 5 Nov 10:01 OCRVOTE4

  BRW - rw - 1 grid asmadmin 8, 113 5 Nov 10:01 OCRVOTE5

  BRW - rw - 1 Grill asmadmin 65, 81-5 Nov 10:01 OCRVOTE6

  ....

  I did createdisk on all disks, and listdisk is compatible on all nodes:

  [root@rac103 ~] # oracleasm scandisks

  Reload from disk partitions: fact

  Cleaning up stale ASM disks...

  ASM disks scanning system...

  Instantiation of disk 'FSSYSDB2 '.

  Instantiation of disk 'FSSYSDB4 '.

  Instantiation of disk 'FSSYSLOG2 '.

  Instantiation of disk 'OCRVOTE1 '.

  Instantiation of disk 'OCRVOTE3 '.

  Instantiation of disk 'OCRVOTE5 '.

  Instantiation of disk 'FSSYSDB1 '.

  Instantiation of disk 'FSSYSLOG1 '.

  Instantiation of disk 'FSSYSDB3 '.

  Instantiation of disk 'OCRVOTE2 '.

  Instantiation of disk 'FSSYSLOG3 '.

  Instantiation of disk 'OCRVOTE4 '.

  Instantiation of disk 'OCRVOTE6 '.

  ....

  [root@rac101: ~] # oracleasm deletedisk - v/dev/prod_ocr1p1

  Disk "OCRVOTE1" is a valid ASM disk

  Header of drive compensation: oracleasm-writing-label: could not open device ' / dev/oracleasm/disks/OCRVOTE1 ': device or resource busy

  has failed

  Impossible to erase the disk 'OCRVOTE1 '.

  ...

  [root@rac101: ~] # oracleasm OCRVOTE1/dev/prod_ocr1p1 createdisk

  Device "/ dev/prod_ocr1p1" is already tagged for disc ASM 'OCRVOTE1 '.

  ....

  My udev rules are quite simple and readable by the user of network:

  [grid@rac101: grid] $ cat /etc/udev/rules.d/20-UEKasm-oracle.rules

  ENV {nom_DM} == "FSSYSDB?", NAME: = "%E {nom_DM}", OWNER: = "grid", GROUP: = "asmadmin", MODE: = "660".

  ENV {nom_DM} is "FSSYSDB? p? ", NAME: ="%E {nom_DM}", OWNER: ="grid", GROUP: ="asmadmin", MODE: ="660 ".

  ENV {nom_DM} == "FSSYSLOG?", NAME: = "%E {nom_DM}", OWNER: = "grid", GROUP: = "asmadmin", MODE: = "660".

  ENV {nom_DM} is "FSSYSLOG? p? ", NAME: ="%E {nom_DM}", OWNER: ="grid", GROUP: ="asmadmin", MODE: ="660 ".

  ENV {nom_DM} == "prod_ocr?", NAME: = "%E {nom_DM}", OWNER: = "grid", GROUP: = "asmadmin", MODE: = "660".

  ENV {nom_DM} is "prod_ocr? p? ", NAME: ="%E {nom_DM}", OWNER: ="grid", GROUP: ="asmadmin", MODE: ="660 ".

  ENV {nom_DM} == "prod_vot?", NAME: = "%E {nom_DM}", OWNER: = "grid", GROUP: = "asmadmin", MODE: = "660".

  ENV {nom_DM} is "prod_vot? p? ", NAME: ="%E {nom_DM}", OWNER: ="grid", GROUP: ="asmadmin", MODE: ="660 ".

  What did I wrong? Thanks in advance.

  In addition, changed paths drive going on and still fails!

  [grid@rac101: grid] $./runcluvfy.sh stage pre - crsinst - n, rac101, rac102, rac103 - asm - asmdev/dev/oracleasm/disks/OCRVOTE1, / dev/oracleasm/disks/OCRVOTE2

  ....

  Control devices of the ASM...

  Checking for shared devices...

  Peripheral device type

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

  / dev/oracleasm/Disks/OCRVOTE2 disk

  / dev/oracleasm/Disks/OCRVOTE1 disk

  Consistency check of the owner of the device on all nodes...

  Check the consistency of the owner of the device for ' / dev/oracleasm/disks/OCRVOTE1 ' PASSED

  Check the consistency of the owner of the device for ' / dev/oracleasm/disks/OCRVOTE2 ' PASSED

  Checking consistency of the set of instruments through all nodes...

  Check the consistency of a set of instruments for ' / dev/oracleasm/disks/OCRVOTE1 ' PASSED

  Check the consistency of a set of instruments for ' / dev/oracleasm/disks/OCRVOTE2 ' PASSED

  Consistency check permissions of device on all nodes...

  Check the consistency of the device permissions for ' / dev/oracleasm/disks/OCRVOTE1 ' PASSED

  Check the consistency of the device permissions for ' / dev/oracleasm/disks/OCRVOTE2 ' PASSED

  Consistency check of the size of the unit on all nodes...

  Check the consistency of the size of the unit to ' / dev/oracleasm/disks/OCRVOTE1 ' PASSED

  Check the consistency of the size of the unit to ' / dev/oracleasm/disks/OCRVOTE2 ' PASSED

  Attributes of UDev search drives ASM began...

  ERROR:

  PRVF-9802: try to get information node udev "rac102" failed

  ERROR:

  PRVF-9802: try to get information node udev "rac101" failed

  ERROR:

  PRVF-9802: try to get information node udev "rac103" failed

  Check failure of UDev attributes for ASM disks

  Devices to check for ASM spent

  ...

  Post edited by: user10501000

  ... so we ignored the error and it installed fine.

• VI to convert input signals NI 9402 in a RPM value, based on the frequency of the pulses

  Hello

  I'm looking for a VI convert an input signal NI 9402 in a RPM value, based on the frequency of the pulses. Is there such a thing that exists in the library of national instruments?

  I run LAbview 2014 integrated control and monitoring on on a cRIO 9802 high performance integrated system with NEITHER 9402, 4 channels, 50 LV, LV TTL Module input/output digital, ultra high speed digital i/o for the cRIO module.

  Any help would be greatly appreciated.

  The easiest way is to use the FPGA to get the time between the edges of your pulse increase (shift registers to maintain the current situation and the time will be necessary).  This will give you the period.  If it's a single pulse per turn, then the number of laps is just 60/T, where T is the time in seconds.

• FTP 9802 by cRIO-9074

  Hi all

  Using the example of LV I can apparently go up and write on a SC map in a module 9802 without problem. A sample file is written to the location u:\Example.txt

  Unfortunately, I can't FTP to this player using the address ftp://xxx.xxx.xxx.xxx/u :/ (I can ftp to the controller, a cRIO-9074, without problem). When trying to connect to the SD card, the internet Explorer simply indicates that the page cannot be displayed.

  Various previous discussions talk about adding a property node (where should pass exactly?) that allows to resolve a conflict. Supposedly this problem has been resolved the recent versions of RIO.

  Another discussion suggests that RIO 3.0.0 worked while RIO 3.1.0 failed in a manner similar to what I see - he seems to not have been a resolution.

  I'm running RIO 3.1.0 with Support of EtherCAT Scan Engine since October 2008.

  Ideas?

  Thank you!

  a slight correction... I "cd" to the "sup" drive letter and the crio ftp server responds "Directory changed to" / u: / '. '.   Sorry for the mistake.

  quarterlbr wrote:

  Hi-

  just stumbled on this thread - I hope that someone is always watching...

  I have a similar problem, (9074 w/9802) that I can't ftp access to the card.  I can mount it and writing, but I do not see in ftp.

  I mount it and it assign a drive letter.

  through screw normal rt file, writing to the card.

  Let the mounted card until the program ends, then it should retain the drive letter - correct?

  When I ftp to the card (via ftp console), I "cd" to the drive letter "x:" and the crio ftp server responds "Directory changed to" / u: / '. '.  look suspicious to me, but in any case, I try to "dir" content and I get an 'error of e/s 451.

  I checked the content of the map is there in removing the card and reading the contents via a card reader.

  no idea what I am doing wrong?

  I have installed 3.1.1 rio.

  Thank you.

• error when trying ot read more large block memory on cRIO 9067 LVRT 2014

  I get error "-2147220623" when you run the following code on a cRIO 9067. It works on the cRIO 9074

  

  
  

• Version with ControlLogix - link cRIO (implicit messaging), "(Code 16 #0315) problem" connection request error: invalid segment type ""

  I have developed and delivered a system in Germany several years ago.  He worked then.  But the cRIO was damaged and replaced by a newer model, and does not now.  I suspect (and Support technical OR agree) it's a problem of software version, which could be solved with the NOT-MAX Software Installer.  But I do not have access to the system myself, and correspondence is slow and tedious.

  The original system was a cRIO-9073, developed with LabView 2009.  He used the implicit Messaging.  The ID of Instance, sizes, IP addresses, etc everything has worked very well.

  The current system is a cRIO-9074, with LabView DURATION 14.0 (I guess that LV 2014), Scan Engine 4.3, NI - Industrial Communications for Ethernet/IP 14.0.0, etc.  Programs FPGA and processor are responsible and seem to work in the cRIO.  The "EthernetIP Set Assembly Instance Data.vi' will return no error.  But the PLC just pointing out "(Code 16 #0315)" connection request error: invalid segment type "."  We looked at intellectual property (the mistake was different), sizes and body #s.

  The PLC doesn't have to all be modified.

  Anyone know if there is no problem of compatibility with LV-2014 and Ethernet/IP 14.0.0?  Or if there are all the other required packages?

  I am including the NOT-Max reports.

  Hi ZX81

  To help you 2009 application to work with the new cRIO, you must deploy it to the device. You must in order to deploy the cRIO, make sure it has the same versions of software that you used with the old cRIO.

  You can format the cRIO NI MAX and deploy the application of LV, 2009. However, if you do not have access to the cRIO or your client does not have the necessary software, you can deploy the application in another cRIO with software (cRIO same model and same modules as your client) and create a picture of it and send it to your customer so that it can deploy the cRIO even without the software on his computer. The following document explains how to do this.

  Utility of RAD

  WenR

• Error Code HDL with CRio RFP generation after update for LabView 2012

  Hello everyone,

  I use a CRio DP Comsoft master/slave module for my communication with a PLC system. The application worked perfectly under LabView 2011. After the update to LabView2012, I got an error message that the HDL Code generation failed. After that I've updated also the Software NI Profibus CRio in Version 1.3, but this n ' t´t solve the problem. The next step was to use the example of project code "CS_cRIO-PB_DP-MasterExample" which was delivered with the new NI CRio Profibus software. Even with this code example, the problem still exists. For detailed information on the configuration and the error message please refer to the screenshot. Any help or idea would be appreciated.

  Jürgen

  Hi Jürgen,

  I looked inside and could reproduce this error. Somehow the compiler with LV 2012 has problems with the coded 8.5.1 Subvi LV. Please use the attached VI and copy it to the following location. (\\Program Files\National Instruments\LabVIEW 2012\vi.lib\addons\Comsoft.lib\cRIO PB)

  Before do you it please close your LabVIEW.

  Then try to compile again.

  Let me know if it still does not. We are currently working on a new installer that will correct this problem.

  DirkW

• cRIO 9068 + Scan Engine Support error - even if it is installed on the cRIO, after the deployment of error says his lack

  All,

  I have a cRIO-9068 I try to use the scan mode for. I have intalled all the latest drivers and software as explained. However, when I put my chassis to scan mode, then select deployment all, I get this error on my chassis and all my modules:

  "The current module settings require a NI Scan Engine support on the controller. You can use Measurement & Automation Explorer (MAX) to install a software package recommended NOR-Rio with NI Scan Engine support on the controller. If you installed LabVIEW FPGA, you can use this module with LabVIEW FPGA by adding an element of FPGA target under the chassis and drag and drop the module on the FPGA target element. »

  Everyone knows this or know why labVIEW does not recognize that the software is installed on my cRIO or is it not installed correctly?

  AGJ,

  Thanks for the image. I saw a green arrown beside all my pictures of chip and it seemed that meant that the software wasn't really being installed. I formatted my cRIO and did a custom install. My problem was that I had the two labview 2013 and 2014 installed and the cRIO put conflicting versions of software. After doing a custom installation and choose only the versions of 2014, my picture now looks like yours!

• cRIO ethercat application error

  I have a cRIO-9074 connected to and AKD via EtherCAT drive, running in standard mode.

  Simple straight line move using a VI express softmotion.

  It works fine except when I force the engine to stall, a strange thing.

  When I take the engine yet it will suddenly reverse direction rotates at a speed faster than the requested speed rear forward.

  The faults of the ADK out but it takes 100 to 400 ms to turn off the power.

  The AKD displays F 503 and Labview indicates an error code 6A 3130.  This resulted in "phase failure AKD.

  Relavent part of this error is: "the excessive power single-phase connection load".

  Of course I am inducing power over load so expect this fault, but the reverse rotation before the AKD Cup feeding is strange.

  I tried to reproduce this using the Kollmorgen Workbench software, but so far it only happens when Labview is controlling via EtherCAT.

  Hello Brians,

  Taking the engine beyond normal limits of operation may cause unexpected behavior. It is never recommended to intentionally block the engine. In this case, it seems that LabVIEW is trying to remove the constraints inherent in the system in the case of a stall by reversing the motor. The reason why you do not see this behavior in the Workbench is because it does not contain the control algorithms that are present in LabVIEW. In addition, I am curious about how to determine the time the motor runs in reverse; 100-400 ms seems very specific. If the pitch of the engine is possible in your code, I need to program under a security to handle this situation and perform all measures requires your application in the case of a stall.

  N