DASYLab 13 // Set t to 0 at triggerevent

Hello Everyone,
I am trying to measure the preasures that occur when an Airbag deploys.
The measurment works great but i have the following problem:
When my trigger signal (Which is on an Analog input of a OMB-DAQ-3000 Unit) is triggering the measurment 30 seconds after i started the measurement my first data point will be at t=30 seconds.
Is there a possibility to set t=0 at the point of the trigger event? or is there an option to set a counter that starts with the trigger that i could just save with my measured data?
And just FYI i cant restart the measurement on trigger becaurse there is a Save file as... box implementet on programm start.
I hope someone can help me.

What you need to do is to set a counter for time for TTL high and add it as a channel.
Then put a trigger at the counter to trigger when input is above 30 seconds and that trigger will connect to an action that is set for "Measurement: Stop/Restart".
This will restart your app at after 30 seconds you started the trigger. Obviously, you can use this action in any way you need it.
Tom Rizzo
InSyS Corp.
www.insyscorp.com
Your DASYLab integrator

Similar Messages

How do I control a servo-valve to open and close with Dasylab?

I am currently using a servo-valve to run an endurance test and would like to control it to open a close at a set frequency rate and set pressure rate (6000psi). Is there a controller that I can use to do that? I am using Dasylab with a NI Daq board and I get the pressure and flow readings from the analog to digital signals correctly but to actually control a servo which is powered with and external power supply to provide 25VDC.

It would be unwise to use DASYLAb to close a loop on a servovalve.
The best way to do that would be to buy a analog PID controller board, MOOG and Parker sells those, and use an anaqlog output from the NI card to controll it.
We did many tests using this way.
There are also other option like servo-controllers that could perform many tasks, like FG, conditioning, limits, and profiles and then use DASYLAb for Data acquisition.
The price for this solution would be of course higher.
Tom Rizzo
InSyS Corp.
www.insyscorp.com
Your DASYLab integrator

How to lookup a value in a 2D array from an Excel file - Dasylab version 12 Pro

Hi, I am new to this forum and am looking for some advice on a worksheet I'm trying to construct. I have an Excel spreadsheet that is basically a 2D array, and I want to use Dasylab v12 Pro to be able to import a value from this array based on user selections from within the Dasylab worksheet.
Column A lists 200+ diesel engine models. I've shown 9 in my Excel attachment...one model per row (shaded in yellow), and each engine model can be run at several speeds (shaded green in columns B thru F). For an engine in a given row, combined with a chosen operating speed gives you a corresponding horsepower (blue shading).
I have this Excel sheet saved somewhere on my C:/ drive, and what I want to do is when the user starts the Dasylab worksheet he will select from a drop drown menu to choose the engine model (ie A, B, C, etc) and another drop down menu to choose the speed (ie 1470, 1760, etc). I know that I can make a drop down menu with a Coded Switch within Dasylab, however it seems only 16 choices can be made from each switch, so for my 200 engine models I will need 13 switches! I know I can assign a text description like "Engine A" to a numerical value within that coded switch. Somehow I need to take those two selections made within the Dasylab experiment, and read this Excel file (ie my database of all of these 200 diesel engine models) as a 2 dimensional array by row and column to spit out the data value (the blue numbers) back into Dasylab.
The goal is to take the engine model, speed, and the horsepower obtained from the array search and write these to an .asc file that I will create a running log of this data. So, after the test page is run 50 times it will have 50 rows of data containing these 3 parameters. There is some other test data taken from my data acquisition that goes along with this, however that's not part of my 2D array predicament.
I'm taking a guess that I need to do something with global strings & variables, and some how import them and export them with an ODBC in/out module. This is something I've just never worked with before so I am a bit lost. Obviously I can just make the user type in the engine model and speed as a startup parameter at the start of the test and save that to a variable or string, but I want to make it idiot proof so that the two selections (ie row and column) can be chosen from a pre-set list and will yield my data value. Everything else related to Dasylab I am pretty proficient with.
Thanks,
Mike
Attachments:
engine 2D array.xlsx ‏10 KB

This would be the best way.
Also, with version 13 they started using Phyton to create custom modules that can be programmed in DASYLab.
We arte learning this right now and I know that you can use standard message dialogs with that as well.
I would suggest to you to download a demo of V13 and take a look at the Pyton module.
Also, usually DASYLab system intgretors like us, can provide services also on things like this including Excel programming for pre and post analisys
Tom Rizzo
InSyS Corp.
www.insyscorp.com
Your DASYLab integrator

