Preventing false trigger in S series Device

I have a PXI 6133 and currently have a task set up to begin with an analog edge trigger, however the line experiences a fair bit of noise due to solenoid power lines. I know that some other devices are able to use the minimum pulse width option in the daqmx triggering property nodes, but as far as i can tell S series devices don't. Does anyone know of a work around for this.

Hi fchacon,
One approach may be to reduce the environment-induced noise in your system. The Field Wiring and Noise Guide and these Five Tips could be a good starting point for you.
Another possible option is using an Analog Edge Reference Trigger that accounts for the noise in your system. This may allow you to set a trigger higher than the desired level, but incorporates the noise from our environment.
Briana C.
Applications Engineer
National Instruments
ni.com/support

Similar Messages

Can any one suggest me how to use drawPixels method for 40 series devices

Hello!
I am using drawPixels method of DirectGraphics class the code I have written is :-
Image offscreen=DirectUtils.createImage(width,height,0x00000000);// width and heights are integer value
public final int MODEL=DirectGraphics.TYPE_INT_8888_ARGB ;
Graphics offgra = offscreen.getGraphics();
DirectGraphics directgraphics = DirectUtils.getDirectGraphics(offgra);
directgraphics.drawPixels(imgData,false,0,width,0,0,width,height,0,MODEL); // imgData is a int array(int imgData[]) which contains required pixels of image.
The above code is working fine with NOKIA 60 series device but when i use it with NOKIA 40 series device it gives java.lang.IllegalArgumentException.
same time if i use :-
directgraphics.drawPixels(imgData,false,0,width,0,0,width,height,0,DirectGraphics .TYPE_USHORT_4444_ARGB ) ;
// imgData is a short array(short imgData[]) which contains required pixels of image. i have used different formet here.
it works fine with 40 series device,
can any one suggest me how to use drawPixels method for 40 series devices with format
DirectGraphics .TYPE_INT_8888_ARGB .

If Remote wipe is activated it can't be undone. And Once the Wipe is done, the device can nö longer be tracked.
Sorry.

Synchronizing AI and Counter Tasks in DSA and M Series devices

Hello DAQ fellows, I am new in the Counter field, so it would be really helpful to have your comments and advices about my application.
I need to acquire simultaneouslythe following signals:
- AI Voltage signal with a DSA device (PXI 4461).
- AI voltage signal with a M Series device (PXI 6250).
- Periods between TTL pulses signal with one counter of the same M Series device. I want to use the counter as it is shown in the figure 7-8 attached below.
You can see my approach in the vi attached below (4461-6250ai-6250Ctr.vi). The 4461 is the master device.
For the synchronization between both AI tasks I am using the "SampleClockTimebase" of the master device as a source for the 6250. I am also using the "StartTrigger" signal from the master device to trigger the start of the AI acquisition in the 6250. As I understand, this configuration is OK.
Now come the second stage, which is to include the Ctr task to the acquisition process. I am creating the 3 tasks previously with another vi, the vi which creates the counter task (CreateTask6250Ctr.vi) is also attached. Now in the measurement vi (4461-6250ai-6250Ctr.vi), I use the "SampleClock" of the 6250-AI task in order to synchronize the AI with the Ctr task (I am not sure that this is the proper way to do this). Then I ask the "CounterTimebase.Source" in order to know which one is been used as SOURCE signal for the tick counting between the TTL pulses. Finally, I use the same "StartTrigger" signal from the master device to trigger the start of the Ctr task. In this way, when the AI task from the 4461 is started, it give the "StartTrigger" signal to the AI and Ctr tasks from the 6250 and the 3 start at the same time.
What do you think. am I right with my approach?
Is the Ctr task properly created to use the counter as in figure 7-8?
Are the three tasks properly synchronized?
Which other options do I have in order to synchronize the Ctr task with the other 2?
Thanking in advance,
Cristián
Attachments:
4461-6250ai-6250Ctr.vi ‏1561 KB
Fig 7-8 from M SeriesUserManual.jpg ‏16 KB
CreateTask6250Ctr.vi ‏35 KB

