N95 Clock Unreliable

The Clock on my N95 cannot be relied upon to keep accurate time. Sometimes it looses a few minuits or even an hour.
It does not matter whether I activate the Network Operator Auto-Update. The SIM in my N95 is quite new Vodafone contract SIM. I am using software version 21.0.016.
I have had some problems with my N95. The Z drive seems to get bunged up if I use too many heavy applications but can be resolved by restarting the phone having removed the battery for 20 seconds.
Maybe I just have a bad phone and I need to wait to get a N96?
Any help would be appreciated.
Adrian
Adrian Smith

I use several applications but not all at once. I often use GPS apps that work well. Messaging, SMS and Email and the Web browser are often used. I like to play music and games (Sudoku). The other application I often use is My Messenger to chat on Windows Live Messenger. I do use the photo and video applications but less often. However I cannot say any one particular application causes a problem.
I use my N95 more widely than most people.
Adrian Smith

Similar Messages

Gusto 2 alarm clock unreliable..advice?

My Samsung Gusto 2 alarm clock has become unreliable, which is a luxury i cannot afford on my job for various time related tasks.
Does anyone have any advice?

Hey paul_r!
Depending on my phone and the alarm clock going off has become a norm for me so it's now become a goal that I get your working just as flawless as mine. So, let's jump right in and fix it up. How long has it been unreliable like this? Does it simply not ring despite having the correct time set? And have you had any other issues present?
Now, I didn't want to just leave you hanging so if you can please try a few basic things. Sometimes dialing *228, choosing option 2, waiting for completion and then restarting your phone may help a great deal. This well help things resync with our network so we can isolate the issue. I hope this helps.
EvanO_VZW
VZW Support
Follow Us On Twitter @VZWSupport

N95 Clock

I took my N95 to a Care Point for software update. After restoring all data from memory card, everytime i try to open clock, i got error message saying system error. What can i do?

To do a hard rest:
-Turn off your phone and backup everything
-Press and hold- 3,* and the green call button
-While doing that, turn your phone on
-When you see signs of life, let go of the buttons
That's right people, I'm back. Where have I been? I have been getting a life, away from this electric madness.

N95 Clock System Error

My N95 has suddenly started giving me a "System Error" when I try to access either the Clock program or the Time and Date update page from the Tools menu. Otherwise the phone works normally and displays the correct time and date on the display during normal operation.
I have tried to perform a "Factory Reset" and this does seem to cure the problem, but the error returns as soon as I perform a Memory Restore using the Nokia PC Suite backup/restore utility.
Is there any way to cure this problem without losing all my data and having to re-enter it again manually??
Regards

03-Dec-2007 04:25 PM
n95_pilot wrote:
My N95 has suddenly started giving me a "System Error" when I try to access either the Clock program or the Time and Date update page from the Tools menu. Otherwise the phone works normally and displays the correct time and date on the display during normal operation.
I have tried to perform a "Factory Reset" and this does seem to cure the problem, but the error returns as soon as I perform a Memory Restore using the Nokia PC Suite backup/restore utility.
Is there any way to cure this problem without losing all my data and having to re-enter it again manually??
Regards
try to get the latest N95 software, ya know NSU...

After Gingerbread update, clock unreliable

Seems to only synch at random times. I googled this, appears to a common problem with GB. Anyone else seeing this?

azdsrt wrote:
Seems to only synch at random times. I googled this, appears to a common problem with GB. Anyone else seeing this?
The widget "time & date" was changed so that it no longer displays in the 4x1 format that I use. I downloaded a free-app and it's better (bigger text). But, I have not had a problem with it keeping time. I have 2 clocks on the screen, 1 with a second hand, and they seem to be working well. But, I will keep an eye out.
BTW: the Verizon network time is 15 seconds faster than the NIST National Time Reference clock, and every computer synced to it. So, it runs 15 seconds faster than my work and home computers. But it has been consistently fast.

N95- most unreliable phone ever.

Had one which had a microphone defect. Then the same one had a problem with battery life. Then the same one had problems with the wrong buttons doing the wrong things. Then that one got replaced with a brand new one. That one now had a problem with the camera, where it will either stay black or won't focus.
Biggest waste of money.