How to set a default start and/or end date for New Events based on trigger date.

I'm using the CalendarActivityListener to get current row when clicking on an existing event. As per previous posts this listener gives you access to event detail including Start Date, End Date, etc.
However, what I want to do is to default the start (and end) dates for New Events based on the trigger date.
I've tried the CalendarListener and can grab the Trigger Date from it - however, I can't see a way to pass this directly to the popup/dialog I'm using to create the new event.
At present I'm putting the TriggerDate into the ADFContext session scope e.g. ADFContext.getCurrent().getSessionScope().put("TriggerDate",calendarEvent.getTriggerDate());
Then, I've tried multiple approaches to try and "get" the TriggerDate from session scope to drop it into my new Calendar Event basically, I'm trying to default the InputField(s) associated with the Start Date using the value from the session - I've tried
1. setting the default value for the InputField in the jspx using a binding expression i.e. value="#{sessionScope.TriggerDate}" - this actually sets the value appropriately when the jspx is rendered but, when I go to create I get a NPE and I can't debug. I assumed that it might be a Date type issue - it would appear that CalendarListener provides a date of type java.util.Date and that the StartDate attribute of my VO/EO/table is a DATE and therefore requires oracle.jbo.domain.Date so I tried casting it - to no effect
2. Using a Groovy expression *(StartDate==null?adf.context.sessionScope.TriggerDate:StartDate)* in my calendar's EventVO to default the Start Date to the same result
Any thoughts or ideas?

