Calculate Duty Cycle

Is there a function or add-on to Diadem to calculate duty cycle from a raw PWM voltage signal?

Hello RussellSenior,
Unfortunately, there is no such function in Diadem. However, you can develop a script which counts the up time and the down time. Base on those information, you can get the duty cycle of your signal.
Carmen C.

Similar Messages

Frequency and duty cycle measurement

Hi Friends,
Its been very helping from the day 1 i started psoting my questions to this forum...
Now again its time to seek ur help...
My req is something like i have a sound waveform (say a tone) saved as a .wav file.
Say suppose 1.wav.................
I need to evaluate this wave at a particular interval and should be able to calculate duty cycle, dB level, output frequency and peak to peak voltage similar to a CRO.
I already tried with the below VI but its showing for the entire .wav, so need to do some modifications which attains my req, but i am not sure where to kick off....
So anybody who have worked or developed similar VI in past ,please share your exp's
Thanking you in advance.
Cheers,
Suneel.V
Attachments:
Duty_Cycle.JPG ‏91 KB

Joe/Jeremey,
I am facing some new issue with the VI,
Frequency and Duty cycle are coming but the problem is something like the JPG attached.
Its not frequent and only coming for a particular part of the waveform
Is it waveform (.wav) dependent, if so let me know how to debug this.
Attached the VI (modified), snapshot of error and also wavefile (.wav)
P.S: error coming only when the yellow lines selected to the first quarter of the wave.
Cheers,
Suneel.V
Attachments:
delete_b.zip ‏12 KB
Waveform_Extractor_With_Duty-Cycle_July11.vi ‏151 KB
error_midlevel1.JPG ‏133 KB

NI 5105 - Measure PWM Waveform Duty Cycle

Will the Positive Duty Cycle scalar measurement in the NI-SCOPE software calculate duty cycle correctly on a PWM (pulse-width modulated) waveform? I have a 400Hz signal that is pulse-width modulated with a 40Hz signal that I need to measure the duty cycle for. Since this is not a normal, continuous waveform (like a sine wave or square wave) I don't know if the NI-SCOPE software will correctly calculate the Duty Cycle. Has anyone tried this with success? I am looking at using the NI-5105 because it has 8 channels, but am open to using other hardware and just multiplex my signals to the digitizer.

The positive duty cycle scalar measurement should correctly calculate duty cycle on your pulse. By default, the measurement finds the base and top of your waveform using a histogram of the Y values (there will be peaks in the histogram at the base and top values). Duty cycle is calculated from the 50% level crossings between these two values. You must have at least one complete cycle and only the first cycle is measured.
If that doesn't work for you, there are a plethora of parameters you can change (except for which pulse you measure - it is always the first). For example, you can set the upper, lower, and level crossing values to specific % or voltage levels. See the documentation and examples for details.
If you need to measure the duty cycle of multiple pulses in the same pulse train, there is a LabVIEW function (Pulse Measurements.vi) which allows you to do this. It uses the same algorithms as the internal NI-SCOPE routines.
In either case, the measurement is independent of the hardware. Any NI-SCOPE device will work. If you have any other questions, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Measuring PWM duty cycle with Analog Input

Hello folks,
I have a NI 9205 module and was wondering if there was a way to measure the duty cycle of a PWM signal that I am generating with a separate microcontroller? I have found a lot of examples with Digital inputs but not analog.. Is this possible?
Thank you,
Bob

Hi Robert,
I'm not sure what that error is, try searching for it.
If you want to measure a PWM signal you would usually use a counter input. A counter is a dedicated piece of hardware that is used to measure digital signals. Since the NI 9205 is an analogue device and it doesn't have any counters onboard, you will not be able to select counter input.
I would recommend you get the right tools for the job and buy a digital acquisition device with an onboard counter. It will make reading PWM much easier for you. The NI 6008 has a counter onboard and is only £99. It will also offload processing from software to hardware since you don't have to calculate duty cycle.
If you still want to use analogue post back and we can look into why its not working for you. Tips to start you off: Voltage is the correct setting and Look in the manual and make sure you have connected it like you have configured it (differential, RSE, NRSE page 14)
Lewis Gear CLD
Check out my LabVIEW UAV

