What is error -1418 on a timed loop?

Has anyone ever gotten error -1418 on the error terminal of timed loop? It only executes once and I'm trying to run it on a cRIO-9004.
There's nothing in that range listed under the timed loop error codes.
http://zone.ni.com/reference/en-XX/help/371361F-01/lverror/timed_loop_error_codes/
Thanks as always,
Jim
Solved!
Go to Solution.

Hi Jim,
I belive this is what you were looking for:
Timing Sources Available for LabVIEW Timed Loop by Platform
Kristen H.

Similar Messages

Error -50103 occured with timed loop inside a while loop

Hello everyone,
i wrote an application to sample analog voltage from DAQ6024E card (see the attachments).
I have a big while loop in the VI because a I want to add some other functions later.
In the "WHILE_Cont Acq&Graph Voltage-Int Clk.vi" I use a while loop inside the big while loop to read the samples. It's working properly.
but when I use a timed loop inside the big while loop (see "TIMED_LOOP_Cont Acq&Graph Voltage-Int Clk.vi"), I get an error -50103 from the timed loop. It seems that the first cycle is ok, but after the first cycle the error occurs.
I don't know what happens with the timed loop, anyone can help me? what does the error -50103 mean? thanks a lot!
PS: I am using LabVIEW 8.0
Message Edited by molo511 on 10-22-2006 05:21 AM
Message Edited by molo511 on 10-22-2006 05:23 AM
Attachments:
TIMED_LOOP_Cont Acq&Graph Voltage-Int Clk.vi ‏143 KB
WHILE_Cont Acq&Graph Voltage-Int Clk.vi ‏75 KB

hi molo511,
I tested your program but only with simulated devices. I had to delete the wire to the timing, so that the timed while loop runs with 1kHz. Did you already try this? Because this works on my PC.
I also found a link in our database that might be interesting for you.
http://digital.ni.com/public.nsf/websearch/04BEDD9E9E91ED3486256D180048116D?OpenDocument
Greets
Philipp N.
NI Application Engineer

What is error 1418

it said that my ipod is corrupt and i need to restore it
but everytime i try to restore it, error 1418 shows up and says i can't restore it. what do i do

I had a similar problem with my old 512 iPod Shuffle. The restore feature in iTunes kept giving me a 1418 error, and I was out of warranty. Then I tried the restore utility: http://www.apple.com/support/downloads/ipodshuffleresetutility101forwindows.html
This worked! I did have to reload music, but at least the iPod is functioning.
I have an ipod video 60G which i bought october of
last year.
I also got that error 1418 thing after updating to
itunes 7.0.2. Everytime I try to restore, my ipod
would stop responding, which ofcourse would lead me
to unplugging the ipod improperly from my computer
(Macbook Pro). I brought my ipod to an apple center
after many tries and they were able to restore the
ipod using an older version of itunes. Stupid me I
reconnected the ipod to my computer again, hoping i
could replace my music back into the ipod - then
there it was again - ipod needs to be restored...
error 1418.
I decided to uninstall my itunes and reinstall the
older version. When i reconnected my ipod...
poooof!.... the display went out, and i could no
longer turn it on. In short, my ipod now is a piece
of crap. It's hopeless because even Apple doesn't
have a solution to it. Is this one was of eliminating
the older ipods and making us buy the newer ones,
which, honestly, doesn't seem to be practically
better than the last ones?
I hope i could still revive my ipod. too bad It's out
of warranty.
My advice: tell others not to download the new itunes
yet.

What is Error 1418 or 14118?

My Ipod 30GB Video died on Weds. and it came back to life
on Sunday. Ever since Sunday, I have been trying to rstore it!!! BUT Itunes says, that an error occurred and request can not be completed. The error # is 1418 or 14118? Good thing I saved the recepit(spelling?). Should I return it ad get another Ipod Video or Try to restore it again???
Please help!!!! PLEASE
Windows XP Windows XP

Have you had a chance to look at this troubleshooting page? It may be of some help: Error 1415, 1417, 1418, or 1428 when restoring or updating an iPod in iTunes 7 or later

Strange DAQmx Timing Source Timed Loop Error