My N95 is now playing up again and it will be the third time in 18 months that I have had to return it for repair. My husband had one at the same time as me and his has never (touch wood) broken down but mine (I am a more regular user of the phone than my husband) has had the screen breakdown on me twice, first time it went multicoloured and I couldn't receive calls or texts, second time it just went black and then this morning it just started to play about 3 seconds of each track I have on the phone. I am very dissatisfied as I need my phone due to being self employed. I have always had Nokia phones and this is the first one that I have been disappointed with.

N95-1 The date next to the clock

How do I get the date to appear next to the clock in a n95-1 in "standby mode"?
Solved!
Go to Solution.

you need to select the analogue clock in time and date settings the date will appear inside the clock
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Clock application on N95

Don't know if anyone can help but if I try to access my clock (date and time menu) I get the message 'System error!'. This prevents me from being able to set alarms which is a little frustrating!
If i go the the time and date option and try to access the application, nothing happens......
Any ideas?!

I really don't understand, how can this problem persist after 4 years. I just got an N95 from a friend because my phone died. The N95 wasn't used for 3 years, so the firmware was really outdated. I've done an update, and I got this clock problem... Of course, there is a solution for it, but I'd rather see that Nokia has been working on this issue and I wouldn't have had to spend hours finding and applying a solution.
This thread isn't really helpful either; after factory restore, I had to manually find out which backed up info can be restored, and which can't be, assuming that I don't wanna get system error when trying to set up an alarm. After 3 factory restores (after the first one I restored the backup file completely... opening clock... system error. After the second one, I restored the elemets one by one, and after each one, I checked wether I get system error. The third restore came after finding out that SETTINGS stored in the backup file shouldn't be restored, because I got system error after restoring them.) I can't beleive it's an unsolvable problem for software developers, I think they simply give.
So people, may any of you have this problem:
1: backup using PC Suite.
2: factory reset (it might be a good idea to save music, images, vids, etc. on your pc from the memory card and format it as well. Applications installded should be restored one by one, manually)
3: restore the PC Suite backup file, but DON'T RESTORE SETTINGS FROM IT!!!
Your phone shuold be fine after this.
cheers
MODERATOR'S NOTE:
We have edited this post because of the wordings used. We encourage users to moderate the choice of words posted in the forum to maintain a friendly environment. Thank you for understanding.

N95 8gb clock standby display

Anyone know is it possible to light the time up during the night by pressing one of the buttons on the N95 8gb. Tried most but it just lights up the main screen. I know on the Sony Ericsson models you can press volume to light up the time. Thanks in advance
Solved!
Go to Solution.

cClock screensaver will do what you want.
http://home.pacific.net.sg/~welic/cClock.html
Set "Always on top" to "Yes". Then pressing any key on the phone will light up the main screen, showing the cClock large clock.
Press the red hangup button to show the normal phone display.

N95 World Clock

Hi, I have been using the World Clock feature on my N95, with just two cities... London and Caracas.
The problem is that it is displaying the wrong time for Caracas because Venezuela has changed its official time from GMT -4:00 to GMT -4:30. There has been no software update to compensate for this.
Please help

You need to email Nokia for that, they are may not be aware of the change especially if it has been recent.

Question re standby clock N95

Hi,
I've just got an N95. With my SE K800 when it was in clock 'screensaver' mode you could press the volume keys on the side to cause the back light on the screen to illuminate so you could see the clock-pressing other keys would take you to the main screen. Doesn't seem to work this way on the N95-it's retarded-when I wake up in the night etc I just want the little status screen saver to be illuminated so I can read the time etc.
Any ideas-anyone else understand what I'm on about?!
Cheers.

10-Nov-200711:47 AM
mexpress wrote:
I know that dude, I was wondering if there is anyway to have it so that a single key press (one of the side buttons would be perfect for this) will simply illuminate the standby screen for a few seconds without having to open the phone, use multiple key presses to unlock the phone and without sending it into full on lights-alive-mode. Anyone who has used the SE phones will hopefully understand what I mean.
Just another thing I'll have to get used to, like not having a stopwatch or countdown timer as standard....
the stopwatch countdown is a problem i agree there
BUT there is a work round for the stopwatch
http://europe.nokia.com/A4323689
download and install sports tracker from Nokia
you will find it has a great big stopwatch to time events but you can time any thing with it
Nokia user / modder since Nokia Orange and Mobira user too before that

Clock n95

Hi
Please could someone advise me to get a new analogue clock do I have to install a full new theme ? - I am looking for a good analogue clock with 2 10 20 25 etc minute markers
MTIA
Steve

