How to prevent cRIO Scan Engine Warning 66030

I find that when my cRIO cpu spikes briefly I can trigger something bad in the scan engine and it will start spewing 66030 warnings and go into a Fault state.
The only recourse at that point is to reset the cRIO even though the cpu usage has returned to normal. I would like to know if there is anyway to make the scan engine
a little bit more forgiving of cpu spikes?

sachsm:
Is that 66030 or -66030?
66030: This I/O variable is referencing an I/O device or channel that is not active in the current I/O mode. Data read may be stale or invalid and data written may not be sent to the output.
-66030: The operation cannot be completed because one of the scanned I/O buses is not in the required I/O mode.
I'm assuming it's the non-negative one, but I just want to be sure.
If so, I think your best bet is to clear that specific warning code and/or use the programmatic Scan Engine configuration and fault handling VIs to correct the Scan Engine.
(The VIs are located in "Measurement I/O --> NI Scan Engine").
Hope that helps!
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

Similar Messages

Does the cRIO scan engine support TEDS

I have a cRIO chassis with 9237 bridge amplifier modules and would like to use the TED feature of my transducers. I know the module itself supports TEDS but is this functionality incorporated into
the new scan engine?
Thanks

Hi Sachsm,
Currently, there is no support for TEDs with the CompactRIO Scan Interface. However, you should be able to write an application that will allow you to get to your desired TEDs information by compiling two biftfiles, one that communicates to the modules using the TEDs interface that is supported with the LabVIEW FPGA Host interface functions, and another that then just communicates to Modules through the Scan Interface.
After the TEDs information was read from the first bitfile, then you could use this information to calibrate the data used for the sensor.
Let me know if you would like me to explain a little bit further or if you think the solution would work for you.
Thanks,
Basset Hound

Scan Engine Warning 537549

I am getting this warning message on my cRIO but it appears to be undocumented.
Does anybody know what it means?

Hey sachsm,
What VI is the warning occurring at? Does it have anything to do with an XML toolkit (this is the only reference I managed to locate on this code)? What other problems are you seeing with your code, if any? Are you using any VIs that might be considered unusual? What modules are you using in scan mode?
One recommendation would be to walk through the code in highlight execution mode to figure out exactly where the warning occurs.
Thanks,

Does the cRIO Scan Engine Support Offset and Shunt Calibration on the 9237 module

Thanks.

Sachsm,
The documentation for the Set Shunt Calibration (Scan Interface).vi should have been in the VI help but it looks like it didn't make it so I'll make sure it gets updated. I'll double check my understanding tomorrow morning but the documentation should be the following for the inputs of this VI:
slot - Specifies the chassis slot of the strain module (9237, 9235, 9236 ). Valid values are 1 through N, where N is the number of slots in the chassis.
channel - Specifies the channel to be affected. Valid values are 0-N where N is the channel for shunt calibration.
value - Turns Shunt calibration on or off. Valid values are 0 or 1 where a value of 1 will turn shunt calibration on for the given slot and channel.
Now, for your orginal question about offsets on the AI inputs, here are my addtional thoughts:
Unlike our SCXI products, the NI 9237 does not have an internal hardware nulling circuitry because its input range is sufficiently wide so that the inputs will not saturate even with a very large initial bridge offset. Since the 9237 does not have any hardware nulling circuitry, you have to perform offset nulling with software compenstation, and save the value to use later in the application as you mentioned. For example, when an offset null is performed in DAQmx, the entire offset is stored in the Initial Bridge Voltage property and is stored in software. You should see the same offset if you used the module from DAQmx, FPGA Interface, or in the Scan Interface. With that being said, I believe what your seeing is really just the resting measurement of the module and transducer together and you should be able to zero out your measurement by performing Software Compensation.
Regarding, Offset Calibration, I think its important to make clear exactly what it is providing as the name is a little misleading. The Offset Cal feature of the 9237 is really more like an Auto Zero used for eliminating offsets generated by an amplifier stage and doesn't provide the same behavior as offset nulling. In Auto Zero Mode, the 9237 shorts the input channel to ground and subtracts the obtained measurement from all subsequent samples. Performing an auto zero is a quick calibration technique that takes place at the beginning of a scan. A typical use of the Offset calibration feature would be to set it true at the begining of acquiring data and then leaving it on indefinitely.
Personally, I do not bother enabling offset cal in my FPGA applications because the measurement of the sensor at rest takes into account all sensor and module offsets.
And finally, if your looking for some information on how to perform shunt calibration, I like to refer to the example VI located here:
C:\Program Files\National Instruments\LabVIEW 8.6\examples\CompactRIO\Module Specific\NI 9235\NI 9235 Getting Started
As it has walks through the programming steps of setting up Shunt cal and applying the Gain Factors. Its written for LabVIEW FPGA but it should be easy to use with Scan Interface.
Hope that helps a little bit,
Let me know if you have questions and I'll help where I can or bug the right engineer.
Basset Hound

