Driver interval timing

I posted this in the Solaris 10 forum in error yesterday. No joy there, but you guys MUST know the answer.
Simple question really. Lots of tools (like iostat) report device service times (or response times) in milliseconds even when the clock interrupts are in 10 millisecond intervals. I gather that device drivers are supposed to record timestamps at various points, and I have even gone as far as determining that they do so in a structure known as a kstat (I think).
But how does a disk driver which services an interrupt on a different CPU to the one on which the I/O was initiated measure intervals? Isn't "gethrestime" based on the caller's CPU registers?
Google has utterly failed me, as has every Solaris internals reference that I can find. I am getting frustrated. Can anybody put me out of my misery?

I'd think you should be posting in the forum for the Solaris 10 os, not a Java forum. Maybe someone in the Java Native Methods forum would have the necessary Solaris 10 expertise, also.
If you do post elsewhere, either close this out with a final post or put a reference(s) to any other posts and say where you want replies posted, so replies aren't needlessly duplicated.

Similar Messages

Interval Timing Issue On Solaris 10/Intel

Not sure this is the right forum for this, but I'll give it a shot. Please redirect me if you think there's a better forum. This is going to look like a "C" problem, but this really is a question about something going on in the interactions between the operating system, the JVM, and a piece of native code we have.
We have an interval timing facility that's implemented over a small set of platform-dependent native timing facilities. The *NIX "itimer" facility is used wherever it exists. On RedHat/Fedora we also implement a timer over the RTC device. On Windows we use a WaitableTimer.
On all platforms there's a Java class that bridges to an appropriate timing facility via the JNI, and to date this has worked great on all platforms except for Solaris 10 on Intel. By "worked great" I mean that the clock tics end up being almost exactly what we expect for a given configured Hz update rate. So... e.g. if we set up a timer for 50 Hz, then we actually get 50 Hz +/- some minor variation much less than 1 second.
On Solaris 10/Intel we set up a 50 Hz itimer in a plain-vanilla C app and we get ~50 Hz, but if we call the same C code from Java via the JNI we almost always end up with ~38Hz.
The amount of Java and native code involved is almost trivial, and the hardware is a smoking fast contemporary PC. We ran over the itimer facility on an old Sparc 5 box and it worked fine.
I've tried tweeking sundry esoteric -X and -XX JVM invocation options with no effect.
J2SDK 1.4.2-07 in all cases.
Thoughts?

I'd think you should be posting in the forum for the Solaris 10 os, not a Java forum. Maybe someone in the Java Native Methods forum would have the necessary Solaris 10 expertise, also.
If you do post elsewhere, either close this out with a final post or put a reference(s) to any other posts and say where you want replies posted, so replies aren't needlessly duplicated.

Interval Timing Issue On Solaris 10/Intel When The JNI Is Involved

We've observed an odd behavior bridging to interval timers over the JNI on Solaris 10/Intel, and I was wondering if anybody here has ever seen anything like this.
We have an interval timing facility that's implemented over a small set of platform-dependent native timing facilities. The *NIX "itimer" facility is used wherever it exists. On RedHat/Fedora we also implement a timer over the RTC device. On Windows we use a WaitableTimer.
On all platforms there's a Java class that bridges to an appropriate timing facility via the JNI, and to date this has worked great on all platforms except for Solaris 10 on Intel. By "worked great" I mean that the clock tics end up being almost exactly what we expect for a given configured Hz update rate. So... e.g. if we set up a timer for 50 Hz, then we actually get 50 Hz +/- some minor variation much less than 1 second.
On Solaris 10/Intel we set up a 50 Hz itimer in a plain-vanilla C app and we get ~50 Hz, but if we call the same C code from Java via the JNI we almost always end up with ~38Hz.
The amount of Java and native code involved is almost trivial, and the hardware is a smoking fast contemporary PC. We ran over the itimer facility on an old Sparc 5 box and it worked fine.
I've tried tweeking sundry esoteric -X and -XX JVM invocation options with no effect.
J2SDK 1.4.2-07 in all cases.
Thoughts?