Could I also use the PXI_Clk10 as a "ReferenceClock.Source" for the three tasks in order to synchronize them? I mean, instead of using the "SampleClock" of the AI task of the 6250 and the Ctr tasks of the same device. See the attachment to see what I mean.
Greetings,
Cristián
Attachments:
4461-6250ai-6250Ctr - PXI_Clk10.vi ‏1558 KB

Self made trigger for third party device?

Hi, everyone! I am new to labview programming.
Recently I have been trying to realize a function to trigger(or start) the third party device to do acquisition. I want to use the DAQmx to acquire one channel signal(which is continous pulse signal). And use this DAQmx acquired signal to trigger the third party device. I want each pulse signal to start the third party device to do acquisition.
Could someone give me some advice or suggestions? I would be grateful for any of your help. Thanks in advance.

Hi, Lynn
Thank you very much. I am glad to get your reply. First I am sorry for my lack of knowledge of Labview. I will learn and be more careful of using the terminology.
I have "NI PCI-6052E" as the hardware device. And I use "BNC-2120" connector block to connect the trigger source. I useonly one channel of 6052E to acquire the signal. This trigger signal actually is periodic pulse signal of voltage ranging from 0 to 5V. The pulse voltage is 0V, all other are 5V.
I give my answers to your questions as followings.
What kind of signal does the third party device require for triggering?Is it a physical signal like a voltage or current?
The third party device actually doesn't have to use this pulse trigger to start, I just want to make a customized trigger to sync the third party device with the pulse signal. And each pulse make the device start working. This pulse trigger is a voltage signal that can be linked to 6052E by BNC connectors.
Is it a message transmitted via USB, Ethernet, or tin cans and a string?
I am sorry, I don't get this. I guess it transmitted by BNC.
What is the timing of the signal you are acquiring?
I used the sample clock in DAQmx timing function.
How much latency can you tolerate between the acquired signal and the trigger to the third party device?
I actually can control the interval time between each pulse. I require this interval time to be more than 1s and during this time the third party device can do acquisition itself. So the latency I think should be in the range of ms.
Do you need to do any signal processing or analysis on the acquired signal to generate the trigger?
The trigger signal is pulse signal. Actually I don't know much about signal processing, I don't know what kind signal is better for my application. If you have any better idea, please let me know.
Thanks a lot.
Yu

IPS SSP module vs standalone 4200 series devices

Looking at price to performance ratio it seems that the IPS SSP modules are the winner.
The 4200 series devices however has hardware bypass which can ensure traffic flow is not interrupted even if the power to the IPS goes down. How likely is it that a malfunction of the IPS SSP affects the work of the ASA?
We are looking at ASA5585X S20 with IPS SSP S20 or same ASA with IPS 4260.
Any and all input in terms of pros and cons you are aware of will be appreciated.

Yes, you can have the IDSM2 module in your CAT 6K. However, please check how much traffic will be traversing the IDSM2 module since you mention internal as well as traffic towards the internet. Please ensure that the performance of the internal traffic is not impacted. Also depends on whether you will be configuring the IPS in promiscuous or inline mode.
Here is the datasheet for IDSM2:
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_data_sheet09186a00801e55dd.html
You might even want to bundle a few IDSM2:
http://www.cisco.com/en/US/prod/collateral/modules/ps2706/ps5058/product_data_sheet0900aecd804b91d7.html
Hope that helps.

Is the AT-MIO-16DE-10 an E series device?

I'm trying to reinstall labview and I'm not sure which option to select. The choices are the recommended one, the one for all non-E series devices, and neither, and there's a note at the bottom for which devices should use neither.

The AT-MIO-16DE-10 is an E Series device. Thus, I would pick the "recommended one" because that seems to apply to the E Series boards which are the regular boards produced by NI.
If you still have troubles, let me know what version of LV you are trying to reinstall.
L Aguila
Applications Engineer
National Instruments

SCB-68 Reference Label for M series devices

What's the difference between the SCB-68 Reference Label M series devices connector 0 and connector 1? I'm installing a NI PCI-6221-M series Multifunction DAQ and the SCB-68 connector block, and I don't know how to make the physical connections. With the SCB-68 kit, I received the Reference Label for the E-series devices. In the NI site, there is info about the connector 0, but what is the connector 0 and connector 1?
Thanks,
ZeK