Programmatically change cRIO scan engine IOV scaling

Has anyone created any vi's that can do this? I have located the config.xls files on the cRIO that specify the scaling parameters and this can be changed by parsing and modifiying the xml data but it would be very nice to have a ni approved tool or api to handle this. In the real world, a system needs the ability to change scaling of xducers. For example when a pressure transducer goes out for calibration you need a way to easily change the scaling without having to rebuild the rtexe.

Hi sachsm,
I would recommend checking out this example. If you dig in, you'll see property nodes and methods for creating your own variables programmatically. It'll also give clues about what parameters we can change.
https://decibel.ni.com/content/docs/DOC-5929
Regards,
Che T.
Applications Engineer
National Instruments

Programmatically remove ethercat slaves from scan engine

I am using an RT Target as the master of EtherCAT chain. It has several different sorts of third party slaves in the chain. All are correctly detected. However some are buggy (they're in development) and prevent the Scan Engine from switching to Active mode. If I remove the buggy slaves from under EtherCAT Master (but leave them plugged into the chain) in the project then the Scan Engine will switch to Active and the remaining targets are interogated correctly.
However I want my RT app to be stand alone and adapt to different chains of slaves. I invoke the Refresh Modules method to find all the available slaves then it finds the buggy ones. These then prevent the Scan Engine from switching to Active mode. I have not been able to find a way to programmatically remove these buggy slaves as I can from the project - does it exist???
Many thanks!

I am not sure if you will be able to do this but I would suggest posting this question to the Industrial Communications board.
http://forums.ni.com/t5/Industrial-Communications/bd-p/260
If this is something that you are able to do, the people that frequent that board are much more likely to know about it.
Matt J
Professional Googler and Kudo Addict
National Instruments

9236 enable shunt cal property crashes crio OS with scan engine

I would like to inform users of the 9236 Quarter Bridge Strain Gauge Module of a bug. The Real-Time team is aware of this issue and I have been working with an app engineer on it for about a week and he has confirmed my findings. He says the problem is most likely a driver issue or scan engine issue and they are investigating it.
There is a bug that completely crashes the cRIO operating system with the 9236 module. Currently when a cRIO device is loaded with LV2009 SP1 or LV2010 and using scan engine interface, attempting to write the "shunt cal enable" property of a 9236 module completely crashes the VxWorks OS. If you try to access the property again, the crio crashes and enters an error state where the crio has rebooted twice without being told to. The LED indicator blinks four times to indicate this.
I have tested this with a few different hardware combinations with both the crio-9014 and crio-9012 controllers, combined with either the 8-channel 9104 back plane or the 4-channel 9102 back plane with the same results. The app engineer was able to duplicate this issue as well.
To duplicate the bug:
Load a crio device with 2009 SP1 or LV2010 and configure the device for scan engine. Locate the 9236 module in the project explorer and drag and drop it into a VI to create the IO variable. Right click the output terminal of the IO Variable and go to create > property > enable shunt calibration on a channel. Once the property is dropped, right click on it and do change to write so that you can write a boolean to the variable. It doesn't matter if you write a true or false to the property, the results are the same. Hit run, watch it crash. When it reboots, hit run again. The crio is now in a state that can only be recovered by physically resetting the device.
I love the crio stuff and I use it every day because it is very reliable and robust. This kind of thing is rare, which is why I am reporting it to the community as well as NI as it is a pretty big bug that took me a while to narrow down.
[will work for kudos]

rex1030,
Shunt calibration can be accessed using a property node. The operation will be the same, you still need to acquire two sets of data and compute the scalar.
You can obtain the necessary reference by dragging the module to the block diagram from the project. Please see http://zone.ni.com/devzone/cda/tut/p/id/9351 for more information on programmatic configuration.
Let me know if you have any other questions.
Sebastian

CRIO 9068 + Scan Engine Support Error - Even though it is installed on cRIO, after deploying error says its missing

All,
I have a cRIO-9068 that I am trying to use the scan mode for. I have intalled all the latest drivers and software as explained. However, when I set my chassis to scan mode and then select deploy all, I recieve this error on my chassis and all of my modules:
"The current module settigns require NI Scan Engine support on the controller. You can use Measurement & Automation Explorer (MAX) to install a recomended software set of NI-RIO with NI Scan Engine support on the controller. If LabVIEW FPGA is installed, you can use this module with LabVIEW FPGA by adding an FPGA Target Item under the chassis, and drag and drop the module onto the FPGA Target Item."
Has anyone experienced this or know why labVIEW won't recognize that the software is installed on my cRIO or is it not being installed correctly?
Solved!
Go to Solution.

So I found that the target's Scan Engine was in Configuration mode. After placing it in Active, I was able to deploy all of the modules on the cRIO target. However, now I cannot deploy any of my modules on my EtherCAT NI 9144 racks regardless of which scan mode I place the Scan Engine. I verified that I have all software on the cRIO target I need. I was also able to find the EtherCAT slaves and their modules on MAX and I was able to add them to the project. The problem I am having is being able to deploy them. I have gone through the procedure outlined in the manual provided with the EtherCAT racks and the following link with no issues: http://www.ni.com/white-paper/10555/en/
The top LEDs on the EtherCAT racks are solid yellow and the bottom are solid green. Does anyone know why I may be having this problem?

Can you still use soft motion without the scan engine on crio?

Where are the trajectory generator property and invoke nodes in softmotion for LV 2011?
These functions are not longer found in the pallet? Are they no longer supported?
All the new soft motion examples are using the scan engine. Can I use soft motion without the scan engine????
Steve
SteveA
CLD
FPGA/RT/PDA/TP/DSC

Hi Ian,
I apologize that this wasn't stated in the release notes. While your code should have upgraded without breaking, the release documentation should have mentioned that the advanced trajectory genertor functionality is no longer supported. If you still want to use the trajectory generator functions, they are still shipped with SoftMotion, they are just not on the palette. I have attached a zip file that has 4 .mnu files that will get them on the palette. To install these, do the following:
Close LabVIEW
Make a copy of the following directory: C:\Program Files (x86)\National Instruments\LabVIEW 2011\menus\Categories\VisionMotion\_nism. In case something goes wrong, we will want to have a copy of this directory so that we can replace it.
Copy the 4 .mnu files from the attachement into the above _nism directory (the original, not the copy). If it asks you to replace any of the exisiting files, please do. You don't have to copy the readonly.txt file.
Start LabVIEW. You should know have the trajectory generator functions in your SoftMotion Advanced palette.
Keep in mind that we no longer support these functions. This means that they are not tested in new releases and any bugs will likely not get fixed.
I would recommend that you use the new API for any new designs. You can still get most of the functionality of the old API but without the complexity. If you want to generate setpoints at 5ms then you will run the scan engine at 5ms. This is certainly easier than having to do the timing yourself, but it does take away some control from the user. If you give me a brief overview of what you mean by synchronization, I will let you know the best way to do it with the new API.
Thanks,
Paul B.
Motion Control R&D
Attachments:
_nism.zip ‏4 KB

NI Scan Engine, cRIO 9211 and CJC

Does anyone know if the temperature returned by the scan engine uses the CJC and zero offset channels on the 9211?
Thanks

This is what the 9211 user manual says about it.
http://digital.ni.com/manuals.nsf/websearch/A24B9BB284234EDF862571CA00684AC7
Heat dissipated by adjacent modules or other nearby heat sources
can cause errors in thermocouple measurements by heating up the
terminals so that they are at a different temperature than the
cold-junction compensation sensor used to measure the cold
junction.
Not sure what the different ways for implementing CJCs are, but is there something that can be inferred by knowing that is a an actual sensor within the module?

Optimizing EtherCAT Performance when using Scan Engine

Hello everyone,
This week I have been researching and learning about the limitations of the LabVIEW's Scan Engine. Our system is an EtherCAT (cRIO 9074) with two slaves (NI 9144). We have four 9235s, two 9237s and two 9239 modules per chassis. That means we have a total of 144 channels. I have read that a conservative estimation for each scan is 10 usec. This means with our set up, assuming we only scan it would take 1.44 msec which would yield roughly a rate of 694 Hz. I know that when using a shared variable, the biggest bottle neck is transmitting the data. For instance, if you scan at 100 Hz, it'll be difficult to transmit that quickly, so it's best to send packets of scans (which you can see in my code).
With all of that said, I'm having difficulties scanning any faster than 125 Hz without railing out my CPU. I can record at 125 Hz at 96% of the CPU usage but if I go down to 100 Hz, I'm at 80%. I noticed that the biggest factor of performance comes when I change my top loop's, the scan loop, period. Scanning every period is much much more demanding than every other. I have also adjusted the scan period on the EtherCAT's preferences and I have the same performance issues. I have also tried varying the transmission frequency(bottom loop), and this doesn't affect the performance at all.
Basically, I have a few questions:
1. What frequency can I reasonably expect to obtain from the EtherCAT system using the Scan Engine with 144 channels?
2. What percent of the CPU should be used when running a program (just because it can do 100%, I know you shouldn't go for the max. Is 80% appropriate? Is 90% too high?)
3.Could you look through my code and see if I have any huge issues? Does my transmission loop need to be a timed structure? I know that it's not as important to transmit as it is to scan, so if the queue doesn't get sent, it's not a big deal. This is my first time dealing with a real time system, so I wouldn't be surprised if that was the case.
I have looked through almost every guide I could find on using the scan engine and programming the cRIO (that's how I learned the importance of synchronizing the timing to the scan engine and other useful facts) and haven't really found a definitive answer. I would appreciate any help on this subject.
P.S. I attached my scan/transmit loop, the host program and the VI where I get all of the shared variables (I use the same one three times to prevent 144 shared variables from being on the screen at the same time).
Thanks,
Seth
Attachments:
target - multi rate - variables - fileIO.vi ‏61 KB
Get Strain Values.vi ‏24 KB
Chasis 1 (Master).vi ‏85 KB

Hi,
It looks like you are using a 9074 chassis and two 9144 chassis, all three full with Modules and you are trying to read all the IO channels in one scan?
First of all, if you set your scan engine speed for the controller (9074), then you have to synchronize your Timed Loop to the Scan Engine and not to use a different timebase as you do in your scan VI.
Second the best performance can be achieved with I/O variables, not shared variables and you should make sure to not allocate memory in your timed Loop. memory will be allocated if an input of a variable is not connected, like the error cluster for example or if you create Arrays from scratch as you do in your scan VI.
If you resolve all these Issues you can time the code inside your Loop to see how long it really takes and adjust your scan time accordingly. The 9074 does not have that much power so you should not expect us timing. 500 Hz is probably a good estimate for the max. Performance for 144 channels and depending on how much time the additional microstrain calculation takes.
The ECAT driver brings examples which show how to program these kinds of Apps. Another way of avoiding the variables would be the programmatic approach using the variable API.
DirkW

How do I virus scan my iMac with OS X

How do I virus scan my iMac with OS X?

Mac users often ask whether they should install "anti-virus" software. The answer usually given on ASC is "no." The answer is right, but it may give the wrong impression that there is no threat from what are loosely called "viruses." There is a threat, and you need to educate yourself about it.
1. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to log in to it remotely. That threat is in a different category, and there's no easy way to defend against it.
The comment is long because the issue is complex. The key points are in sections 5, 6, and 10.
OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect."
The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
The following caveats apply to XProtect:
☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
☞ It can easily be disabled or overridden by the user.
☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however.
For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking.
4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, and a technological fix is not going to solve it. Trusting software to protect you will only make you more vulnerable.
The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the scam artists. If you're smarter than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. How do you know when you're leaving the safe harbor? Below are some warning signs of danger.
Software from an untrustworthy source
☞ Software of any kind is distributed via BitTorrent, or Usenet, or on a website that also distributes pirated music or movies.
☞ Software with a corporate brand, such as Adobe Flash Player, doesn't come directly from the developer’s website. Do not trust an alert from any website to update Flash, or your browser, or any other software.
☞ Rogue websites such as Softonic and CNET Download distribute free applications that have been packaged in a superfluous "installer."
☞ The software is advertised by means of spam or intrusive web ads. Any ad, on any site, that includes a direct link to a download should be ignored.
Software that is plainly illegal or does something illegal
☞ High-priced commercial software such as Photoshop is "cracked" or "free."
☞ An application helps you to infringe copyright, for instance by circumventing the copy protection on commercial software, or saving streamed media for reuse without permission.
Conditional or unsolicited offers from strangers
☞ A telephone caller or a web page tells you that you have a “virus” and offers to help you remove it. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
☞ A web site offers free content such as video or music, but to use it you must install a “codec,” “plug-in,” "player," "downloader," "extractor," or “certificate” that comes from that same site, or an unknown one.
☞ You win a prize in a contest you never entered.
☞ Someone on a message board such as this one is eager to help you, but only if you download an application of his choosing.
☞ A "FREE WI-FI !!!" network advertises itself in a public place such as an airport, but is not provided by the management.
☞ Anything online that you would expect to pay for is "free."
Unexpected events
☞ A file is downloaded automatically when you visit a web page, with no other action on your part. Delete any such file without opening it.
☞ You open what you think is a document and get an alert that it's "an application downloaded from the Internet." Click Cancel and delete the file. Even if you don't get the alert, you should still delete any file that isn't what you expected it to be.
☞ An application does something you don't expect, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
☞ Software is attached to email that you didn't request, even if it comes (or seems to come) from someone you trust.
I don't say that leaving the safe harbor just once will necessarily result in disaster, but making a habit of it will weaken your defenses against malware attack. Any of the above scenarios should, at the very least, make you uncomfortable.
6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it—not JavaScript—in your browsers.
Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.
Stay within the safe harbor, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.
7. Never install any commercial "anti-virus" (AV) or "Internet security" products for the Mac, as they are all worse than useless. If you need to be able to detect Windows malware in your files, use one of the free security apps in the Mac App Store—nothing else.
Why shouldn't you use commercial AV products?
☞ To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. This technique is a proven failure, as a major AV software vendor has admitted. Most attacks are "zero-day"—that is, previously unknown. Recognition-based AV does not defend against such attacks, and the enterprise IT industry is coming to the realization that traditional AV software is worthless.
☞ Its design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere. In order to meet that nonexistent threat, commercial AV software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
☞ By modifying the operating system, the software may also create weaknesses that could be exploited by malware attackers.
☞ Most importantly, a false sense of security is dangerous.
8. An AV product from the App Store, such as "ClamXav," has the same drawback as the commercial suites of being always out of date, but it does not inject low-level code into the operating system. That doesn't mean it's entirely harmless. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
An AV app is not needed, and cannot be relied upon, for protection against OS X malware. It's useful, if at all, only for detecting Windows malware, and even for that use it's not really effective, because new Windows malware is emerging much faster than OS X malware.
Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else. A malicious attachment in email is usually easy to recognize by the name alone. An actual example:
London Terror Moovie.avi [124 spaces] Checked By Norton Antivirus.exe
You don't need software to tell you that's a Windows trojan. Software may be able to tell you which trojan it is, but who cares? In practice, there's no reason to use recognition software unless an organizational policy requires it. Windows malware is so widespread that you should assume it's in everyemail attachment until proven otherwise. Nevertheless, ClamXav or a similar product from the App Store may serve a purpose if it satisfies an ill-informed network administrator who says you must run some kind of AV application. It's free and it won't handicap the system.
The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have all the disadvantages mentioned in section 7.
9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
10. As a Mac user, you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither can you assume that you will always be safe from exploitation, no matter what you do. Navigating the Internet is like walking the streets of a big city. It's as safe or as dangerous as you choose to make it. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.

NI Scan Engine Wont Run

Hello, I am trying to deploy a program on the real time controller of a compactRIO. I decided to use scan mode for now. However, when I try to run my VI I get the following error:
One or more items in this deployment require the NI Scan Engine and corresponding I/O driver(s) to be installed. Go to MAX to install.
If you continue to encounter this conflict, refer to the "Deploying and Running VIs on an RT Target" topic in the LabVIEW Help for information about resolving target deployment conflicts.
I have LabVIEW real time on my machine so I don't know what the reason for this is and I can not find under MAX where to install the scan engine (again I assume it is already installed).
I am using LabVIEW 8.6.1 and the modules I use on my cRIO-9073 are the 9477 DO module and the 9205 AI module. Any help would be appreciated.
Solved!
Go to Solution.

if I tried to install the software software at the NI Max
but it give error
"The selected target does not support this function"
how to fix this error,
what problem with it
thank you
Msyafiq
Attachments:
install error.jpg ‏128 KB

Scan Engine power up time

We have supplied a customer with a Labview/cRIO system.
There is a realtime program running with the Scan Engine, and a UI on the host.
Everything is working fine except for that they are
observing very long powerup times, in the 2 minute range. In particular, after
being powered off for several days, it take 4 minutes. Part of the time is
because of the Ethernet extender modems which take 35-40 seconds to connect
with each other.
I have ran some tests here, without the modems, and have
observed that after applying power:
1. I can ping the controller after 5 seconds.
2. The system is operational after 35-40 seconds. This was
measured both by the user interface being able to read Shared Variables, and
the System manager reconnecting and reading Shared Variables. I let it sit
overnight and this time went up to 50 seconds, so there does appear to be a
correlation between how long it was powered down and how long it takes to power
up.
I searched the NI forums but couldn’t find any discussion on
this. Does anyone have any ideas?

Hey pjackson59,
Quite a strange problem I must agree! Here's some of my ideas for you to try...
1) In the Distributed System Manager, navigate to the cRIO on the network. Choose NI_SystemState >> Memory >> Available (you may also want to take note of the values for the other three variables there as well). Notice that when you click on that a Trend Line appears on the right. Leave this up and running overnight and check it in the morning. If the trend line is going down, this means you're losing available memory and could have a memory leak in your realtime VI, which could effect startup time.
2) In MAX, find the cRIO under Remote Systems and click on the System Settings tab. Under the System Monitor section, take note of the Free Drive Space. If this value gets smaller and smaller over time, say dangerously close to no free disk space, then it's definitely possible it could be affecting start-up time.
3) Ethernet communication is at the lowest priority on a real-time system. That being said, if your real time VI is doing some hardcore processing, especially more and more as time goes on, then the CPU isn't going to publish data out the Ethernet port as regularly as it should be. This would explain why reading those shared variables takes a long time to update.
4) You could have a combination of the three things, in which case you'll probably (unfortunately) need to resort to some more intensive debugging and troubleshooting techniques - i.e. using the Real-time Execution Trace Toolkit
Rory