I'd think you should be posting in the forum for the Solaris 10 os, not a Java forum. Maybe someone in the Java Native Methods forum would have the necessary Solaris 10 expertise, also.
If you do post elsewhere, either close this out with a final post or put a reference(s) to any other posts and say where you want replies posted, so replies aren't needlessly duplicated.

My hard drive is timing out with my airport extreme

I have an Airport Extreme Model A1345. Trying to connect my LaCie Rugged 500 GB HD and use it as a networked HD. But it keeps timing out. Are there only certain drives compatible with the Airport Extreme? Or do I need change a file share setting?

What firmware are you running?
All drives these days are designed to spin down.. not all setups are that smart spinning the drive up again.
And yes, there can be issues.. even though the LaCie is powered (i hope) you might still need a powered hub to overcome the very poor ability of the USB in the AE.
I would also tend to think running it on 7.5.2 firmware or 7.6.1 at the latest is prreferable to 7.6.4 but the only way to tell is try it.

Sample interval variability

The attached vi is used to sample eight analogue channels at an interval of 31,250microseconds or 32Hz with a cRIO-9074. When I look at the data file there is a sampling interval variation of up to plus or minus ~150microseconds but when I monitor the output from DIO7, which gives a 12msec pulse for every acquisition, with a counter/timer, the variation is ~1microsecond.
Could somebody suggest why there is such a difference and what measures could be taken to reduce the sampling rate variation.
Best regards,
nos
Attachments:
sample data 13 [marina].vi ‏71 KB

Thank you for your response. With regard to your questions see below.
I assume that when looking at the data file, you're using the timestamp to work out the interval?
That is correct, see attached Excel file; the included plot works out the variability by subtracting the actual sampling interval from the desired interval and plotting the results against sample number.
I would therefore expect a relatively large variation, especially if you are looking at the microsecond scale (and I also assume you are running the code in Windows, not RTOS).
The code is running on the cRIO-9074 and uses a timed loop that is synchronised with the Scan Engine.
Do you need an absolute time? If you are only after interval timing, use the Tick Count (ms), this will give you a more accurate reading.
Absolute time is not required; as shown in the attached file the first data sample should have a time stamp of zero, with each successive sample incrementing by the sampling interval.
Best regards,
nos
Attachments:
data file 1.xlsx ‏259 KB

Is USB 2 fast enough to record to hard drive over?

Hi folks. Atthe moment I'm recording to ext HD via FireWire 800, but down the line I may well want to get a FireWire audio interface, would recording to the drive work ok over USB? Or has anyone got experience of using FireWire busses? Advice/recommended options appreciated :) ta!

While the USB 2 transfer rate may seem faster than Firewire 400, it is a "BURST RATE" meaning after a few seconds it drops substantially while Firewire starts high and stays high meaning that Firewire is faster at "SUSTAINED RATES" such as streaming audio to drives. Test it your self by copying a 1 GB file to a USB 2 drive and then to a Firewire Drive while timing the transfer... Firewire will smoke it everytime
http://www.mac-forums.com/forums/schwebs-lounge/54422-usb-2-vs-firewire-400-agai n.html
http://www.barefeats.com/usb2.html
From GlyphTech:
"Even though USB 2.0 Hi-Speed has a theoretical max raw data rate slightly higher than FireWire (480 mbps vs. 400 mbps), the typical sustained transfer rates are about the same, because FireWire is a more efficient protocol to use in audio and video environments. In fact, in most cases, FireWire beats USB 2.0 Hi-Speed, albeit by a small margin. Very often it will be the computer or hard drive mechanism which limits the system performance more than the interface, so you might see about the same performance using FireWire-A or USB 2.0. "
According to NEC (Dec 2004):
"Specified speed of USB 2.0 is 480 mbps (in other words, around 60 Million Bytes per second, or 57.2 MB/s), but 57.2 MB/s is NOT the actual data rate.
This is because USB 2.0 packet is inclusive of overhead data.
[Note that conversion from megabits to MegaBytes requires (x*1,000,000/8)/1,048,576.]
Moreover, idle time are added between packets.
Besides, data rate is also dependent on the system architecture, the PCI bus and the attached USB devices.
Therefore, actual data transfer rate [of USB 2.0 High-speed] will be lower than 480 mbps (57.2 MB/s).
Our measurement result of data transfer rate with USB 2.0 storage device (HDD) is about 20 - 25 MB/s on average."