Good question Zek. The M series family uses a smaller version of the 68-pin connector used on E series so that two connectors can be located on the same board. The second connector is available on certain M seriies boards in order to provide connectivity to additional channels. In the case of the 6221, there is only one connector.
The 6221 is fully compatible with the SCB-68. The following link provides a revised version of the SCB-68 label adapted for M Series devices:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/61ed77983ad7cca386256f66008215f1/$FILE/SCB68%20M%20Series%20Connector%200.pdf
For pinout specific to a particular M Series device, you can refer to the M series help available at either one of the following locations:
http://digital.ni.com/manuals.nsf/websearch/9477D6DF1FE5A72986256FAB00633DE4?OpenDocument&node=132100_US
http://digital.ni.com/manuals.nsf/websearch/3AE9D4533E03A6EF86256FE300809FE6 (HTML format)

Qualified Disks for px-Series Devices

Note: The following information pertains only to px-Series network devices. If you have any other StorCenter network device, including ix-Series devices, this does not apply to you.
Before adding new hard drives to your StorCenter px-Series network device, please be sure to familiarize yourself with the following information. If you still have any additional questions about this topic, feel free to post them below.
Supported Drives:
For the current list of drive brands and models that have been tested with the StorCenter px devices and are supported for use, please visit https://iomega-na-en.custhelp.com/app/answers/detail/a_id/26012. Our approved hard drive list is still growing! Please check back with the list often or subscribe for updates by clicking on the "Notify Me" button on the above link.
Important: All disks within a single storage pool must meet the following requirements:
Same manufacturer
Same rotational speed
Same capacity
Failure to meet these requirements may result in unpredictable device behavior and will not be supported by Iomega. If you need technical assistance, please be prepared to backup your data and remove any unsupported drives or configurations.
Pre-Installed Drives:
If you purchased your px device either fully or partially populated with drives, the device’s operating system resides partially on the drives. To replace all of the drives from the original configuration, follow the steps here: https://iomega-na-en.custhelp.com/app/answers/detail/a_id/27190

What model px4 do you have? Version 4.0.8.23976 is the latest LifeLine firmware release for the px2-300d and px4-300d network storage devices while Version 4.1.4.24001 is the latest for the px4-400d.
There is not any supported way to disable or restrict the services you are referring to. Debian is the operating system of the device so it would not be able to disable that unless by turning the device off.
Apache is the web interface of our devices so if you disable Apache you will not be able to access the web management console and would have to do any configuration by SSH at that point. It might be able to disable Apache if you really wanted to, but the device may just restart the service after disabling it as it is a main function of the device.
I'm not sure about OpenSSL and PHP, but if you are concerned about the Heartbleed bug, it only affects the px4-400d and px4-400r. Please see the following release from Lenovo: OpenSSL Heartbleed security vulnerability
Have questions and need answers?
Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
LenovoEMC Support & Downloads
LenovoEMC North America Support Contact Page

Digital trigger to start other device

Hello can anyone help me create Vi to generate digital trigger to start another device. I have agilent u2531A measure card and LabView 2010, and want to generate digital trigger to start generate signal on Rigol 4000 generator.

Ok, here is a possible solution to your problem. But I am not sure it will work properly so please give me some feedback. Also, as you will see, I set a sine wave as a defaut output signal from Rigol DG4000.
To have the functions I used for your devices, you have to install the appropriate drivers: LabVIEW>Help> Find Instruments Drivers then select the manufacturer and select the driver from the list.
Besides, note that we usually do not support customer for the Rigol device.
I hope the attached file will work for you.
Tamara Moullet
National Instruments
Attachments:
AgilentTrigger_RigolGen.vi ‏31 KB

Will ni-daq drivers for an E-series device work under WinXP?

I now use them to program the device using Visual C++ under win 98.

Hello
NI-DAQ 6.9.3 does provide support for XP and 98, so you most certainly can use it in XP with an E-series device.
Thanks
Bilal Durrani
NI
Bilal Durrani
NI