you need new theme go to nokias new beta site for great stuff the site is called MOSH
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Snooze problem since software update on N95

I've had my N95 for about 18 months now. I don't use a lot of the things on it, but one I do use is the alarm clock to get me out of bed in time for work. I like to have a bit of "coming around" time so I usually have a few snoozes before getting up. I generally switch the phone off at night so I don't get woken by text messages and calls.
This has worked fine since I got the phone.
However, this week I upgraded to the new software and since then I've had the following problem -
When the alarm goes off and I press snooze (which makes the phone switch off again)the alarm doesn't come on after 5 minutes. However, once I turn the phone on the snooze alarm immediately comes on even if this is 10 minutes after it should have.
I tried the following test to try to replicate it once I had got to work. With the phone on, set the alarm for a few minutes in the future, then snooze - works fine. With the phone off do the same - works fine.
So it appears that this problem either happens when the alarm is for the following day or when the phone has been off for some time.
Has anyone else found this and does anyone have any suggestions of how it could be resolved?
Thanks

This all happened a while ago so it's going to be buried deep down in the forum. What I can do is summarize the problem here.
If the phone was switched off before midnight and left off overnight the clock would jump forward several days from time to time.
This would cause alarms not to go off at the desired time.
The snooze function was dysfunctional. Regardless of the snooze time set in the clock's settings, if you decided to snooze an alarm it would snooze for the default 5 minutes and sometimes freeze the phone up when the snooze time was up.
The workaround for these problems is to leave the phone switched on overnight, which is why I never noticed them on my N96 until reading about them here - I leave it on overnight. It doesn't fix the snooze duration problem but it does prevent the phone from freezing, which is a good start.
I think you'll find that the Nokia developers are already aware of this problem. When there's a huge outcry of despair like this on these forums, the moderators do pass the information back to the dev teams.
Was this post helpful? If so, please click on the white "Kudos!" star below. Thank you!

My N95 review