Error when connect to sqlserver

I encounter the following error,any 1 can tell me reason?
com.solarmetric.kodo.runtime.FatalDataStoreException: java.sql.SQLException:
[Microsoft][SQLServer JDBC Driver]Error establishing socket.
[code=0;state=08001]
NestedThrowables:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing
socket.
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Connection timed
out: connect
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLException
s.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
..java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
NestedThrowablesStackTrace:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing
socket.
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.createConnection(Data
SourceImpl.java:932)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.findConnection(DataSo
urceImpl.java:844)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.getConnection(DataSou
rceImpl.java:563)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
321)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
314)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(Dat
aSourceConnector.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
..java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Connection timed
out: connect
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.createConnection(Data
SourceImpl.java:932)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.findConnection(DataSo
urceImpl.java:844)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.getConnection(DataSou
rceImpl.java:563)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
321)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
314)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(Dat
aSourceConnector.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
..java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
com.solarmetric.kodo.runtime.UserException: This operation cannot be
performed while a Transaction is active.
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.close(PersistenceManager
Impl.java:1058)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.close(PersistenceManager
Impl.java:1042)
at com.ipacs.als.test.Test.main(Test.java:183)
Exception in thread "main" Process terminated with exit code 1
Regards,
geduo

Geduo-
It sounds like your ConnectionURL is not correct. Can you post the
properties you are trying to use?
In article <[email protected]>, geduo wrote:
I encounter the following error,any 1 can tell me reason?
com.solarmetric.kodo.runtime.FatalDataStoreException: java.sql.SQLException:
[Microsoft][SQLServer JDBC Driver]Error establishing socket.
[code=0;state=08001]
NestedThrowables:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing
socket.
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Connection timed
out: connect
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLException
s.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
.java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
NestedThrowablesStackTrace:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing
socket.
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.createConnection(Data
SourceImpl.java:932)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.findConnection(DataSo
urceImpl.java:844)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.getConnection(DataSou
rceImpl.java:563)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
321)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
314)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(Dat
aSourceConnector.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
.java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Connection timed
out: connect
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.createConnection(Data
SourceImpl.java:932)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.findConnection(DataSo
urceImpl.java:844)
at
com.solarmetric.datasource.DataSourceImpl$AbstractPool.getConnection(DataSou
rceImpl.java:563)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
321)
at
com.solarmetric.datasource.DataSourceImpl.getConnection(DataSourceImpl.java:
314)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(Dat
aSourceConnector.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDi
ctionaryFactory.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSim
pleConfiguration.java:377)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCSt
oreManager.java:710)
at
com.solarmetric.kodo.impl.jdbc.query.JDBCQuery.getExpressionFactory(JDBCQuer
y.java:112)
at
com.solarmetric.kodo.query.QueryImpl$DatastoreQueryExecutor.<init>(QueryImpl
.java:1516)
at
com.solarmetric.kodo.query.QueryImpl$QueryExecutionManager.getQueryExecutor(
QueryImpl.java:1351)
at com.solarmetric.kodo.query.QueryImpl.internalCompile(QueryImpl.java:462)
at
com.solarmetric.kodo.query.QueryImpl.getAccessPathClasses(QueryImpl.java:116
1)
at
com.solarmetric.kodo.query.QueryImpl.executeQueryWithMap(QueryImpl.java:574)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:533)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:483)
at com.ipacs.als.test.Test.main(Test.java:125)
com.solarmetric.kodo.runtime.UserException: This operation cannot be
performed while a Transaction is active.
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.close(PersistenceManager
Impl.java:1058)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.close(PersistenceManager
Impl.java:1042)
at com.ipacs.als.test.Test.main(Test.java:183)
Exception in thread "main" Process terminated with exit code 1
Regards,
geduo
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Kernal Panic - Video related?

