cFP-2020 Locks up after 1-3 hours

[Ben]

BTW

Ames posted a seperate answer to your Q.

Ben

[seanpatrick]

Hi Ames,
I thought you had it fixed right up until a couple of minutes ago. I had put in a 7 second wait. it still locked up it just took longer. I wil upload the file ASPA and everone can check it out. Sorry ahead of time because it is a bit of a mess at the moment.

[seanpatrick]

Me again it is not letting me upload at the moment but I will try again later, the files may be to large. Houston has the code already but I have not hard anything from them in 2 days. Matt some times when it locks up I get a �4� code on the status light but other times it is fine. Some times when the when it locks up I can get right back into the cFP-2020 from labview other times I have to power down the module and it will come back up and then I can communicate with it again.. Ben when I ran your software at the same time it always showed about 14.5 Meg free. There is no data being save to the controller so I would expect it to stay level. So my search continues�

[Ben]

Hi Seanpatrick,

Continue with the posting attempts.

Molly K can help with posting large files.

Now that you say that re-trying helps, I do suspect the memory issue.

If other paths do not lead to a solution, concider using the Leds on the cFP as a diagnostic tool.

You can write a different led pattern when you code is in different states. This could give a clue as to what is going on inside the cFP when the problem occurs.

Please keep us updated.

Still trying to help,

Ben

[seanpatrick]

Molly is going to post the file for me. Right now I am running one of the example VIs to make sure it is not hardware.

[Molly K]

The attachment you requested...
Molly K
Web Support & Operations
National Instruments

[Ben]

Thank you Molly!

Sean,

I do not have LV 7.1 on my machine yet so I can not look at the code.

I'll let Ames help you for now.

If time permits, I'll try to get LV 7.1 loaded on a machine so I can look at your code.

Ben

[seanpatrick]

Ok not much new yesterday. But I did have a FieldPoint support engineer tell me it was a problem with the real time code and an RT engineer till me it was a hardware problem... It sounds just like this place. I blocked out 2 large sections of the code and am going to try to run what is left to see if I can track it down. Because the RT examples seem to run just fine I am back to thinking it is something in the code. I am using all of the com ports and on top of that I am hitting the 485 port kind of hard so maybe it has something to do with that. I will let everyone know what happens...

[Ben]

I'll watch for the update.

Ben

[cous]

Sean,
I have spoken with Ames and Yusif about the issue, and we are in the process of recreating and resolving the issue. I'll keep my eye on this discussion forum for any useful postings, but rather than post responses to the forum, I'll keep in direct email and phone contact with you.
Regards,
Marcus G.
Applications Engineer
National Instruments