I have a digital edge counter fed into a timed loop. Everything works fine until I stop the loop, and stop the DAQ task. Once I restart the loop it fails with "resource is reserved". Attached is my code.
Thanks
Solved!
Go to Solution.
Attachments:
daqloop.JPG ‏136 KB

Here is a piece of code to illustrate the issue. If the timing source is created in the loop (it will be created each loop iteration) the error occurs. If it is moved outside the loop, and only created once the issue is resolved. Is there a way to RELEASE the timing source so that it can be created again? If the VI is stopped, this "resource" is released. I want to programatically release it.
Note the error comes from the timed loop Error terminal that is Probed (50).
Message Edited by bkb on 10-08-2008 09:52 AM
Message Edited by bkb on 10-08-2008 09:53 AM
Attachments:
ts.jpg ‏57 KB

Unable to run Timed Loops

Bit of an odd one that had me scratching my head.
I have a development system consisting of a PC running a 7842R, acquiring analogue and digital data from the FPGA, loading it into a shared variable, and reading it out within a timed loop on the host as one parallel loop in a producer-consumer architecture.
All's well until one day last week when I noticed my host VI becoming unresponsive.
After a bit of digging, I find that the timed loop doesn't run at all. Replacing with a while loop with a wait at least allows me to show that the error is timed loop related, but it's not a viable long term option for me. Creating a new project and a new VI with a simple timed loop showed the same behaviour.
A restart of the system, and rerunning the same VIs, and no problems since.
So, questions:
1) Has anyone else seen this behaviour?
2) Any idea what causes it? A service crashing, for example?
3) Is there a way of recovering without a reboot? If it's a service crash, I'm hopeful.
The system will eventually form part of a production test environment, hence the query.
Edit - also, wiring error terminals of a timed loop is a good way of highlighting errors of course.
FWIW, LV2012 SP1 32bit, Win7 64bit, Core2 Duo, 4GB RAM, tassels from the handlebars etc.
CLD

The timed loop is used to read all elements from a DMA FIFO and load them into a buffer FGV, which spits out packets of N samples long once they've assembled within the FGV. Ordinarily, I'd do this with a timed while loop and be perfectly happy to do so. However, the elements are actually an interleaved array, meaning that I have to demux them in the correct order that they were loaded.
I use timed loops for a number of reasons: on my current Windows host, I've found that using a while loop has caused me more problems with respect to disordered packets, and that at least with using multiple timed loops (two, at most), I can assign priority to the acquire loop. Finally, it's also a development platform, and will be deployed onto an sbRIO once the electronics integration is finished in a week or two!
W.r.t. system resources, there's very little else running on that system, but that doesn't normally stop Windows
I recognise it's not ideal to run a software timed loop under Windows, but when you cannot run a blank project with Optimizing timed loop rate.vi from the shipped examples with nothing else running, it makes me curious to know why!
CLD

Timed loop in LabVIEW DLL does not exit nicely

Hello! I have what I think is a simple timed loop in LabVIEW that exits after 100 iterations by throwing an error, and letting the loop "stop on error". This works fine when run in the regular LabVIEW environment, however, when compiled as a Dynamic Linked Library (DLL) and called from LabWindows it forces me to terminate execution, rather than exiting nicely. What's more, it seems to quit the actual Virtual Instrument call just fine and proceed to the next line of code, but when my main() function in LabWindows completes there must still be something not cleaned up that is causing it to not exit nicely. Any ideas?   I've tried adding a call to QuitLabVIEW and that doesn't seem to do it.
Thanks in advance - hoping you'll point out some really easy mistake. )
Attached is a picture of the timed loop.
Below is an excerpt of code from LabWindows:
int main ()
CallMyLabVIEWDLL(); //This line successfully launches and closes the window for my LabVIEW virtual instrument
MessagePopup ("My Title:", "This happens after the call to your LabVIEW DLL");    //This popup shows up - indicating the call to the DLL has completed
//But after the code has completed LabWindows still says "Running", rather than shutting down.
    return 0;
Solved!
Go to Solution.
Attachments:
LabVIEWTimedLoopDoesntExit.png ‏103 KB