Hey everybody, I am running OSX 10.7.5 on my MB404LL Macbook. I've only owned the machine for a few weeks but I am getting a kernal panic once or twice a week when I open the computer from sleep. I ran the thorough Apple hardware test (took about an hour) which returned no errors. I have even ran a fresh install of Lion last week to see if the issue was from a previous time machine restore. Here's the crash log which mentions the graphics card driver:
Interval Since Last Panic Report: 66548 sec
Panics Since Last Report:          1
Anonymous UUID:                    65DF09F9-E322-4B77-B850-98FB22AD08F8
Sun Sep 15 10:43:36 2013
panic(cpu 0 caller 0x18db9f8): AppleIntelGMAX3100FB GPU parser error. EIR 0x1 ESR 0x1 ISR 0x8000 - unknown type
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0xadbea8 : 0x2203de (0x6b08cc 0xadbec8 0x229fb0 0x0)
0xadbed8 : 0x18db9f8 (0x18eba26 0x6b21c80 0x18eb941 0x1)
0xadbf28 : 0x66434a (0x6beb400 0x6bba280 0x1 0x2c557d)
0xadbf68 : 0x663198 (0x6bba280 0x6d42be8 0xadbfa8 0x22ee1a)
0xadbfa8 : 0x663014 (0x6c32c40 0x5c15d00 0x6c32c5c 0x6d42be8)
0xadbfc8 : 0x2c7d0c (0x6c32c40 0x0 0x10 0x794c4d0)
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelGMAX3100FB(7.0.4)[5066EB85-013A-4A3C-B786-20A637B5B9 1E]@0x18d8000->0x18f2fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[5EC48FA0-6225-414F-ABAB-A898F91B7E15]@0xa8700 0
            dependency: com.apple.iokit.IOPCIFamily(2.7)[8087C029-833E-4B62-A8C3-2B074B4C55F7]@0xb3c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[EE3F8FBE-3457-4F0E-A3A3-B9B1A44DCF6B]@0 x1008000
            dependency: com.apple.driver.AppleSMC(3.1.3d10)[B27E4CCE-EE2E-41F5-ABA7-D9B109283D27]@0xa8e 000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