John,
Thanks for that suggestion - could not get it to work. However, I did manage a different approach. I finally determined the sequence of events in terms of how the various events and listeners fire (I think).
Basically, the CalendarActivityListener fires, followed by the listener associated with the Calendar object's Create facet, followed finally by the CalendarEventListener - the final is where the TriggerEvent is available and then finally, control is passed to the popup/dialog in the Create facet. So, my approach of trying to set/get the TriggerDate in the user's HTTP session was doomed to failure because it was being get before it had been set :(
Anyway, I ended up adding a bit of code to the CalendarEvent listener - it grabs the current BindingContext, navigates through the DCBindingContainer to derive an Iterator for the ViewObject which drives the calendar and then grabs the currently active row. I then do a few tests to make sure we're working with a "new" row because I don't want to alter start & end dates associated with an existing calendar entry and then I define the Start and End dates to be the Trigger Date.
Works just fine. Snippet from the listener follows
BindingContext bindingContext = BindingContext.getCurrent();+
*if ( bindingContext != null ) {*+
DCBindingContainer dcBindings = (DCBindingContainer) bindingContext.getCurrentBindingsEntry();+
DCIteratorBinding iterator = dcBindings.findIteratorBinding("EventsView1Iterator");+
Row currentRow = iterator.getCurrentRow();+
if ( currentRow.getAttribute("StartDate") == null)+
currentRow.setAttribute("StartDate", calendarEvent.getTriggerDate());+
if (currentRow.getAttribute("EndDate")==null)+
currentRow.setAttribute("EndDate", calendarEvent.getTriggerDate());+
*}*

I would like to use DasyLab for a research project with Siemens PLC

I would like to use DasyLab with Siemens PLC Simatic S7-300. Which OPC Server shall I use?
I would like a manual for connecting DasyLab via OPC server to the PLC if it is possible.
Could I use NI OPC Servers which are compatible with LabView?
Thank you for your help

I believe that Siemens has an OPC server that you can purchase.
KepWare has the KepServer and drivers for Siemens www.kepware.com.
DASYLab has the Help menu with the instructions for the OPC DA modules. It's straightforward - configure the OPC server with the necessary drivers and connections (tags). Update rates are in milliseconds, for example, 100 ms is typical. You need to know your device and driver, to determine data types.
Once configured, KepServer has an OPC quick client to allow you to test your settings.
Then, add the OPC DA module to DASYLab, connect to the server, and select the tags to read or write.
Note that it's simple to set up on a single computer - to set up on multiple computers requires assistance from your It team to correctly configure the DCOM permissions. That's specific to the OPC server.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

How to Set A Default Start Time For New Events In Calendar?

How to Set A Default Start Time For New Events In Calendar?

John,
Thanks for that suggestion - could not get it to work. However, I did manage a different approach. I finally determined the sequence of events in terms of how the various events and listeners fire (I think).
Basically, the CalendarActivityListener fires, followed by the listener associated with the Calendar object's Create facet, followed finally by the CalendarEventListener - the final is where the TriggerEvent is available and then finally, control is passed to the popup/dialog in the Create facet. So, my approach of trying to set/get the TriggerDate in the user's HTTP session was doomed to failure because it was being get before it had been set :(
Anyway, I ended up adding a bit of code to the CalendarEvent listener - it grabs the current BindingContext, navigates through the DCBindingContainer to derive an Iterator for the ViewObject which drives the calendar and then grabs the currently active row. I then do a few tests to make sure we're working with a "new" row because I don't want to alter start & end dates associated with an existing calendar entry and then I define the Start and End dates to be the Trigger Date.
Works just fine. Snippet from the listener follows
BindingContext bindingContext = BindingContext.getCurrent();+
*if ( bindingContext != null ) {*+
DCBindingContainer dcBindings = (DCBindingContainer) bindingContext.getCurrentBindingsEntry();+
DCIteratorBinding iterator = dcBindings.findIteratorBinding("EventsView1Iterator");+
Row currentRow = iterator.getCurrentRow();+
if ( currentRow.getAttribute("StartDate") == null)+
currentRow.setAttribute("StartDate", calendarEvent.getTriggerDate());+
if (currentRow.getAttribute("EndDate")==null)+
currentRow.setAttribute("EndDate", calendarEvent.getTriggerDate());+
*}*

DASYLAB QUERIES on Sampling Rate and Block Size

HELP!!!! I have been dwelling on DASYLAB for a few weeks regarding certain problems faced, yet hasn't come to any conclusion. Hope that someone would be able to help.Lots of thanks!
1. I need to have more data points, thus I increase the sampling rate(SR). When sampling rate is increased, Block size(BS) will increase correspondingly.
For low sampling rate (SR<100Hz) and Block size of 1, the recorded time in dasy and the real experimental time is the same. But problem starts when SR>100Hz for BS=1. I realized that the recorded time in dasylab differs from the real time. To solve the time difference problem, I've decided to use "AUTO" block size.
Qn1: Is there any way to solve the time difference problem for high SR?
Qn2: For Auto Block Size, Is the recorded result in dasylab at one time moment the actual value or has it been overwritten by the value from the previous block when AUTO BS is chosen.
2. I've tried getting the result for both BS=1 and when BS is auto. Regardless of the sampling rate, the values gotten when BS=1 is always larger than that of Auto Block size. Qn1: Which is the actual result of the test?
Qn2: Is there any best combination of the block size and sampling rate that can be used?
Hope someone is able to help me with the above problem.
Thanks-a-million!!!!!
Message Edited by JasTan on 03-24-2008 05:37 AM

Generally, the DASYLab sampling rate to block size ratio should be between 2:1 and 10:1.
If your sample rate is 1000, the block size should be 500 to no smaller than 100.
Very large block sizes that encompass more than 1 second worth of data often cause display delays that frustrate users.
Very small block sizes that have less than 10 ms of data cause DASYLab to bog down.
Sample rate of 100 samples / second and a block size of 1 is going to cause DASYLab to bog down.
There are many factors that contribute to performance, or lack there of - the speed and on-board buffers of the data acquisition device, the speed, memory, and video capabilities of the computer, and the complexity of the worksheet. As a result, we cannot be more specific, other than to provide you with the rule of thumb above, and suggest that you experiment with various settings, as you have done.
Usually the only reason that you want a small block size is for closed loop control applications. My usual advice is that DASYLab control is around 1 to 10 samples/second. Much faster, and delays start to set in. If you need fast, tight control loops, there are better solutions that don't involve Microsoft Windows and DASYLab.
Q1 - without knowing more about your hardware, I cannot answer the question, but, see above. Keep the block size ratio between 2:1 and 10:1.
Q2 - without knowing more about your hardware, and the driver, I'm not sure that I can fully answer the question. In general, the DASYLab driver instructs the DAQ device driver to program the DAQ device to a certain sampling rate and buffer size. The DASYLab driver then retrieves the data from the intermediate buffers, and feeds it to the DASYLab A/D Input module. If the intermediate buffers are too small, or the sample rate exceeds the capability of the built-in buffers on the hardwar, then data might be overwritten. You should have receive warning or error messages from the driver.
Q3 - See above.
It may be that your hardware driver is not configured correctly. What DAQ device, driver, DASYLab version, and operating system are you using? How much memory do you have? How complex is your worksheet? Are you doing control?
Have you contacted your DASYLab reseller for more help? They should know your hardware better than I do.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Command line STOP of Dasylab

Hi,
I'm trying to find a quick () way of stopping Dasylab from the command line e.g. from an external script file.
I can STOP Dasylab via a VB Windows based DDE utility (produced by NI/DasyTec), but I need the same degree of control from the command line.
I have several DDE command line utilities, namely TCMD.exe & CMCDDE.exe but none of these work with Dasylab ….even though they control other DDE servers without problem!
Any ideas??
Thanks,
Paul Towle.
Luk Leamington

Hello all.
This has now been solved .....thanks to Thomas Gebbert at Measx.com.
It only requires a Visual Basic Script file.
Place the following in a file (e.g. named 'Dasylab_STOP.vbs)' & execute from the command line or another script/batch file.
Regards all,
Paul T.
=========================================================================================
Start
Sub Start
'Nun alle weiteren Prozeduren/Funktionen hier aufrufen.
TastenSimulation 'Für DASYLab-Stop.
End Sub
Sub TastenSimulation
Dim WshShell
set WshShell = WScript.CreateObject("WScript.Shell")
'In Überschriftszeile steht immer u.a. ein DASYLab.
WshShell.AppActivate "DASYLab"
' Tastaturanschläge durchführen.
' 'Enter'-Taste = ~; 'STRG+F5'-Taste = ^{F5};
WshShell.SendKeys "~"
WshShell.SendKeys "^{F5}"
End Sub

DASYLAB/USB 2416 error, freezes

Hello everyone,
I'm running into an issue where the USB 2416 DAQ is freezing up, stuck in a state while it is outputting signals. I have worksheet where Dasylab is outputting two digital signal to turn on a physical relay, which in turn activates two solonoids. I'm using the TTL pulse module with a delay in order to cycle and alternate between the two solonoids. The trouble is, that the DAQ seemed to freeze up after five cycles. DASYlab is still working but DAQ is stuck on one of the cycles. I was able to get it working by changing the synchronization on TTL pulse module to DASYlab, which is set to 10 Hz (same as the output of the US 2416).
However, after closing DASYlab and restarting the worksheet, the DAQ gets stuck on 15 cycles. Any ideas on what is causing the issue? Is it timing/synchronization?
Thanks,
Rey

Rey,
This is very hardware specific. I am going to suspect that your timing is too fast for the device, and that the data is blocking.
Please call Measurement Computing or contact them through their web page at www.mccdaq.com.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Python script in dasylab using single input multiple output

Hello
For a project, I would like to use the python scripting module of dasylab 13. I got it to work for simple functions such as y=f(x), where i have one input and one output.
The next step in order to get to where i want to be with my script is using a single input and generating two outputs.
I defined it in the "predefined settings" that pops up first. The module created looked as it should, having one input and two outputs. However, when I wanted to edit the script (and double clicked the module) the module went back to having one input and one output.
I searched the help and found the section "channel assignment constants". There describe the various constants, which should have been set in predefined settings. In my case it is CR_1_2.
It also states to setup the meta data in the SetupFifo tab.
Now here is my problem: How should i change the SetupFifo tab?
I tried the command:
self.SetChannelRelation(channel_no, Ly.CR_1_2)
Unfotunately this didn't work, which doesn't supprise me, as I made this command up, based on the examples in the help file on the SetupFifo tab. Those are, however, for SetChannelFlags and SetChannelType, which I don't think I need yet...
Has anyone experienced a similar problem? I also installed a trial version on another computer to check if it works there (it doesn't).
Or does someone know a method to find out how to be able to change inputs and outputs the way i want?
Every help will be greatly appreciated.
Sincerely, Jarno

You do not need to set the channel relation for "simple" channel relation like 1:2, 2:1, etc.
Just set the relation you want in the configration dialog that open when you drop a script module into to worksheet.
The channel relation and their python constants have nothing to do with the amount of inputs and outputs of a script module.
The channel relation tells the "DASYLab core" how to guide meta data (channel names, units, etc) through a module.
In function "DlgInit" you have to tell DASYLab how many inputs and outputs your module should have.
Your module should have 2 outputs for each input: this combination of input and outputs is called a "channel".
Because one channel has 2 outputs, the module can have max. 8 channels only.
The dialog with the channelbar "thinks" in channels, but DASYLab "thinks" in connectors (connectors are inputs/outputs).
So, you are responsible to translate "channels" in "connectors" and vice versa
In DlgInit you can ask DASYLab about the amount of inputs and outputs.
self.NumInChannel <-- amout of connectors on modules left side
self.NumOutChannel <-- amount of connectors on the right side
self.DlgNumChannels <-- amount of activated channels in the dialog (something between 1 and DlgMaxChannels)
Your module's channels have 1 input, 2 outputs each, so you can write either
self.DlgNumChannels = self.NumOutChannel / 2
or
self.DlgNumChannels = self.NumInChannel
If the module has 3 input and 6 outputs, the dialog will get 3 channels.
In DlgOk you need to translate the amount of channels into the correct amount of connectors (inputs/outputs):
For "one channel = 1 input + 2 outputs" this is:
self.SetConnectors( self.DlgNumChannels, self.DlgNumChannels * 2 )
DlgInit
self.DlgNumChannels = self.NumInChannel
# or: self.DlgNumChannels = self.NumOutChannel / 2
self.DlgMaxChannels = 8 # or Ly.MAX_CHANNELS/2
DlgOk
self.SetConnectors( self.DlgNumChannels, self.DlgNumChannels * 2 )
M.Sc. Holger Wons | measX GmbH&Co. KG, Mönchengladbach, Germany | DASYLab, DIAdem, LabView --- Support, Projects, Training | Platinum National Instrument Alliance Partner | www.measx.com

DasyLab Timebases - Can anybody explain the various clocking methodologies ?

Hi All.
I,ve been using DasyLab for at least 10 years and as you'd expect become quite proficient.
Mostly I use Measurement Computing USB pods or DataShuttles.
But the exact homology of the Time Bases, their physical methods of generation, and particularly the optimum logical choices,
still remains mysterious and obscure. I can always get a program working you understand, but selecting DasyLab clocking feels like playing Tetris.
Any insight would be welcomed. Does anybody see the 'Highest Governing Concept ' here ?
Thanks and respect.
DaveTheRave

Generally speaking, you want to use the hardware based clocking, since the hardware usually has the highest resolution clock.
When we introduced the Time Base concept, it was to address the new feature that allowed more than one DAQ device to be connected to the PC. Each device may have its own clocking, and some allow you to connect and synchronize multiple devices (Master/Slave clocking).
One major driver, the IOtech driver, decided to stay within the original Driver API, which allows only one time base, but they made changes in the driver to handle master/slave and sample rate decisions.
Other drivers embraced the Time Base concept, and were developed using the "Extension DLL API", starting with the National Instruments driver, and picked up by most driver developers, including Measurement Computing, UEI, instruNet, and many others.
So, DASYLab now shows you timing sources from at least two devices --
Driver Timebase is associated with the installed driver - Sound Card, Demo, or IOtech, typically.
DASYLab Timebase is a software timed source, usually used for slower (less than 100 samples/sec) timing
As you add drivers, you will be exposed to that manufacturer's choice of timing:
National Instruments NI-DAQmx - timing is set in NI Measurement & Automation (MAX)
You have choices of 1 sample on demand, n samples, continuous
Each task has its own timing, so one board may have a timebase for Analog Input, Analog Output, Digital Input, Digital Output, etc.
Measurement Computing MCC-DRV
You have two timebases available for most devices, Hardware clocked or software clocked.
Some devices only allow hardware clocking for one subsystem - the other subsystems would then use the software clock
Some devices only allow a single sample rate (USB-TC, USB-TEMP are 2 s/sec)
Some devices use the settings in instaCal to determine allowed sample rates (USB-2416, USB-2408); individual channel choices may limit the overall (aggregate) sample rate.
Analog/Digital output timing can be configured "using the input timing" or with driver based timing - many devices only support software clocked ("slow") timing on outputs.
UEI - time bases are not created until you create modules that require them
InstruNet - time base is determined by a mix of the DASYLab time base and the individual channel settings
If you open a worksheet and you see a time base that is in (parentheses) - the driver or hardware was not found, but the worksheet remembers it.
Many modules are software data generators - the Generator, the Switch, the Slider, and they offer an option to select one of the available time bases. If you use a switch, for example, to control a relay, the switch timing should match the other inputs of the relay. The switch and the slider also offer a "with input" choice, which allows you to wire an input to them, to force the module timing to match the input timing.
Some Input/Output modules have to use software timing on the data - the RS232 Input, for example. It has to assume that the input samples are not equidistantly spaced, and tags the timing with "triggered". You can force it to use hardware timing in the Options, and fill the data block with old data until new data is received.
Confusing? Yep.
What's the right choice?
Hardware vs. software clocking - for sample rates above 100 samples/second, you will want hardware clocking. For slower rates, you may be forced to use software clocking.
DASYLab vs. Driver vs. Timebase A HW vs. Timebase B SW
I would use the device's clock whenever feasible. It's more reliable and accurate than the PC clock.
So, for Measurement Computing USB "pods" (I like that word!) - use the MCC-DRV timebases when ever possible.
Datashuttle... are you in the UK? The original Datashuttle is long gone, and only used the Driver timebase.
The UK sold (sells?) a version of the IOtech PersonalDAQ 54/55/56 products as a Datashuttle.
Funny that you should mention tetris... someone may have written a tetris module for DASYLab as a exercise.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

Y/t chart stops showing data depending on Maximum Display Range setting

The y/t graph will not display any data if I increase the Maximum Display Range setting to .8000s or higher. The data in the file is at 5000 Hz, is this part of the problem? I have played around with the Time Base and Measurement setting to no avail. The data is arbirary in length, but will not be longer than 3 seconds.
Solved!
Go to Solution.

Here's the scoop...
You have 145 blocks of data in the file. Fewer than that are sent through the Relay00.
When you configure the Y/t Chart for more blocks than you have, then it waits for the rest of the blocks to come in. And they are not going to come in.
One workaround is to use the "Fast Recorder" mode of the Y/t Chart, but your block size is too small (50 vs 128 minimum).
I'd suggest switching to the Chart Recorder module - configure it like this... and then, because you want the trigger to reset the time to 0, use an Action module.
Configure the Action like this... it will reset the Chart to start at 0 each time the trigger opens the Relay.
- cj
Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

DASYLab data output stopping after 10 points

Let me preface everything by saying I'm a novice at this. Now that that's out of the way...
I am having an issue getting more than 10 data points to record into an output file. I'm sure it's some setting conflict but I'm having no luck figuring it out.
I've got two tasks in Measurement & Automation Explorer: the first recording 4 strain gage signals, the second recording 2 temperature signals. The strain gage signals are coming into a NI 9237 and the thermocouples are coming into a NI 9211; both seated in a NI cDAQ-9188.
In DASYLab (v13) I have the setup shown in the attached image:
When I click Play everything seems to run fine (i.e., no error messages), but when I stop and open up the generated ASC file there are only 10 data points, one point every 0.1 second for 1 second.
Can anyone point me in the direction of the settings that control data collection, either in DASYLab or in M&AE? Thanks!
Solved!
Go to Solution.

Thanks for responding so quickly!
As I was typing up a response I noticed something in the Timing Settings in the M&AE tasks. The Acquistion Mode was set to 'N Samples'. I changed the mode to 'continuous samples' and it is now recording as I was expecting. I'm still not sure what was defining the "N" as 10, because the Samples to Read was set to 10k, but since it now seems to be working I'll leave that to another day. Thanks again

Agilent 34970 with Dasylab

Hi
Does anyone Know Is it possible for me to use the Agilent 34972A with Dasylab 12. I have connected the device to max and installed the IVI drivers and everything seems to be connected ok (VIA LAN CABLE) However when i try to use the IviDmm+ module in Dasylab 12 i get the error.
IVI API Function IviDmm_ConfigureMeasurement return with error -1074135023.
Iam new to MAX and was wondering do you need to set up a channel list in max and if so how do i do this?
Thanyou
Brian

Duplicate Post:
http://forums.ni.com/t5/DASYLab/could-you-tell-me-what-this-error-is-please-IVI-API-Function/m-p/175...
Nick C.
Cardiff University

Can Dasylab calculate mean and median power frequency of EMG? And how?

I got a set of consecutive EMG signals. Can I get the mean and median power frequency by just using Dasylab software?
If the answer is yes, how can I get them? Thank you in advance!

Dear Mr. Wei-Jie Fu,
I found a lot of special article for EMG, mean and median power frequency with Google search. So I think there are special algorithm necessary to figure out the correct informations. I think we don't have a useful result based on DASYLab standard modules for your application. If you have an algorithm in C/C++ so it's general possible to design an payed Extension Toolkit module for this job for you.
Best Regards,
MHa

DASYLab 13 // Set t to 0 at triggerevent

Similar Messages

Maybe you are looking for