Maemo / MeeGo for N series devices?

Hi,
is there a chance Nokia offers an update of N series devices like the N97 to Maemo / MeeGo? I think this would offer a whole new world of software to these devices. I am pretty sure one or the other engineer has already played with this idea in his lab

It's not possible and it won't happen ! I would think there is a good chance we may get a tiny overspill from Symbian^3, but that's the best you can hope for, the N97 has neither the memory or the processor speed to perform much better. More likely that memory management may be improved in later updates and would think there will be at least another 12 months support from Nokia, but that's about it. That said, it's only my opinion , but I wouldn't hold your breath !
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution'

Analog start trigger for x series card gives an error?

Hi everyone,
I am having some trouble setting up an analog start trigger for DAQ using an x series PCIe card (6351)... Attached is my configuration... After reading the manual (http://digital.ni.com/manuals.nsf/websearch/08B4B2E1B5373B94862579BA006E6BAB), my understanding is that AFPI0 is a compatable analog trigger for the device; however, the vi will not run and I get an error... Although if I change the soruce to "Force" (which is ai0) it works..
Also, the device document says (pg 11-8):
"To improve trigger accuracy, do the following:
• Use an AI channel (with a small input range) instead of APFI <0,1> as your trigger source. The DAQ device does not amplify the APFI <0, 1> signals. When using an AI channel, the NI-PGIA amplifies the AI channel signal before driving the analog trigger circuitry. If you configure the AI channel to have a small input range,"
To me, this implies that I probably should use "Force" as the trigger soruce anyway (note that the instrunment is used to acquire data load cell data generated from human muscle contractions; so slew rates are relatively low compared to signals acquired from industrial tests).
Could someone please comment on these issues for me?
Regards,
Jack
LV2010
Attachments:
Untitled 1.vi ‏22 KB

Ok... I think I have answered by own question... APFI0 needs a low impedence signal to drive the terminal... I mistakenly thought this was an internal terminal or trigger...
So I should stick with using the first analog signal acquired in my DAQ device (e.g. ai0) as the trigger source?
Regards,
Jack
LV2010

Q: Re: Q: Acquiring data using two E series devices connected by RTSI and streaming data to disk

<< (My first posting)
I use two E series PCI Cards, connected by RTSI. I'd like to stream the data
from both cards to a binary file and to add a header to it.
I also need to somehow read (plot) the stored data, this with another VI.
The whole should be then integrated into an existing program, that used just
one acquisition card.
Till now I have tried to combine "Two E-series Shared ScanClk.vi" and "High
Speed Data Logger.vi" into another VI, and I have tried to read the stored
data with the "High Speed Data Reader.vi". The problem is that I fight with
one error after another, what prevents me from going further.
I use LabView 6.1, under Windows 2K.
Has somebody by chance already done something similar and would agree to
share with me their experience? TIA for any suggestion.
Regards,
Victor Manta
>>
"Ben" wrote in message
news:[email protected]...
> Hi Victor,
>
> I have done a lot of similar work.
>
> Exactly what did you try and what specific errors did you encounter?
>
> What you are trying is do-able provided the hardware you have suuports
> it.
>
> Please post (both here and to the DAQ group)
> the details of the hardware you are using,
> versions of software being used,
> Examples that you are using,
> error codes that occured,
> posibly post example code showing the problem.
>
> Ben
Hi Ben,
I use two PCI-MIO-16E-1 cards, connected by RTSI. I'd like to stream the
data from both cards in real time to a binary file, after having added a
header to it.
For tests, on the channel 0 of each card is applied the same square wave,
100 Hz.
Yes, the hardware support RTSI. I use LabView 6.1.
Till now I have:
1. Combined the "Two E-series Shared ScanClk.vi" and the "High
Speed Data Logger.vi" into a DAQ VI. To do this, I have "doubled" and
adapted the "High Speed Data Logger.vi". For testing purposes the data are
stored in two files, always the same ones (the old ones being overwritten
after each acquisition).
2. "Doubled" and adapted "High Speed Data Reader.vi" into another VI, for
reading from both files, mentioned earlier.
What already works:
- The headers for both files are correctly stored (VI point 1.)
- The acquired data from the first card (device 1) are correctly stored (VI
point 1.)
- The VI (point 2.) that reads both files and displays the results works
What doesn't work:
- The acquired data from the second card aren't stored at all (VI point 1.)
- An error message says: "Error -10608 occurred at AI Buffer Read. Possible
reason: NI-DAQ LV: No transfer is in progress for the specified resource."
I think that I understand this message, but I don't know how to continue.
The DAQ VI can be downloaded from (please click the link, then the link on
that page; about 100K, zipped):
http://www.swissheartnet.unibe.ch/labview.htm
Thanks a lot in advance.
Regards,
Victor Manta
PS. I don't know which DAQ group you mean.

"Filipe A." wrote in message
news:[email protected]...
> Victor;
>
> You can definitely accomplish that task with the DAQ boards you have
> and Labview.
>
> It would be good if you could be more specific as far as what type of
> errors you are seeing and how you are integrating both VIs.
>
> Regards
> Filipe A.
> Applications Engineer
> National Instruments
Maybe Mr. Filipe A. could help me? Please see below, and TIA.
Regards,
Victor Manta
"Victor Manta" wrote in message
news:[email protected]...
> << (My first posting)
> I use two E series PCI Cards, connected by RTSI. I'd like to stream the
data
> from both cards to a binary file and to add a header to it.
>
> I also need to somehow read (plot) the stored data, this with another VI.
>
> The whole should be then integrated into an existing program, that used
just
> one acquisition card.
>
> Till now I have tried to combine "Two E-series Shared ScanClk.vi" and
"High
> Speed Data Logger.vi" into another VI, and I have tried to read the stored
> data with the "High Speed Data Reader.vi". The problem is that I fight
with
> one error after another, what prevents me from going further.
>
> I use LabView 6.1, under Windows 2K.
>
> Has somebody by chance already done something similar and would agree to
> share with me their experience? TIA for any suggestion.
>
> Regards,
> Victor Manta
> >>
>
> "Ben" wrote in message
> news:[email protected]...
> > Hi Victor,
> >
> > I have done a lot of similar work.
> >
> > Exactly what did you try and what specific errors did you encounter?
> >
> > What you are trying is do-able provided the hardware you have suuports
> > it.
> >
> > Please post (both here and to the DAQ group)
> > the details of the hardware you are using,
> > versions of software being used,
> > Examples that you are using,
> > error codes that occured,
> > posibly post example code showing the problem.
> >
> > Ben
>
> Hi Ben,
>
> I use two PCI-MIO-16E-1 cards, connected by RTSI. I'd like to stream the
> data from both cards in real time to a binary file, after having added a
> header to it.
>
> For tests, on the channel 0 of each card is applied the same square wave,
> 100 Hz.
>
> Yes, the hardware support RTSI. I use LabView 6.1.
>
> Till now I have:
>
> 1. Combined the "Two E-series Shared ScanClk.vi" and the "High
> Speed Data Logger.vi" into a DAQ VI. To do this, I have "doubled" and
> adapted the "High Speed Data Logger.vi". For testing purposes the data are
> stored in two files, always the same ones (the old ones being overwritten
> after each acquisition).
>
> 2. "Doubled" and adapted "High Speed Data Reader.vi" into another VI, for
> reading from both files, mentioned earlier.
>
> What already works:
>
> - The headers for both files are correctly stored (VI point 1.)
> - The acquired data from the first card (device 1) are correctly stored
(VI
> point 1.)
> - The VI (point 2.) that reads both files and displays the results works
>
> What doesn't work:
>
> - The acquired data from the second card aren't stored at all (VI point
1.)
> - An error message says: "Error -10608 occurred at AI Buffer Read.
Possible
> reason: NI-DAQ LV: No transfer is in progress for the specified resource."
>
> I think that I understand this message, but I don't know how to continue.
>
> The DAQ VI can be downloaded from (please click the link, then the link on
> that page; about 100K, zipped):
>
> http://www.swissheartnet.unibe.ch/labview.htm
>
> Thanks a lot in advance.
>
> Regards,
>
> Victor Manta
>
> PS. I don't know which DAQ group you mean.