11G63
Kernel version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT 2012; root:xnu-1699.32.7~1/RELEASE_I386
Kernel UUID: 859B45FB-14BB-35ED-B823-08393C63E13B
System model name: MacBook4,1 (Mac-F22788A9)
System uptime in nanoseconds: 200241646178
last loaded kext at 25476624299: com.apple.driver.AppleTyMCEDriver    1.0.2d2 (addr 0x175c000, size 45056)
last unloaded kext at 109103421786: com.apple.driver.USBCameraFirmwareLoader    1.1.0 (addr 0xe28000, size 24576)
loaded kexts:
com.apple.driver.AudioAUUC    1.59
com.apple.driver.AppleHDA    2.2.5a5
com.apple.driver.AppleHWSensor    1.9.5d0
com.apple.driver.AppleUpstreamUserClient    3.5.9
com.apple.driver.SMCMotionSensor    3.0.2d6
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleSMCPDRC    5.0.0d8
com.apple.driver.AppleLPC    1.6.0
com.apple.driver.ACPI_SMC_PlatformPlugin    5.0.0d8
com.apple.iokit.IOUserEthernet    1.0.0d1
com.apple.iokit.IOBluetoothSerialManager    4.0.8f17
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AudioIPCDriver    1.2.3
com.apple.driver.ApplePolicyControl    3.1.33
com.apple.driver.AppleBacklight    170.2.2
com.apple.driver.AppleMCCSControl    1.0.33
com.apple.driver.AppleIntelGMAX3100    7.0.4
com.apple.driver.AppleIntelGMAX3100FB    7.0.4
com.apple.driver.CSRUSBBluetoothHCIController    4.0.8f17
com.apple.driver.AppleUSBTrackpad    227.6
com.apple.driver.AppleUSBTCKeyEventDriver    227.6
com.apple.driver.AppleUSBTCKeyboard    227.6
com.apple.driver.AppleIRController    312
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.BootCache    33
com.apple.iokit.SCSITaskUserClient    3.2.1
com.apple.driver.XsanFilter    404
com.apple.iokit.IOAHCIBlockStorage    2.1.0
com.apple.iokit.AppleYukon2    3.2.2b1
com.apple.driver.AirPortBrcm43224    501.36.15
com.apple.driver.AppleEFINVRAM    1.6.1
com.apple.driver.AppleRTC    1.5
com.apple.driver.AppleFWOHCI    4.9.0
com.apple.driver.AppleUSBHub    5.1.0
com.apple.driver.AppleAHCIPort    2.3.1
com.apple.driver.AppleUSBEHCI    5.1.0
com.apple.driver.AppleUSBUHCI    5.1.0
com.apple.driver.AppleIntelPIIXATA    2.5.1
com.apple.driver.AppleHPET    1.7
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleACPIButtons    1.5
com.apple.driver.AppleSMBIOS    1.9
com.apple.driver.AppleACPIEC    1.5
com.apple.driver.AppleAPIC    1.6
com.apple.driver.AppleIntelCPUPowerManagementClient    195.0.0
com.apple.nke.applicationfirewall    3.2.30
com.apple.security.quarantine    1.4
com.apple.security.TMSafetyNet    8
com.apple.driver.AppleIntelCPUPowerManagement    195.0.0
com.apple.driver.DspFuncLib    2.2.5a5
com.apple.kext.triggers    1.0
com.apple.iokit.IOFireWireIP    2.2.5
com.apple.driver.IOPlatformPluginLegacy    5.0.0d8
com.apple.driver.IOPlatformPluginFamily    5.1.1d6
com.apple.iokit.IOSurface    80.0.2
com.apple.iokit.IOSerialFamily    10.0.5
com.apple.driver.AppleHDAController    2.2.5a5
com.apple.iokit.IOHDAFamily    2.2.5a5
com.apple.iokit.IOAudioFamily    1.8.6fc18
com.apple.kext.OSvKernDSPLib    1.3
com.apple.driver.AppleGraphicsControl    3.1.33
com.apple.driver.AppleBacklightExpert    1.0.4
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.iokit.IONDRVSupport    2.3.4
com.apple.driver.AppleSMC    3.1.3d10
com.apple.iokit.IOGraphicsFamily    2.3.4
com.apple.driver.AppleUSBBluetoothHCIController    4.0.8f17
com.apple.iokit.IOBluetoothFamily    4.0.8f17
com.apple.driver.AppleUSBMergeNub    5.1.0
com.apple.iokit.IOUSBHIDDriver    5.0.0
com.apple.driver.AppleUSBComposite    5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.2.1
com.apple.iokit.IOBDStorageFamily    1.7
com.apple.iokit.IODVDStorageFamily    1.7.1
com.apple.iokit.IOCDStorageFamily    1.7.1
com.apple.iokit.IOATAPIProtocolTransport    3.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily    3.2.1
com.apple.iokit.IO80211Family    420.3
com.apple.iokit.IONetworkingFamily    2.1
com.apple.iokit.IOFireWireFamily    4.4.8
com.apple.iokit.IOUSBUserClient    5.0.0
com.apple.iokit.IOAHCIFamily    2.0.8
com.apple.iokit.IOUSBFamily    5.1.0
com.apple.driver.AppleEFIRuntime    1.6.1
com.apple.iokit.IOATAFamily    2.5.1
com.apple.iokit.IOHIDFamily    1.7.1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.security.sandbox    177.11
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.DiskImages    331.7
com.apple.iokit.IOStorageFamily    1.7.2
com.apple.driver.AppleKeyStore    28.18
com.apple.driver.AppleACPIPlatform    1.5
com.apple.iokit.IOPCIFamily    2.7
com.apple.iokit.IOACPIFamily    1.4
Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 3 GB, SMC 1.31f1
Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz, 0x2C00000000000000, 0x3136485446313238363448592D3636374631
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0xAD00000000000000, 0x48594D503132355336344350382D59352020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: WDC WD3200BEKT-00F3T0, 320.07 GB
Parallel ATA Device: MATSHITADVD-R   UJ-867
USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0229, 0x5d200000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2