Calculate Square wave Duty Cycle

Hello everyone,
I'm acquiring (with USB-6212) a square wave, "100Hz" with variable duty cycle - which can be 20%, 50% or 80% - for matters of decodification; the acquisition frequency is set to 4k. Actually, I said the frequency is 100Hz, because I get a rising edge every 10ms, but the length of the high level is defined by the communication protocol and that is what I called duty cycle (even though this does not match the exact definition of this property)
Since I need to decode the information contained by the wave, it's necessary for me to be able to tell what the duty cycle is. I've acomplished this so far by taking the derivative of the signal, then calculating peaks and valleys index in the waveform and finally subtracting them, as shown below.
It works ok almost the whole opeartion, however, the acquisition is not 100% exact. Sometimes I get the signal in the picture A, that is ideal for what I intended.
Other times, the signal is like B and the derivative amplitude does not cross my threshold, even though there is a rising edge there. I could lower my threshold to 2, for instance, but then I'd get vulnerable to the signal in picture C, which would accuse 2 peaks, instead of just one.
Anyone have an idea on how to work around this or any other method more reliable than taking the derivative of the signal?
Solved!
Go to Solution.

Well, we can only answer question based on the information supplied! The LabVIEW Mind Reading Toolkit is still in development.
Your application is one where parallel loops may be valuable. In the acquisition loop you read data from the data acquistion device at a rate which optimizes the DAQ perfomance (the >= 2k points you mentioned). The data is transferred to an analysis loop via a queue. In the anaylsis loop you can put the data into a shift register. When more data is available from the Acquisition loop, dequeue it and append it to the data in the shift register. The Duty Cycle section will find two consecutive rising edges and the falling edge between them ( the 10 ms segment). It calculates the duty cycle for that segment. Then it uses the second of the rising edges as the first rising edge for the next segment. Repeat until duty cycles have been determined for all segments.
There are a lot of details which can be imprortant in a process like this. Many of them are dependent on other things you have not specified. What will be done with the duty cycle values? Is the raw data to be displayed? Saved to file? Discarded after the duty cycle is measured? How long will the process continue? How much data can accumulate?
Lynn

How can I measure a 0% or 100% duty cycle signal ?

I want to measure the duty cycle of an input signal using a counter of a 6030-E board.
I work with a PXI Rack under Labwindows/CVI.
My program already works properly for duty cycle between 1% and 99%, but it is not able to detect 0% duty cycle (ie : signal to ground), nor 100% duty cycle (ie : signal to power supply).
The problem is I don't understand how the counter works in such a situation (it cannot detect any edge, as long as the signal is continuous 0V or continuous 12V).
Please have a look on the following code :
1- First, the counter is configured
// Reset Compteur
i_Status = GPCTR_Control(iDevice, iCptID, ND_RESET);
//Definition du type de mesure du compteur (mesure temps impulsion)
i_Status = GPCTR_Set_Application (iDevice, iCptID, ND_SIMPLE_PULSE_WIDTH_MSR);
//Definition de la vitesse d'echantillonage (20 Mhz)
i_Status = GPCTR_Change_Parameter(iDevice, iCptID, ND_SOURCE, ND_INTERNAL_20_MHZ);
//Definition du signal a mesurer (defaut)
i_Status = GPCTR_Change_Parameter (iDevice, iCptID, ND_GATE, ND_DEFAULT_PFI_LINE);
// initialisation du compteur
i_Status = GPCTR_Change_Parameter(iDevice, iCptID, ND_INITIAL_COUNT, 0);
// Preparation du compteur avant de l'armer
i_Status = GPCTR_Control (iDevice, iCptID, ND_PREPARE);
2- Then, every 10 ms, the value of the counter is read, so that I can calculate the duty cycle...
i_Status = GPCTR_Watch(iDevice, iCptID, ND_COUNT, ul_val_cpt);
3- ...and the counter is armed again for the next reading
i_Status = GPCTR_Control(iDevice, iCptID, ND_ARM);
When duty cycle changes from x% to 0% or 100%, the counter always keep the value corresponding to x%.
Even if I reset the counter between each measurement, it keeps this value ! I don't understand how it is possible.
How can I know that the counter didn't see any edge, and so that duty cycle is 0% or 100% ?
Thank you in advance for your help !
FraB