It’s almost a year now that I was waiting for this magnificent piece of technology, I mean 5 megapixel camera, 3.5G, WLAN, S60…what could you ask for more? Surely the N93 turned heads with its twisting and turning but this baby did more than that.
So let’s see my first impression after I opened the box…it looked exactly like those ads we see everyday on the highway or on the internet, only smaller and better looking.
I saw a huge screen with QVGA resolution and 16 million colours, 13 main keys including a joy-pad, a stylishly placed camera popping out of the housing, a speaker, and that infamous Nokia N sign.
On the right side of the phone I see something that reminds me of the N73, not just the colour, but those blue backlighten keys. Up and down, gallery, autofocus and camera buttons and also a “chrome” speaker grill with 12 holes.
On the left side there is another speaker grill and a special 3.5mm jack of which I will speak about later, it also has an infrared cover and the microSD slot, very nicely built on the cover and easy to remove.
On the back we obviously find that awesome Carl Zeiss lens 5 megapixel camera with DVD recording and a powerful flash and even a stylish shutter. You also find the battery cover, which contains a BL-5F 950 MaH battery, same as the N93.
The top part has simply a ON/OFF/Profiles button while the bottom has a charger input, a miniUSB port and a microphone.
The phone is very thick, 21mm. We can compare it to the massive 7710 but its quite light for its kind, especially without the battery. The weight is 120g, it’s 99mm long and 53mm wide.
The main keypad feels weird for people who are used to Nokia’s soft keys. The soft keys are still there but they are made real thin as there are Menu and Multimedia keys next to them, so if you’re not careful, you will press the wrong buttons but eventually times cures everything.
Time to slide the cover up and uncover an ergonomic keypad. This keypad is rather small for such a big space, but it’s not an issue, because the keys and modelled in such a 3D shape that it’s actually comfortable and pleasant to play with them. There is a line dividing the first row of keys from the rest, I don’t know why though. The GPS module is under the # key and the lock slide sensor is in the middle of the first row of keys. There is sort of a wall that looks like a cover of the phone: between the keypad and the cover there is a big space and you can rest your fingers there, quite nice and stylish I would say.
The keypad lightning is done very well, there are lines of blue light coming between the keys when it’s dark and it gives the phone that futuristic look. The lightning of the LCD is also done very well, a very bright screen but still a perfect contrast.
This slider phone got something I’ve never seen on a phone of its shape: the base is huge and the top slide is thin as a needle. But moving on to the other slide, I notice that when opening the slide, it makes an ugly and loud voice, oppposite of when closing the phone. Turning the phone on the pther way, activates the landscape mode. They multimedia keys on the left side of the phone aren’t keys, they feel like a touchpad, you can’t see them, they are flat, a stylish manouvre and an ergonomic choice, they are also blue backlit. When turning the phone to landscape mode triggers the multimedia menu which can be customized, and pressing the play button activates the music player. The screen’s rotation is quite fast and it doesn’t usually crash.
And then, there’s that camera shutter. Just like in a proper camera, sliding the shutter down activates camera mode, even if the keypad is locked, and only this way the right side keys will light up.
What to expect from this Symbian OS9.2S60 V3 with FP1? Oh well, looking from the past this OS seemed to be advancing to an extreme, possibly outlining Windows itself! But no…9.2 isnt that great unfortunately, perhaps I’m owner of a young version of it, my phone has v10.0.0.18 on it, and it behaves quite well in general, although no AGPS or FOTA on this version yet.
On the waiting screen we have that old S60 GUI with the active desktop, WLAN status, shortcuts, operator, signal, battery, clock and the selected profile. We head to the menu and see the 4x3 assembly with animated icons or the choice of list view. There are 3 folders: tools, applications and office. There is a little tool called Search and was built in conjunction with Windows Live, some marketing from the Microsoft guys I guess. There’s also a Maps application which I will talk about later.
When you enter Settings you can see everything much more organised and clear, more functions, practicaly everything is connected to the Settings program, even the Themes.
The GPS Data application tells you the Latitude, Longitude, Precision, Altitude, Altitude Precision and Speed, and on the other tab you can find averages and bearing (compass). Then there is the actual maps application. You must have your country’s maps installed, as in doesn’t come with every country, unfortunately most African countries aren’t there which is bad for me as I’m somewhat an explorer. Another disadvantage is that voice navigation is costly. You can see roads, petrol stations, define and save places with the application. The search button doesn’t work well as my searches always return no results, and the GPS takes quite long to startup. The latest firmware version (12) offers Assisted-GPS but that will need some sort of internet connection. The voice navigation cost 106$ for 3 years.
The web browser is very advanced, letting you open different windows, offerring minimaps and a mouse cursor, quite lovely. It also plays Javascript and flash animations.
The music player improved a lot, let’s you search for music, shiws album art and has fantastic visualizations. It has 6 predefined equalizers and you can change the settings on 5 of them. There is a modern multi functional headset device of which I will talk about later on.
In the Office folder you can find a Zip application, I wonder what does…There is also a Video Centre application which streams/downloads videos from different sources like Reuters.
When it comes to connectivity, the N95 is king. Starting with Bluetooth 2.0, transfers at full speed and up to 6 devices at the same time. Followed by the old infrared system, and then the ever-growing Wireless LAN, which let’s you easily access internet and join networks. Unfortunately you cannot create networks with other phones.
Then there’s our lovely HSDPA or 3.5G. Fast browsing and downloading at 1.8mbps, just awesome. If that doesn’t work, there’s 3G, EDGE, and EGPRS which is an advanced class of GPRS.
There’s also a miniUSD port which when connected with a cable provides Mass Storage, PC Suite, Media Player and Image Print options. Of course Mass Storage won’t activate if you got a theme or an application running from the memory card.
As I said before, I would like to especially talk about that 3.5mm jack on steroids. Normal jacks offer just a two channel input or output. This one has 3 channels, both input and output at the same time, which is a wonderful connection by Nokia, I haven’t seen it or atlease noticed it anywhere else, so for me, these small details count a lot. This special jack helps with the audio controller and also makes way for TV-Out. It can be used normally and connected to stereo systems.
Now it’s time for the camera, it offers 0.3mp, 0.8mp, 2mp, 3m and 5mp resolutions. There are options such as: capture mode; flash option; timer; sequence mode; light compensator; white balance; colour tone; ISO sensitivity; contrast; and sharpness.
Video mode at 640x480 30fps has options of mode, white balance and colour tone.
What was really missing here is optical zoom as its digital zoom is unfocused. The front CIF camera works poorly as it’s only for video calls.
The flash is very powerful, in totally dark situations, it looks like daylight, especially indoors.
The sound on this device is great, 3D Stereo speakers offering a loud quality music output, even as a loudspeaker for calls it behaves perfectly. Unfortunately the included stereo earphones are really soft, so you might have to get a new pair. The memory card included should be enough to store about 300 songs, it’s a 1GB. The music can be converted through PC Suite, but this phone supports most music formats so it won’t be necessary unless you wish to change the bitrate.
Now any phonehas faults, and the N95 is no exception: the lights on the multimedia keys off during music playback, not nice if you are driving at night and want to pause the song as you won’t be able to see the keys. The battery doesn’t last long, 950mah is very light, and if the default screen saver isn’t set to an acceptable time range, the phone will die very quicly as the screen consumes and extreme amount of electricity. If you use the phone moderately, let’s say for internet and music, you will end you charging it every night or so.
The top slide isn’t assembled properly, you can see some cracks and openings on the sides, and white light escapes minimally, this tells us that the phone is very fragile.
The sildes makes a huge noise as I said before, this problem doesn’t exist on the competitors, and Nokia failed there.
If you have a third party 3D theme running the phone will considerably slow down, especially on typing.
When playing Java built games, the phone’s battery lasts long enough, but when playing SISX games that push the powerful Graphics IC to its limit, the battery drains quite badly.
Java applications all drain the RAM very badly and the phone crashes if you try to multitask, making me restart the phone, and that can get irritating for heavy users like me, as you will have to restart 5+ times per day.
The phone comes with a good audio controller for earphones or an external audio output. The controller features a microphone, a 3.5mm stereo jack, a holder, a security key lock, volume up and down, answer button, play, forward and backward buttons.
The provided earphones have an extremely short left ear cable and a long right ear cable which is not very comfortable.
A TV-Out cable is also provided.
Advantages: 5mp Carl Zeiss camera with Autofocus; DVD-like recording; Powerful flash; loud speakers; 3.5mm jack with 3 channels; HSDPA; GPS; S60 OS9.2
Disadvantages: Weak battery; GPS takes long to startup; OS is still young in some aspects.
Rating: 9.8/10
full review at: http://merajchhaya.googlepages.com/nokian95
Visit http://www.phonereport.info for the latest phone news