Hi jdcountryboy,
If you are having issues troubleshooting a reoccuring kernel panic, you may find the following article helpful:
OS X: About kernel panics
http://support.apple.com/kb/ts3742
Regards,
- Brenden

Unexpected ECIC Error

We recently upgraded our PCs from Lenovo C20 to C30. Both are running Win7 64-bit, in combination with a NI GPIB card. We are currently using version 2.8 of the NI-488.2 library. All these PC's are used to communicate with different GPIB devices. C30 PC's is however raising unexpected GPIB CIC errors (Controller In Charge), during the communication with the devices. The same program has been running fine over many years on the C20 PC's without the CIC errors.
Here are some of my observations:
1. When the NI-SPY program is running the CIC error did not occur ever after 2 days. When the NI-Spy program was closed, the CIC error occured within a day.
2. I tried changing the IbaTiming config parameter from 350 ns to 2 us as suggested by one of the threads here. That didnt help.
3. I also the added the condition where If the CIC bit was not set, wait until the CIC was set or until it timeouts before calling the Send() and ReadByte() commands. See below code:
if ((Ibsta & CIC) == 0)
  OutputDebugString("Waiting for CIC or TIMO to be set");
  ibwait(nBoardID, (CIC | TIMO));
  if(Ibsta & TIMO)
   OutputDebugString("Timeout Error Waiting for CIC");
Sleep( 10 );
Send( nBoardID, nDeviceAddress, ptrBuffer, lLength, nEOT );
I never saw the "Timeout Error Waiting for CIC" indicating that the CIC was surely set before calling the Send() or ReadByte() commands, neverthless I see the CIC error.
4. I also tried using ThreadIbsta() instead if Ibsta variable. But that didn't make any difference.
Does anyone have a suggestion or solution for this problem?
Thanks in advance,
SK

With the latest driver upgraded, I changed the bus timing from 500 ns to 2 us. However, this time the CIC error appeared much later than it appeared with old version of the driver & bus timing 500 ns. Any suggestions please? I've completely run out of ideas.

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.

Turquoise Screen over imported media