Hi,
Just have a look at this link, it can be interesting for you...
http://forums.ni.com/ni/board/message?board.id=40&message.id=2161&requireLogin=False
Regards
DD

Duty Cycle - Calculations

Hello,
I have spent the most of the day trying to figure out why my duty cycle calculations were not going any faster then .1 sec.
I am aquire data from 13 accelerometers at a frequency of 20000 Hz. When I put this through the Express VI to calculate the duty cycle, the time step always goes to .1 sec.
My question really is it possible to make this faster? The duty cycle of my accels are around 10ms.
I tried to dive into the express vi's front panels, but that didn't seem to have any good answer.
Thanks,
Royce

I think that you mis-understood what I was getting at. I get excellent readings in terms of the duty cycle output. The accels duty cycle ranges from around .25 -> .75 in my case. I even setup a nice little config block to get everything to around .5 to adujust easily to gravity readout for all 13. The problem that I am having is that the duty cycle conversion doesn't seem to read out all values of the input. The duty cycle will readout only 1 sample every .1 secs. That readout I believe should really be less then .01 secs depending on the resistor values that I have set up for my accels etc. What is even more interesting is that with the dynamic data readout, if I were to probe the data. Since I am reading at 20000 Hz, it is telling me that my dt should be .00005 secs. Which was fine for sampling of my input duty cycle wave, but afterwards that dt value should be scaled down to the actual frequncy. Now, if the program was written to take an average of duty cycles over .1 secs to fix the output period to a standard amount instead of having all sorts of strange step sizes since each reading (accel) generally has a different output frequncy the program forces that conversion to .1 sec period then fine or that is just takes a sample of 10, I guess I will have to deal. But, I did have the option to have a lot higher sampling rate for my accels, and if the .vi forces everything to .1 sec period for duty cycle output or if it takes an average of 10 readings and then rounds to the nearest sig digits this should be documented in the .vi for the duty cycle so that it is clear. If I am way off base and I shoudln't be getting a reading resulting from the duty cycle every .1 secs then I guess I am really lost. But, I do understand where the duty cycle readout comes from, that part is simple enough.
Thanks!
Royce

How to decode duty cycle using LabVIEW?

The duty cycles are output of an accelerometer, which are the input of the DAQcard-DIO-24, but how to decode the duty cycles after acquisition? I knew a timer would be useful, but have no idea about how to perform with labview.
Thanks a lot.
--yang
Message Edited by YangLi on 02-23-2006 05:43 AM
Message Edited by YangLi on 02-23-2006 05:48 AM

This will still be a very difficult task without dedicated hardware, and the 1ms resolution will still be relative to other things outside your control. Timed Loops give the tasks they execute a high priority in terms of processor time, but Windows will always be able to preempt LabVIEW in favor of anything it pleases (anti-virus software, automatic updates, screen redraws, etc.). The Timed Loop gives you the ability to dynamically handle what you do in such a situation (discard loop iterations, abort, etc.), but this is not ideal.
You would really be much better off, as Dennis said, with dedicated hardware. Most NI MIO or DIO boards come with a couple counters, which can measure high times and low times against a high-accuracy clock and calculate the duty cycle. The advantage here is that the hardware is doing all the work with real-time accuracy, so you don't have to worry about software-timing and Windows instability. In addition, the API for this in LabVIEW is much simpler.
If you choose to try using timed loops, then you will have pair each digital acquistion with a timestamp and for a sort of digital waveform.
Jarrod S.
National Instruments

