viSci

With the help of my NI inside sales rep, I was able to get a cDAQ Linux installation image and instructions to restore and existing Linux chassis or convert a WES7 to Linux. NI was very protective with this stuff even though the Linus RT source is published on GIthub.

I was told if you are within the first 30 days you can send it back to NI and they will replace it with your OS of choice. In my case that is not possible so I have to find a way to do it myself. I found this document http://www.ni.com/product-documentation/54592/en/ which alludes to being able to restore a cDAQ image or even make it a dual boot device but details are lacking.

I have two cDAQ-9133 controllers, one with WES7 and one with LinuxRT. I would like to convert the cDAQ 9133 with WES7 to LinuxRT. Both cDAQ's were purchased 6 months ago to determine the best OS for our application. I have gone through all of the forums and it seems like I might be able to use the NI recovery disk or possibly a disk cloning utility like acronis or similar. Has anyone had success doing this?

Sharp LV developer needed for design / implementation of large scale distributed data acquisition system. Skills Needed: LabVIEW Real-Time, Publish Subscribe, Messaging Protocols, Data Distribution Services (like RTI-DDS, RabbitMQ, etc), DB Stored Procedures, Tree Structures, TDMS. This is a 9-12 month contract position in Gainesville, FL. Please send CV to mike.sachs@viscience.com

Just curious, what is the advantage of the MQTT implementation over off the shelf RTI-DDS now built into LabVIEW for windows and RT Linux

Can TestScript be used with Python v2.7?

Started putting together an example and found that the flatten and unflatten work correctly. The problem was in the file write which had the 'convert EOL' option enabled. Thanks for your help.

I often use variant attributes as a quick and dirty dictionary. I found out that I could flatten my 'variant dictionary' and save the flattened string to a file. I tried to unflatten the saved string and reconstitute the variant and its attributes but am getting an error 116 (Unflatten or byte stream read operation failed due to corrupt, unexpected, or truncated data.) I am using a variant constant because the variant dictionary I created has no datatype other than the attributes which are all 1D string arrays. I am beginning to think that this might not be possible to do, but thought I would check in to make sure I am not overlooking something.

I am looking for alternatives to using Systemlink to manage a large network of WES7 cDAQ's. I imagine there are many windows server tools out there to manage software deployment, replication, remote monitoring, etc. I am hoping someone might have some experience in this area and could offer a few suggestions on tools that would work well for the NI ecosystem but not require being an IT specialist. Thanks.

Systemlink was designed for such use cases. The only negative I have with it is the pricing model which is based on the number of nodes in your network.

I was wondering when someone would mention the long forgotten but hopeful promise of Teststand Lite. I doubt after all these years NI is going to provide this. It is likely something that will only happen with community support.

Finally, It works! Sometimes a clusterasaurus is just what you need. The cluster within cluster idea is a neat trick, thanks Rolf.

Not sure were the 1024 comes in as AES key here is 32 bytes and the ReconFile path is 260 characters. As you said to get 260 I would have to append two clusters. Here is my latest clusterasaurus... Unfortunately this still is not satisfying the DLL. It is not blowing up but returning an error indicating an invalid parameter so I might not be too far off...

I like the idea of a cluster within a cluster. Is it then possible to just use an array to cluster going into a cluster bundle to add in the fixed arrays?

So does every *struct passed into a dll need to be flattened to a byte array? I guess in the previous case it only worked because I was passing a empty array in the cluster. So for something like this: // Structure to pass reconstruction parameters struct RECON_INFO_STRUCT { unsigned int cpmBlkSize; unsigned int sepTimeDelta; unsigned int sepByChannelFlag; //0=no, 1=yes unsigned int wavFormat; //0=mulaw, 1=pcm unsigned int decryptFlag; //0=no, 1=yes unsigned int AESKeySize; //0=128,1=192,2=256 char AESKey[CRYPTO_KEY_MAX_LENGTH_BYTES]; unsigned int makeReadableAfterReconFlag; char reconFile[MAX_PATH]; }; STATUS __stdcall SRVIVR_API_ReconFile(void* handle, char* partDataFileName, RECON_INFO_STRUCT* pReconInfo, void* pNotifyCB, void* pCBArg); Do I need to manually flatten everything to a single byte array or is there some way to use this?