I need to modify an FPGA.vi that has already been deployed on a cRIO and runs at start-up.

[Joe D.]

Hi John, You should be able open the vi's under the compactRIO in your project to be able to run them; However you may need to rework any fieldpoint specific functions inside of those vi's

Also you may need the fieldpoint driver:

http://sine.ni.com/psp/app/doc/p/id/psp-855/lang/en

[Newton2this]

Wow!  That was a quick response!  Thank you Joe!  Have a good weekend!  John

[Newton2this]

Hi Joe,

Happy Monday!  I'm stuck on configuring FieldPoint to run on my system.  I installed the drivers you told me to and I see FieldPoint 6.0.5 from Start Menu > All Programs >Nation Instruments now but it looks like I can't import FieldPoint configuration files into LV Projects yet until I configure MAX.  I have attached a word document screenshot of my project explorer window.  I'm not sure what to do next.  John

[Joe D.]

Hi John,

You should be able to directly open the vi's without the project to see what is going on in them. Try this and let me know how it works out. 

[Newton2this]

Hi Joe,

Actually the vi's seem to be working fine but they (or the project) is not working as advertised.  If I disconnect the ethernet cable I am still getting error messages and I am not able to reconnect to the cRIO w/o at least closing the program and restarting it.  We will need to run all our programs from startup so I will need to build executables and installers.  Will that take care of some of the 'lost connection' error messages I have been getting??  I have heard error messages that occur during development don't necessarily occur after an executable is created.   I plan to try that out next.  - Regards, John

[Joe D.]

Hi John,

Would you like me to make you a good heartbeat example?

[Newton2this]

Actually, that would be great!  Thank you for offering.  John

[Joe D.]

Hi John,

Sorry for the late reply but here is an example of a heartbeat.

You will notice that there are two timed loops. The top one is the server that sends the heartbeat. The heartbeat is just a simple boolean that sends a squarewave that changes every 1000ms (this can go as fast as 20 ms).

The second loop is on the client and detects the consistent change from the server if the change is detected that counter is reset, if not the counter is increased by one. Once the counter reaches a certain value the psuedo watchdog engauges and runs your failover code. In this case, it is just a string output.

Hope this helps

[Newton2this]

Hi Joe,

Your example may come in handy.  Can you tell me what's going on in the true cases of the Case Stuctures? My customer has come up with another solution and it will be interesting to compare the two!  thanks again,  John

[Joe D.]

so the first case structure (under left) checks to see if the signal has changed. If so (true) the counter resets, if not (false) the counter increments.

The second case stucture (lower right) checks to to see if the counter goes about a cricital theshold if so (true) a warning is generated if not (false) all is well.

The code is a vi snippet so you can save and drag and drop the file into a block diagram.

Please let me know how this turns out