Bad Duty Cycle readings

Hello!
I’m building an application in which I want to measure a duty cycle. I can control the “Duty Cycle In” and the FCM analyzes the info and sends a signal to the Motor. I want to measure the “Duty Cycle Out” of the motor. (I attached diagram) For this measurement I just connected a wire to the negative side of the motor. To calculate this Duty Cycle I am measuring the period and the pulse width. The program works very good when I have a “Duty Cycle Out” from 1% to 99%, but whenever is 0 or 100% it shows wrong info. I would expect that the pulse width at 0% or 100% is cero, but LabVIEW shows a value (1,1E-5 s) and calculates a Duty Cycle of about 23% which is totally wrong. Also, if I run the program for the first time and I measure this pulse width with a “Duty Cycle In” of 0%, pulse width is cero., but whenever I change the “Duty Cycle In” to 10% or higher, and then I go back to a “Duty Cycle In” of 0% it shows a value, and calculates a bad Duty Cycle. I don’t know why this only happens when I put higher “Duty Cycles In”, and then I go back to 0%. I measured the signal with an oscilloscope and there is nothing, not even noise! I don’t know how the card gets these lectures. Do you have any suggestions of what can be wrong?
Appreciated!
Solved!
Go to Solution.
Attachments:
Diagram.JPG ‏33 KB

Hi Elmar
Thanks for the reply. I attached my Code. I am measuring the period with ctr0 and pulse width with ctr1. I divide Pulse Width / Period to obtain the Duty Cycle. To detect 0% and 100% I compare the value of pulse width to zero. I created an additional Digital Input, with this channel I check if the signal is high or low. So if Pulse Width is zero, I read from the Digital Input the level of the signal, and then I know whether is 100% or 0%. My problem is when I have a Duty Cycle of 0 or 100%, the DAQ keeps sending a value for the pulse width, and I cannot apply the method explained before. I think this value should be zero, I don’t know if I am mistaken.
Attachments:
PWM_Measurement.vi ‏61 KB
PWM_Measurement.JPG ‏151 KB

How can I vary a PWM´s duty cycle inside a while loop?

Hi,
I'm using the "Generate Pulse Train.vi" to generate pwm signals in counters 0 and 1 in order to drive a DC motor both ways.
The problem is, I need to control the movement of the dc motor with my PI controller which is inside a while loop. I've tried letting the "generate pulse train.vi" outside the while loop, but the problem is, it only changes the value of the duty cycle when the loop is stopped. I also tried putting it inside the loop, but then it doesn't even work.
So, how can I vary a PWM´s duty cycle inside a while loop?
I'm attaching the VI with the PI controller.
Thanks for your help!
Guilherme
Attachments:
controleValvula.vi ‏332 KB

Here's some code I threw together a while back to change a duty cycle on the fly. It generates a fixed 5KHz or 25KHz frequency depending on laser selection, then allows duty cycle to be changed continously. Maybe you can use the premise of it for your application.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Attachments:
Pulse_Width_Modulator.llb ‏197 KB

How to generate a pwm whose duty cycle has to be varied depending on the frequency of the input trigger??

Sir/madam,
I am quite new to the Labview FPGA module.
I am currently working on an application where i have to generate a pwm to control the ON time duration . The pwm ON time depends on the frequency of an input signal.I want to retrieve the ON time value from a lookup table which contain the duty cycle values for the pwm at different frequencies of the input.This input also has to work as a trigger. The input is pulsed and the trigger has to generate the pwm at every rising edge. I am using a PCI 7831R- RIO series. I am urgently in need of some help and i have hardly a couple of weeks before i meet the deadline.
I am trying hard to learn the basics from the shipping examples but not able to quite make my vi work.
Kindly lend a helping hand and i would be very grateful to anybody who can help. Thanks a lot in advance.
Do ask in case of any clarifications required. I think i have explained my problem quite well.