Update: I tried the simplest possible "While" loop and it works. If I replace it with the simplest possible Timed Loop, it doesn't. (See attachments.)
The only thing I could find in a search for why a time loop would break a dll is a patch for lvalarms from LabVIEW 8.5.1 .... I'm running LV 2010 so I don't believe that's an issue. Correct me if I'm wrong?
Thank you!
Attachments:
Doesnotwork.png ‏43 KB
DoesWork.png ‏9 KB

Unable to click on buttons during timed loop .

Hi !
I have a timed loop with a cadence set by user . And when the loop is running, I can not push any button of my GUI to stop this....
I have to wait until error or I stop the run.
I can't put the diagram it's too big and I think I haven't the right but do you have some ideas ?
Ask me for more details .
Thanks
Solved!
Go to Solution.

bejard wrote: The Timed loop is just in an event structure and I set 10 ms or 100 ms .
The program is running correctly (with this Timed loop of 10ms/100 ms) as the beginning but I still can't push any button or change tabs during the loop .
You should not have long processes inside of an event case. What is supposed to stop your timed loop?
I think you have the "Lock front panel until event case completes" option turned on. This will not allow you to press anything until everything in that event case (including the timed loop) completes.
In my experience, using a timed loop in a Windows system is a complete waste and often adds more overhead and issues. Instead, I really think you need to change over to use a State Machine. When the button is pressed, you just tell your state machine to go into the state the runs some of the code inside of your timed loop. You can use the state with the event structure to time your loop. So you can go back and forth from your event structure state to your processing loop. Just set the timeout on the event structure to whatever loop rate you actually want.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Stopping Timed Loop inside a Reentrant VI

I just converted a project over from 8.5 to 2009 and I found that some of the funtionality that was working in 8.5 no longer works in 2009 (probably for good reason...).
Anyway, I found that if I tried to use the stop timed loop vi to stop any timed loops in reentrant vi's that I get a -804 error. The stop timed loop sub vi was in the same reentrant vi in the application, but I found it also did not work if it was outside the reentrant vi.
It does get a little hairy when thinking which loop you are trying to stop because of the reentrancy, but if the names passed into the instances are different for the loops then it shouldn't be a problem right?
See attached for a very simple example of this occuring.
Note: Just running in windows...not in RT
Solved!
Go to Solution.
Attachments:
Stop Time Loop.LLB ‏41 KB

I resorted to using an alternative way to stop the loops as well. Does anyone at NI know if this is a feature or a bug or if there is anyway to use the stop timed loop function with a timed loop in a reentrant vi?
Thanks.
Whoops... Just read your post. Thanks for the update.
Message Edited by klessm1 on 01-06-2010 10:55 AM

CVS-1458RT - ISO I/P triggered timed loop

Hi everyone,
I am developing a real-time machine vision application on a CVS-1458 RT.
What I am aiming is a timed loop that is triggered via external clock (in my case a photoelectric sensor connected to an ISO input). All examples I can find are related to DAQmx devices, nothing related to visionRIO.
Question 1: Is this the best way to construct the acquisition loop? I want it to be condition based as to free-up the CPU from continous polling. If not, wht is the best way ?
Question 2: If the above method is OK, how can I setup the input node of my timed loop in a way to implement this ?
Thank you,
Omar

Hi Omar,
I was able to find some Vision-RIO examples in the Example Finder of LabVIEW. If you open LabVIEW and navigate to Help>> Find Examples.
In the Example Finder in the Browse tab navigate to Hardware Input and Output>> Vision Acquisition>> Vision-RIO.

What is wrong with this (timed loop error)?

I can't figure out why the timed loop is not starting and I receive an error -805 message. Any idea?
Thanks,
Ben64

Hi Ben64,
There's no obvious problem.
I tried the same and it works perfect.
So there must be a problem under the cover.
I have 2 suggestions.
1) There is a problem with your wiring -> the Error wire is not connected to the loops error out -> close timing source is executed before the loop is executed (Are you sure the loop doesn't even start ?)
2) Labview often uses Names to identify items (queues, images, semaphores,..... timing sources(?) )
I tried to open and close another timing source with the same name.
Et voila : I'm able to get exactly the error code you mentioned.
Is it possible you use the same name for a second timing source and this one is closed prior to executing the timed loop you've got problems with ?
Best regards,
Balze
Attachments:
timed_loop_2010.vi ‏37 KB