02-Aug-200703:19 PM
dfulgo wrote:
...hmmm, very interesting...
- BT in compliance with NOKIA point of view, BT protocol missed.
- Outlook sync according to NOKIA way, SyncML protocol missed.
- History calls ALWAYS with mobile icons, CommonSense missed.
...so, no matter if the new firmwares are getting things worse than before?
...wow, Nokia, you're right, continue in this direction, your Customers will never be disappointed, they simply don't care...(sigh).
you are quite right, i guess i never noticed those details
Visit http://www.phonereport.info for the latest phone news

Buffered event counting. Why can't I explicitly sequence generating the Sample Clock Pulse and reading the counters?

At irregular occasions I need to grab counts from several counters, and buffering the counts must be done simultaneously for all counters. I'm modeling my approach after zone.ni.com/devzone/cda/tut/p/id/5404 which someone kindly pointed out in an earlier thread. However, that example only uses one counter, and you can't test the synchronization with only one counter, so I am using two counters configured the same way, and they're wired to a single benchtop signal generator (for example at 300 kHz).
What I want to do, I can test in a loop with a somewhat random wait in it. I want to drive a hardware digital output line high for a few ms and then low again. The hardware line is physically connected to terminals for my timing vi's Sample Clock Source and so will cause them to buffer their counts for later reading. After I pulse this line, when I know new good buffered counts await me, I want to read both my counters. If their bufferings are simultaneous, then each counter will have counted the same number of additional counts since the last loop iteration, which I can check by subtracting the last value sitting in a shift register and then subtracting the two "additional counts" values and displaying this difference as "Diff". It should always be 0, or occasionally +1 followed immediately by -1, or else the reverse, because buffering and a count could happen practically at the same moment.
When I do this using a flat sequence to control the relative timing of these steps, so the read happens after the pulse, the counters often time out and everything dies. The lengths of time before, during, and after the pulse, and the timeout value for the read vi, and the size of the buffer and various other things, don't seem to change this, even if I make things so long I could do the counting myself holding a clipboard as my buffer. I've attached AfterPulse.vi to illustrate this. If I get 3 or 10 or so iterations before it dies, I observe Diff = 0; at least that much is good.
When I use two flat sequences running in parallel inside my test loop, one to control the pulse timing, and the other to read the counters and do things with their results, it seems to work. In fact, Diff is always 0 or very occasionally the +/- 1 sequence. But in this case there is nothing controlling the relative timing such that the counters only get read after the pulse fires, though the results seem to show that this is true. I think the reads should be indeterminate with respect to the pulses, which would be unreliable. I don't know why it's working and can't expect it to work in other environments, can I? Moreover, if I set some of the pulse timing numbers to 1 or 2 or 5 ms, timeouts start happening again, too. So I think I have a workaround that I don't understand, shouldn't work, and shouldn't be trusted. See SeparateSequence.vi for this one.
I also tried other versions of the well-defined, single sequence vi, moving the counter reads to different sequence frames so that they occur with the Sample Clock Source's rising edge, or while it is high, or with the falling edge, and they also often time out. I'll post these if anyone likes but can't post now due to the attachment limit.
Here's an odd, unexpected observation: I have to sequence the reads of the counters to occur before I use the results I read, or else many of the cycles of this combine a new count from one counter with the one-back count from the other counter, and Diff takes on values like the number of counts in a loop. I though the dataflow principle would dictate that current values would get used, but apparently not so. Sequencing the calculations to happen after the reads fixes this. Any idea why?
So, why am I not succeeding in taking proper control of the sequence of these events?
Thanks!!!
Attachments:
AfterPulse.vi ‏51 KB
InSeparateSequence.vi ‏49 KB