How to simulate cRIO

Hello,
I'm trying to find out how to simulate cRIO in LabVIEW. I found another thread about this, but I am using the cRIO just as a chassis/DAQ not the FPGA or RTOS, basically just like a cDAQ. I've downloaded and installed NI-RIO, but when I go into MAX to set up a Simulated NI-DAQmx device, I have no option for cRIO, I see cDAQ there. I need to set up with a cRIO-9074 chassis
much thanks!

Hello Monse,
That is correct- a RIO is a completely separate standalone device with its own OS that you can cross-compile code for and deploy to (and then communicate with once running). DAQ devices are tethered and controlled by the DAQmx driver on the local machine and can be simulated via this driver. You can certainly develop code without the physical RIO present- just add the model to a LabVIEW project and add the modules you intend to use to the chassis. All of your variables will be present, you just won't be able to deploy the hardware configuration or interface with the RIO. Most RT code can be run on Windows (to validate logic, if not timing), and the FPGA can be simulated, so you should be able to get pretty far without a physical controller.
How do you intend to use the RIO? What aspect of the hardware do you need to simulate for code development? It sounds as though your end goal is to access Scan Engine variables without deploying any RT code or configuring the FPGA at all, is that correct? If this is the case, then all you would need to do to simulate these channels would be to deploy equivalent Network-Published Shared Variables for testing and then re-link the deployed libraries once you have the hardware.
I hope that's helpful- if you could specify what in particular you are trying to achieve at this time (end result and what you are trying to achieve via simulation right now) as well as why you chose this hardware platform, I and others on the forum may be able to offer more specific advice.
Regards,
Tom L.

How to prevent cRIO Scan Engine Warning 66030

Similar Messages

Maybe you are looking for