Hello Everyone!
I am trying to decide whether to get adobe Premiere pro CS4. Right now I have the trial version. But here's the problem:
Everytime I import something into the project (I've used AVI, MPG, JPEG, etc) into the project bin, and play it on the little preview screen, it works perfectly fine, and it looks great. However, everytime I drag it into the timeline, it is overlayed with this Turquoise texture, and you can see very little to no video at all. It looks horrible. Has anyone come across the problem, and if so how did you fix this? Anyone know how to fix this? Is this something to do with the settings? Like I said, i've tried multiple formats. Support said it had nothing to do with the fact that this is a trial version.
Here are my computer specs:
Toshiba Satellite A215-S4767
2.2 GHz, Core 2 duo processor
2 GB of Ram
250 GB Hard Drive
A timely responce would be most appreciated. Thank you in advance!

There seems to be a recurring issue with the Program Monitor in Premiere and embedded graphics cards in laptops, particularly in later OS's. I've witnessed this 3 times and heard about it second hand a number of times on this forum.
In my experience, it is often linked with a video driver issue on the machine. On one occasion, the latest driver from the machine vendor fixed the issue, on another occasion the latest driver from the Graphics card vendor (Intel) fixed the issue, on the third occasion (a 12" Dell), there simply was no solution.
May I ask, is the Graphics Card Memory shared with the machine memory? You can have a look in the BIOS. You may be able to increase the amount of RAM set aside by the BIOS for the graphics card. This might be clutching at straws but it may be worth a try.
There may be some settings in your graphics card you can tweak/play with. The section you're particularly interested in will be called "Video Overlay" or just "Overlay".
best of luck.
MP

G505s keeps restarting randomly

Before it does it again.... I've updated BIOS, bought an under-cooling fan platform, checked the cpu apu temps, uninstalled unused software, run ESET NOD 32 and found no viruses, raised the back for better ventilation, and IT STILL KEEPS RESTARTING RANDOMLY no matter what I'm trying to run. I'm running Windows 8.1 and every driver is up to date. Nothing exotic is plugged in. I've tried rebooting without anything plugged in. I've run all of the lenovo diagnostic software -- they all report everything is fine. I uninstalled any software I recently installed in the last month to see if it would stop the problem -- no luck. I have to end this quick before it restarts again. PLEASE HELP! --mikkimbru

Ok... Down to some basic troubleshsooting questions - bear with me on this...
1. Did you attempt to reset the notebook BIOS by removing the battery and AC power then pressing the power button for thirty seconds?
2. Did you try removing memory modules one at a time to see if one is going bad?
3. Did you attempt to remove the hard drive, boot from Linux Live CD or USB?
4. Have you been running on AC power without battery installed - suffered same failure?
I have seen this type of behavior with bad memory sticks, or a hard disk that is failing (drive circutry vs. HDD secotors). lastly - if the BIOS was corrupted would also be an issue requireing attention.
What I would do - remove battery and AC adapter, press and hold power button for 30 seconds. Insert battery, attach AC power and boot. If this regains working sytem, download and run Process Explorer to figure out what the running SVCHOST instances are connected to.
If BIOS reset fails to work, turn off computer remove battery and AC power. Access memory location (bottom access plate) and remove all memory sticks. If you have two installed this is a good way to test for issues. Boot computer without memory - if it beeps, or shows error message stating no memory installed we are in good shape. Insert one stick of memory into the first available slot and see if it is stable. If you have two memory sticks repeat this process with stick two - replacing stick one. If computer boots and is stable with both sticks in slot one, repeat using slot two. If one or more sticks does not work in slot two - then is an issue with the system board, and if under warranty have service center replace system board.
Once memory has been excluded from situation, try removing the hard drive and using a USB dock or adapter to test it on another computer. If it reads without errors, passes all tests (from manufacture) then try booting your notebook from CD/DVD using Linux "live" distro disk. If works, then may be issue with hard drive controller timing out or HDD integrated electronics failing with overheat condition or "soft solder" that expands when warm.
If all these steps fail to produce a stable system - there maybe issues with the sytem board that fail under heat stress. This might be from "silver threading" or a small crack in the board or in the system attached boards.
Either way - I hope that I have given you some things to look for.
Good luck.

How do I collect Analogue and Digital Data

Newbie to DAQmx - I need to acquire analogue and digital channels synchronously at, say, 1000Hz. But .NET Tasks appear to only copy with one type of channel...?
Any clarification or ideas welcome.

If you need to acquire data from two different operations synchronously, one way to handle that would be to set up on task to drive the timing, and have the second task use external timing.
If we assume that the second task is digital, then the second task would need to use something like "Dev1/ai/SampleClock" as the external timebase. There is no way to start both tasks at the exact same time, so it would also be helpful to use the same terminal as the start trigger for the second task.

Timed Interval D1-IMD batch is not working in MDM

Hi,
This issue is regarding CM-IMDD(Duplicate of D1-IMD) Timed Interval batch in MDM for converting PENDING imd's to EXCEPTION or FINALIZED.
When i run this batch for 90 sec as Timed interval. it is creating Next Batch Number and status is going to complete but none of the records got processed. In log threadId is getting null. But when i run the same batch for non-Timed Interval records are getting processed and in log also threadId is not null.
In threadpoolworker.log see below:
- 2011-12-06 13:54:24,340 [DistributedCache:EventDispatcher] INFO (support.batch.DistributedJobExecuter) Creating initial run for batch control CM-IMDD
- 2011-12-06 13:54:24,356 [DistributedCache:EventDispatcher] INFO (support.cluster.BatchClusterCache) updateEntryWithRunInfo key: 773891993 runId: BatchRun_Id(batchControlId: [CM-IMDD], batchNumber: 99, batchRerunNumber: 0) threadId: null
- 2011-12-06 13:54:24,418 [DEFAULTWorker:3] INFO (batch.logging.BatchLogWriter) Sending standard output to E:\MDM\ouaf\sploutput\DEV9\CM-IMDD.20111206135655.5.THD1.stdout
- 2011-12-06 13:54:24,418 [DEFAULTWorker:3] INFO (batch.logging.BatchLogWriter) Sending error output to E:\MDM\ouaf\sploutput\DEV9\CM-IMDD.20111206135655.5.THD1.stderr
- 2011-12-06 13:54:24,497 [DEFAULTWorker:3] INFO (api.batch.AbstractThreadWorker) Batch thread started with holdable session for primary QueryIterator. Cursor will be refreshed every 15 minute(s).
- 2011-12-06 13:54:24,747 [DEFAULTWorker:3] INFO (support.batch.BatchWorkInSessionExecutable) Preparing to remove work.
- 2011-12-06 13:54:24,747 [DEFAULTWorker:3] INFO (support.batch.BatchWorkInSessionExecutable) Configuring the end of batch tread execution
- 2011-12-06 13:54:24,747 [DEFAULTWorker:3] INFO (support.batch.BatchWorkInSessionExecutable) Closing log writer
- 2011-12-06 13:54:34,278 [GeneralBatchWorkManagerWorker:1] INFO (api.batch.AbstractBatchNotifier) Using mail server properties from mail sender context definition
- 2011-12-06 13:54:34,293 [GeneralBatchWorkManagerWorker:1] INFO (api.batch.AbstractBatchNotifier) Will use default email sender CM-EMAIL to send email notifications
- 2011-12-06 13:54:34,293 [GeneralBatchWorkManagerWorker:1] INFO (support.batch.BatchNotificationHandler) Notification message of end of batch run for CM-IMDD has been sent to [email protected]
Please help in this regard asap..
Thanks in advance

Hi Shaymal & VRMP
I have checked the system, the only problem I am facing is that the system does not show next inspection date dialog box at the time of UD where I can see the next inspection date being set by the system
Say, I use QA07 (Triggered Manually) on 19.jan.08. The Next inspection date was 26.jan.08 and Initial Run in Days was 10 (days), the system created inspection lot on 19.jan.08 successfully. At the time of UD it automatically set 29.jan.08 as the next inspection date (i.e. 19.jan.08 + 10 days) istead of 06. Feb.08 (i.e. 26.jan.08 + 10 days) without showing dialog box / suggesting next inspectino date.
regards
Mobashir
Edited by: Muhammad Mobashir on Jan 19, 2009 7:11 AM

It seems like I just missed the interval for the hard disk replacement program. I purchased in March 2009 a 24 inch Intel iMac . How much does it cost to have apple support at an Apple Store replace a hard drive?

It seems like I just missed the interval for the hard disk replacement program. I purchased in March 2009 a 24 inch Intel iMac . How much does it cost to have apple support at an Apple Store replace a hard drive?

My hard drive continually has the floating beach ball and will take massive time to fulfill a request. And then will not boot up...so then I have to do a restore and rebuild hard drive from a past saved time machine version. Works for a little bit...then the floating beachball comes more and more...until it will not boot up again. So then I restore from a previous time machine saved version....and again it works for a day or so ... until it happens again. Now it's happening faster and faster...so I think my hard drive is dying.

Driver interval timing

Similar Messages

Maybe you are looking for