Hello Manu,
You can refer
Developing a PWM Interface using LabVIEW FPGA or PWM Output with LabVIEW FPGA
How this helps.
Best Regards,
Hardik Asawa
AE
National Instruments
Message Edited by Hardik Asawa on 05-05-2010 12:46 AM

Kernel Panic - invalid backlight duty cycle - after upgrade from 10.5.2 on macbook air A1237

Here is the short version. I bought an older orignial Macbook Air Model A1237. The hinges had been damaged, and the screen would not display correctly - it had lines all across it and you could not see what you were doing. Anyway - I replaced the screen, hard drive, logic board, upper case, pretty much everything in sucession in an effort to get the MBA up and running again and get rid of the kernel panic I keep getting, all Apple replacement OEM parts. I bought a replacement screen - making sure I checked compatibility etc.. but when it started up I felt great perfect view - all was good - then it kernel paniced. I finally figured out that if I turned up the backlight manually all the way to max or if the ambient sensor made the backlight go to max - these were the only time I get a panic. Otherwise it runs perfeclty. The odd thing is I bought the original MBA disc that would have came with the MBA brand new - and if I wipe the hard drive and install leopard 10.5.2 from the dics and do not update anything - it works 100% perfectly no kernel panic at all. If I updgrade beyond the 10.5.2 I get the panic back. So that tells me its not the hardware, and I have confirmed the hardware and firmware are all up to date, as I was hoping it would be that easy a fix of updating the firmware. I have tried everything - googled everything - I am at the end of my rope on this one - please help.
In addition to all the repair work - i have tried test user, upgrading to snow leopard and lion, taking to the apple store, everything I can do , with no solid answer - the apple store told me it was hardware. But if it was then 10.5.2 should generate the panic as well. There are lots of articles and posts on other forums on this very issue - usually surrounding having the MBA display repaired and then they started getting the panics thereafter - but no one has ever recieved an answer either at all, or that works.
Here is the KP log below - please let me know your thoughts - id like to upgrade to lion to get the most out of the MBA - any help is appreciated - - - - - heres the log - - - - ( the reason the BSD states at loginwindow is the ambient sensor at that time kicks in and creates the panic ):
Interval Since Last Panic Report: 3873 sec
Panics Since Last Report:          1
Anonymous UUID:                    3A665154-0D6B-4EDF-8F76-80C322CF134A
Mon Aug 27 23:04:07 2012
panic(cpu 0 caller 0x2E42320C): "IG: Invalid backlight duty cycle value"@/SourceCache/GraphicsDrivers/GraphicsDrivers-5.48.6/Common/GLKernel/Inte l/IntelIntegratedFramebuffer/IntelGMAX3100FB.cpp:7065
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x2e3dbaa8 : 0x12b4c6 (0x45f91c 0x2e3dbadc 0x13355c 0x0)
0x2e3dbaf8 : 0x2e42320c (0x2e431258 0xa4aa 0x2e3dbb18 0x0)
0x2e3dbb18 : 0x2e425434 (0x3af6c00 0x5f40 0xe 0x0)
0x2e3dbb68 : 0x2e4d2283 (0x3e75000 0x0 0x626b6c74 0x5f40)
0x2e3dbbd8 : 0x2e3f9769 (0x4639e00 0x4107280 0x3a6ace0 0x80)
0x2e3dbc08 : 0x2e3f724c (0x48f2a00 0x4107280 0x3a6ace0 0x80)
0x2e3dbc38 : 0x2e3f785d (0x48f2a00 0x80 0x2e3dbc68 0x3f158d)
0x2e3dbc58 : 0x2e3f71db (0x48f2a00 0x80 0x2e3dbc88 0x3f0942)
0x2e3dbc78 : 0x2e3f9475 (0x48f2a00 0x430c640 0x3a6ace0 0x80)
0x2e3dbca8 : 0x2e3f92b9 (0x48f2a00 0x430c640 0x3a6ace0 0x80)
0x2e3dbd28 : 0x440edf (0x48f2a00 0x3feb880 0x44 0x11e7de)
0x2e3dbd78 : 0x18b71a (0x48f2a00 0x3fea900 0x44 0x407c7c0)
0x2e3dbdb8 : 0x12d4d6 (0x3b92090 0x407c79c 0x2e3dbdf8 0x11f1c6)
0x2e3dbdf8 : 0x1264fa (0x3b92000 0x392e984 0x408226c 0x0)
0x2e3dbf08 : 0x198fa3 (0x2e3dbf44 0x0 0x0 0x0)
0x2e3dbfc8 : 0x1a1cfa (0x398d120 0x0 0x1a40b5 0x3dc0c80)
          Backtrace continues...
      Kernel loadable modules in backtrace (with dependencies):
         com.apple.driver.AppleBacklight(1.6.0)@0x2e4d0000->0x2e4d3fff
            dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0x2e435000
            dependency: com.apple.iokit.IOPCIFamily(2.6)@0x2e2d5000
            dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x2e3f5000
         com.apple.driver.AppleIntelGMAX3100FB(5.4.8)@0x2e41c000->0x2e434fff
            dependency: com.apple.iokit.IOPCIFamily(2.6)@0x2e2d5000
            dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x2e3f5000
            dependency: com.apple.driver.AppleSMC(2.3.1d1)@0x2e412000
            dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x2e2ec000
         com.apple.iokit.IOGraphicsFamily(1.7.3)@0x2e3f5000->0x2e411fff
            dependency: com.apple.iokit.IOPCIFamily(2.6)@0x2e2d5000