What is the best/most effective way to dynamically build a timed loop in LabView?

I am relatively new to labview (not to code in general) and am looking for the "LabVIEW" way to dynamically build a timed loop. This is what I am trying to accomplish:
I have several heaters controlled through labview using Labview's PID toolkit. This works great. I have no issues with DAQ in general. However, throughout an experiment, I want to change the set point of each heater. I could set this up fairly easily using either a timed loop or the wait vi if I knew exactly how many different set points there would be.
If possible, I would like to be able to read in a config file that includes the different times and set points for all heaters and dynamically create a loop that can handle this. I have tried using the Elapsed Time vi with an array of time targets; however that didn't seem to work.
Has anyone been able to do this? Does anyone know where I could learn about using LabView in this manner? All help is appreciated.

DHagan wrote:
I am relatively new to labview (not to code in general) and am looking for the "LabVIEW" way to dynamically build a timed loop. This is what I am trying to accomplish: I have several heaters controlled through labview using Labview's PID toolkit. This works great. I have no issues with DAQ in general. However, throughout an experiment, I want to change the set point of each heater. I could set this up fairly easily using either a timed loop or the wait vi if I knew exactly how many different set points there would be. If possible, I would like to be able to read in a config file that includes the different times and set points for all heaters and dynamically create a loop that can handle this. I have tried using the Elapsed Time vi with an array of time targets; however that didn't seem to work. Has anyone been able to do this? Does anyone know where I could learn about using LabView in this manner? All help is appreciated.
Write a tab-separated spreadsheet file makes it easy to use the write/read from spreadsheet files. Assuming you have a 2D-array of your times and set points it's just a question of setting up a for-loop going through the array row-by-row and extract the elements (expanded index array) to set your points and wait time.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Unrecoverable Error w/ Timed Loop

When I use a timed loop I get an "Unrecoverable Error" (status light on FP-20xx blinks four times) after compile and run - although not immediately. When I replace the timed loops with regular while loops everything is o.k.
TommyH

Hi TommyH,
Thanks for the information. I understand that all this stuff can be a little overwhelming. That's OK. We'll get through it.
Sounds like this is a case of the code not being able to execute within the allowed amount of time. So, in this case I would suggest not using the timed loop because the code will not be able to execute within 1ms. I would suggest using the regular while loop and using a wait until next millisecond multiple timer. You will need to experiment with the code to determine how long to wait. Give this a try and let me know how it goes.
Best Regards,
Brooks W.
National Instruments

IPod corrupted, error 1418 , what does it mean?

Ipod froze and than message appeared to synchronize with computer. After initial dramas with upgrading iTunes (lost my library in the process through uninstalling and reinstalling) the message appeared that the ipod was corrupted; suggested restoration to factory state, but could not do it due to error 1418. What does it mean?

Does this article contain anything useful?
(25748)

What determines Finished Late? flag in timed loop?

I've monitored the Global Start Time (and Iteration Start) from iteration to iteration in a real-time loop. These delta time between iteration starts varies beyond my loop rate (e.g. 1680 usec between iteration starts with a 1666 usec period), yet the Finished Late? flag does not indicate true. Maintain Phase is TRUE, Discard Missed Periods is FALSE, Deadline and Timeout are default (-1). So why does Finished Late? not fire when all clocks tell me the loop was late?

A (very) rough example is below and some results (run on an RT controller). I guess the loop didn't "finish late" but it appears that they can (and usually do) start (significantly) late or early so am I missing something? This jitter is there even when the Chart and Stop button are removed from the timed loop (e.g. using RT FIFOs to send the data to a chart loop). To some extent I answered my own question - my loops are not "finishing late" so the flag isn't set, but apparently the jitter here is significant. In this simplistic example, I saw jitter of +/- 4 ticks (usec) when the CPU usage is at barely 1% per core (dual core) - so is the RT jitter just bad in general or is it the 1Mhz clock or ???
Attachments:
RT Loop Timing.png ‏8 KB
RT Loop Timing Graph.png ‏14 KB

What is error -1418 on a timed loop?

Similar Messages

Maybe you are looking for