Kevin, thanks for all the work.
>Have you run with the little execution highlighting lightbulb on? -Yes. In versions of this where there is no enforced timing between the counter and the digital line, and there's a delay inserted before the digital line, it works. There are nearly simultaneous starts on two tracks. Execution proceeds directly along the task wire to the counter. Meanwhile, the execution along the task wire to the digital high gets delayed. Then, when the digital high fires, the counter completes its task, and execution proceeds downstream from the counter. Note, I do have to set the timeout on the counter longer, because the vi runs so slowly when it's painting its progress along the wires. If there is any timing relationship enforced between the counter and the digital transition, it doesn't work. It appears to me that to read a counter, you have to ask it for a result, then drive the line high, and then receive the result, and execution inside the counter has to be ongoing during the rising line edge.
>from what I remember, there isn't much to it. There really aren't many candidate places for trouble. A pulse is generated with DIO, then a single sample is read from each counter. -Yup, you got it. This should be trivial.
>A timeout means either that the pulse isn't generated or that the counter tasks don't receive it. - Or it could mean that the counter task must be in the middle of executing when the rising edge of the pulse arrives. Certainly the highlighted execution indicates that. Making a broken vi run by cutting the error wires that sequence the counter read relative to the pulse also seems to support that.
>Have you verified that the digital pulse happens using a scope? -Verified in some versions by running another loop watching a digital input, and lighting an indicator, or recording how many times the line goes high, etc. Also, in your vi, with highlighting, if I delete the error wire from the last digital output to the first counter to allow parallel execution, I see the counter execution start before the rising edge, and complete when the line high vi executes. Also, if I use separate loops to drive the line high and to read the counter, it works (see TwoLoops.vi or see the screenshot of the block diagram attached below so you don't need a LV box). I could go sign out a scope, but think it's obvious the line is pulsing given that all these things work.
>Wait! I think that's it! If I recall correctly, you're generating the digital pulse on port0/line0... On a 6259, the lines of port 0 are only for correlated DIO and do not map to PFI. -But I'm not using internal connections, I actually physically wired P0L1 (pin 66) to PFI0 (pin 73). It was port0/line1, by the way. And when running some of these vi's, I also physically jumper this connection to port0/line2 as an analog input to watch it. And, again, the pulse does cause the counter to operate, so it clearly connects - it just doesn't operate the way I think it is described operating.
For what it's worth, there's another mystery. Some of the docs seem to say that the pulse has to be applied to the counter gate terminal, rather than to the line associated with the sample clock source on the timing vi. I have tried combinations of counter gate and or sample clock source and concluded it seems like the sample clock source is the terminal that matters, and it's what I'm using lately, but for example the document I cited, "Buffered Event Counting", from last September, says "It uses both the source and gate of a counter for its operation. The active edges on the gate of a counter is used to latch the current count register value in a hardware register which is then transferred via Direct Memory Access...". I may go a round of trying those combinations with the latest vi's we've discussed.
Attachments:
NestedSequences.png ‏26 KB

N95 Clock Unreliable

Similar Messages

Maybe you are looking for