BSD process name corresponding to current thread: loginwindow
Mac OS version:
9L31a
Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacBookAir1,1 (Mac-F42C8CC8)
System uptime in nanoseconds: 58935778708
unloaded kexts:
(none)
loaded kexts:
com.apple.driver.AppleHDAPlatformDriver          1.7.1a2 - last loaded 45739893296
com.apple.driver.InternalModemSupport          2.4.0
com.apple.iokit.IOBluetoothSerialManager          2.1.9f10
com.apple.filesystems.autofs          2.0.2
com.apple.driver.DiskImages          199
com.apple.driver.AppleHDAHardwareConfigDriver          1.7.1a2
com.apple.driver.AppleHWSensor          1.9d0
com.apple.driver.AppleUpstreamUserClient          2.7.5
com.apple.Dont_Steal_Mac_OS_X          6.0.3
com.apple.driver.AppleHDA          1.7.1a2
com.apple.driver.ApplePlatformEnabler          1.0.2d1
com.apple.driver.AppleGraphicsControl          2.8.15
com.apple.driver.AppleIntelGMAX3100          5.4.8
com.apple.iokit.IOSCSIArchitectureModelFamily          2.1.1
com.apple.driver.AppleIRController          113
com.apple.driver.AirPortBrcm43xx          367.91.22
com.apple.kext.AppleSMCLMU          1.4.5d1
com.apple.driver.AppleLPC          1.3.1
com.apple.driver.AppleTyMCEDriver          1.0.0d28
com.apple.driver.AppleHDAController          1.7.1a2
com.apple.driver.SMCMotionSensor          2.1.1d2
com.apple.driver.AudioIPCDriver          1.0.6
com.apple.driver.ACPI_SMC_PlatformPlugin          3.4.0a17
com.apple.driver.AppleBacklight          1.6.0
com.apple.driver.AppleIntelGMAX3100FB          5.4.8
com.apple.driver.AppleUSBTCButtons          1.7.4f1
com.apple.driver.AppleUSBMultitouch          189.35
com.apple.driver.AppleUSBTCKeyEventDriver          1.7.4f1
com.apple.driver.AppleUSBTCKeyboard          1.7.4f1
com.apple.driver.BroadcomUSBBluetoothHCIController          2.1.9f10
com.apple.driver.AppleUSBMergeNub          3.5.2
com.apple.driver.XsanFilter          2.7.91
com.apple.iokit.IOATABlockStorage          2.0.6
com.apple.driver.AppleUSBHub          3.4.9
com.apple.driver.AppleFileSystemDriver          1.1.0
com.apple.iokit.IOUSBUserClient          3.5.2
com.apple.driver.AppleAHCIPort          1.7.0
com.apple.driver.AppleIntelPIIXATA          2.0.1
com.apple.driver.AppleUSBEHCI          3.4.6
com.apple.driver.AppleUSBUHCI          3.5.2
com.apple.driver.AppleEFINVRAM          1.2.0
com.apple.driver.AppleRTC          1.2.3
com.apple.driver.AppleHPET          1.4
com.apple.driver.AppleSmartBatteryManager          158.10.5
com.apple.driver.AppleACPIPCI          1.2.5
com.apple.driver.AppleACPIButtons          1.2.5
com.apple.driver.AppleSMBIOS          1.4
com.apple.driver.AppleACPIEC          1.2.5
com.apple.driver.AppleAPIC          1.4
com.apple.security.seatbelt          107.12
com.apple.nke.applicationfirewall          1.8.77
com.apple.security.TMSafetyNet          3
com.apple.driver.AppleIntelCPUPowerManagement          76.2.0
com.apple.BootCache          30.4
com.apple.iokit.IOSerialFamily          9.4
com.apple.driver.DspFuncLib          1.7.1a2
com.apple.iokit.IO80211Family          216.1
com.apple.iokit.IONetworkingFamily          1.6.1
com.apple.iokit.IOHDAFamily          1.7.1a2
com.apple.iokit.IOAudioFamily          1.6.9fc5
com.apple.kext.OSvKernDSPLib          1.1
com.apple.driver.IOPlatformPluginFamily          3.4.0a17
com.apple.iokit.IONDRVSupport          1.7.3
com.apple.driver.AppleSMC          2.3.1d1
com.apple.iokit.IOGraphicsFamily          1.7.3
com.apple.iokit.IOUSBHIDDriver          3.4.6
com.apple.driver.AppleUSBBluetoothHCIController          2.1.9f10
com.apple.iokit.IOBluetoothFamily          2.1.9f10
com.apple.driver.AppleUSBComposite          3.2.0
com.apple.iokit.IOStorageFamily          1.5.6
com.apple.iokit.IOAHCIFamily          1.5.0
com.apple.iokit.IOATAFamily          2.0.1
com.apple.iokit.IOUSBFamily          3.5.2
com.apple.driver.AppleEFIRuntime          1.2.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.iokit.IOHIDFamily          1.5.5
com.apple.driver.AppleACPIPlatform          1.2.5
com.apple.iokit.IOACPIFamily          1.2.0
com.apple.iokit.IOPCIFamily          2.6