Q: Acquiring data using two E series devices connected by RTSI and streaming data to disk

I use two E series PCI Cards, connected by RTSI. I'd like to stream the data
from both cards to a binary file and to add a header to it.
I also need to somehow read (plot) the stored data, this with another VI.
The whole should be then integrated into an existing program, that used just
one acquisition card.
Till now I have tried to combine "Two E-series Shared ScanClk.vi" and "High
Speed Data Logger.vi" into another VI, and I have tried to read the stored
data with the "High Speed Data Reader.vi". The problem is that I fight with
one error after another, what prevents me from going further.
I use LabView 6.1, under Windows 2K.
Has somebody by chance already done something simi
lar and would agree to
share with me their experience? TIA for any suggestion.
Regards,
Victor Manta

<< (My first posting)
I use two E series PCI Cards, connected by RTSI. I'd like to stream the data
from both cards to a binary file and to add a header to it.
I also need to somehow read (plot) the stored data, this with another VI.
The whole should be then integrated into an existing program, that used just
one acquisition card.
Till now I have tried to combine "Two E-series Shared ScanClk.vi" and "High
Speed Data Logger.vi" into another VI, and I have tried to read the stored
data with the "High Speed Data Reader.vi". The problem is that I fight with
one error after another, what prevents me from going further.
I use LabView 6.1, under Windows 2K.
Has somebody by chance already done something similar and would agree to
share with me their experience? TIA for any suggestion.
Regards,
Victor Manta
>>
"Ben" wrote in message
news:[email protected]...
> Hi Victor,
>
> I have done a lot of similar work.
>
> Exactly what did you try and what specific errors did you encounter?
>
> What you are trying is do-able provided the hardware you have suuports
> it.
>
> Please post (both here and to the DAQ group)
> the details of the hardware you are using,
> versions of software being used,
> Examples that you are using,
> error codes that occured,
> posibly post example code showing the problem.
>
> Ben
Hi Ben,
I use two PCI-MIO-16E-1 cards, connected by RTSI. I'd like to stream the
data from both cards in real time to a binary file, after having added a
header to it.
For tests, on the channel 0 of each card is applied the same square wave,
100 Hz.
Yes, the hardware support RTSI. I use LabView 6.1.
Till now I have:
1. Combined the "Two E-series Shared ScanClk.vi" and the "High
Speed Data Logger.vi" into a DAQ VI. To do this, I have "doubled" and
adapted the "High Speed Data Logger.vi". For testing purposes the data are
stored in two files, always the same ones (the old ones being overwritten
after each acquisition).
2. "Doubled" and adapted "High Speed Data Reader.vi" into another VI, for
reading from both files, mentioned earlier.
What already works:
- The headers for both files are correctly stored (VI point 1.)
- The acquired data from the first card (device 1) are correctly stored (VI
point 1.)
- The VI (point 2.) that reads both files and displays the results works
What doesn't work:
- The acquired data from the second card aren't stored at all (VI point 1.)
- An error message says: "Error -10608 occurred at AI Buffer Read. Possible
reason: NI-DAQ LV: No transfer is in progress for the specified resource."
I think that I understand this message, but I don't know how to continue.
The DAQ VI can be downloaded from (please click the link, then the link on
that page; about 100K, zipped):
http://www.swissheartnet.unibe.ch/labview.htm
Thanks a lot in advance.
Regards,
Victor Manta
PS. I don't know which DAQ group you mean.

If you have multiple devices on the find my iphone how do you prevent someone from accessing those other devices if your device is stolen

I have set up the find my iphone app to be hooked up to my phone, computer, ipod and my family's devices. Thru the find my iphone app you can delete the hard drive of any device to keep a theif from getting your personal information. But lets say my phone is stolen, is there a way of preventing the person who stolen my phone from being able to delete the information on my computer?

Welcome to the Apple Community.
Your device should have it's screenlock enabled so that this can't happen, but if you haven't set a screenlock, then yes someone could do this.

Preventing false trigger in S series Device

Similar Messages

Maybe you are looking for