So I found a post on a random forum that offered a fix that I have tried and it worked. Background: I had a cracked LCD screen on a A1237, and I replaced a new screen and a battery. I started getting kernel panics when the brightness went to the highest level. Anyways, what you do is you need to get this file from a apple os x 10.5:
/System/Library/Extensions/AppleIntelGMAX3100FB.kext
then:
Install the .kext file you just grabbed by dragging it into Kext Utility (which can be downloaded here: http://cvad-mac.narod.ru/index/0-4)
then:
Shut down the machine. Reset SMC and PRAM (SMC: http://support.apple.com/kb/ht3964, PRAM:http://support.apple.com/kb/ht1379)
and the problem is fixed. If you google a bit, you can find an os x 10.5.2 AppleIntelGMAX3100FB.kext file at to use.
The original fix I found was posted here:
http://forums.macrumors.com/showthread.php?t=880800
Edit:
Just to clarify, my mac book air is running snow leopard 10.6.8, and I inserted the file from a 10.5.2. The fix completely eliminated the problem, now I can turn the brightness to max without the kernel panic.

Sine, Square & Sawtooth sweep generation with variable duty cycle/rise time & fall time

Dear All !
I request and need some candid advices on the subject issue keeping in view the following notes:
1) I am a novice in LabView.
2) I was an average Electronics Engineering graduate who graduated about 9 years ago and since then I have not been involved in Electronics Engineering.
I have undertaken a task or generation of Sine, Square and Saw Tooth wave forms. All these waveforms are to be frequency swept form 1 Hz to 100 kHz. The amplitude of all these waveforms should be able to be adjusted. The duty cycle of Square Wave should also be adjustable (or better be able to be swept). Likewise the rise time and fall time of sawtooth wave should also be adjustable (or better be able to be swept).
I am considering other options as well but wanna try it on LabView.
I wish to ask that is it possible to execute this task in Labview 7.0? If possible then considering the para 1 & 2 above, is it possible for me to finish this task in 15-20 days if I work on this for about 3 hours a day? If not then what can be reasonable estimate?
I will be extremely grateful if you people can offer advice on whole project or part(s) of it.
Thanking you in advance and requesting urgent response(s).
Solved!
Go to Solution.

Check this thread.
I did some similar coding, it might be usefull to you.
http://forums.ni.com/ni/board/message?board.id=170&thread.id=493477&view=by_date_ascending&page=1
I am using ver 9.0 though.
If you work 3hr /day for 2 weeks you might as well finish book basics 1& 2 and than can do whan you need in a breeze, couple of hours.
Good luck

Using labview cosimulation, how to control PWM duty cycle in multisim

I am new to using Multisim with LabVIEW using cosimulation. I want to ask if there is a PWM component in Multisim that can have its duty cycle be controlled using LabVIEW? I have an algorithm in LabVIEW that outputs duty cycle values from 0 to 1, representing duty cycle percentages.
How do I control the PWM duty cycle in Multisim using LabVIEW cosimulation?
Many thanks,
SPECTRE
Solved!
Go to Solution.

Hi Spectre,
In Multisim, search for the parts base on functionality, there are some PWM models in the database. Have a look at this knowledge base if you don't know how to search for parts:
http://digital.ni.com/public.nsf/allkb/7309A5CABC677296862577ED006EC99E
Aslo, have a look at this knowledgebase:
http://digital.ni.com/public.nsf/allkb/EF391C48CF71AE4F862571B900644F84
This article shows how you can get Mutlisim and LabVIEW to co-simiualte:
http://www.ni.com/white-paper/13663/en
I hope this helps
Tien P.
National Instruments

Problem to measure 0% and 100% duty cycle of a PWM.

Hi,
I am using counters of USB-6341 to measure duty cycle of PWM just by following the example 'Meas Duty Cycle-Buffered-Finite.vi'. It works almost all the time. However, when the duty cycle of a input pwm is 0 or 100%, the DAQ can't read anything, in another word, it can't measure 0 or 100% duty cycle.
How to modify that?
Thank you very much :-)
Nan

That's the thing about PWMs, you never really know if the PWM is 0% or 100%.
Let's say we have a 50% duty cycle, at 1/2Hz. So low for 1 second, high for one second right? What if we run at 1/20Hz, so low for 10 seconds high for 10 seconds. Or is this a 0% duty cycle for 10 seconds, and a 100% for 10 seconds?
A true PWM read will never be 0% or 100% it will just keep waiting until the trigger is seen, and recalculate the frequency and duty cycle of it. The solution to your problem is for you to define a duration to watch for a change, and if one isn't seen, then you can define 0% or 100% appropriatly.
So I would recommend taking your duty cycle like you normally are, and then at the same time watch the digital signal for however long you want, if the digital line does not change state, then output 0% if it is low and 100% if it is high and ignore what ever duty cycle you read. But if the digital line does change state, then use the read duty cycle as the actual value.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Calculate Duty Cycle

Similar Messages

Maybe you are looking for