I currently have a project that I am refactoring. There is a lot of coupling that is not sitting well with me due to typedefs belonging to a class, then getting bundled into another class which is then fired off as event data.
Effectively, I have class A with a public typedef, then class B contains ClassA.typedef and then class B gets fired off in an event to class C to be handled. Class C now has a dependency on class A which is causing a lot of coupling I don't want.
For my real world example I query a bunch of data from our MES, which results in a bunch of typedef controls on the connector panes of those VIs. Those typedefs belong to the MES class. I then want to bundle all that data into a TestConfig class and send that via an event to our Tester class. But, now our tester has a dependency on the MES.
I see a few ways to handle this. First is move the typedefs currently in the MES class, to the TestConfig class. The MES VIs will now have the typedefs from the TestConfig class on their connector panes, but at least the dependency is the correct "direction." Or, I can move the typedefs out of classes all together, but then I am not sure the best way to organize them. Looking for how others have handled these sorts of dependencies.
 

Hi, all I am doing now pulse oximeter project in labview. I have got signals from oximeter and waveform is generated in waveform graph. But not a smooth one. I need a smooth waveform like the image attached here. What are the applicable methods to solve this problem?

Hi all,

We are a group of students from the University of Cambridge who are developing a new data connectivity system for researchers like us, its up at https://rinocloud.com

It currently integrates with LabVIEW, Matlab and Python. The plugin will point your data directly at our secure storage where you can automatically add metadata results for easy and fast retrieval. We’re also rolling out plotting features for presenting the data, collaboration features for project teams and an integrated lab book.

We are looking for new users, researchers like us, to help us to get feedback from our product.  You’ll be able to directly influence the product development so that you get a data system that is useful for you.

Know more at https://rinocloud.com 
https://twitter.com/Rinocloud
 
Thanks, 
Helena

Hi,
 
I've decided to take the temperature on a known issue, that lvclass files retain knowledge of some of their old content after it's deleted.
 
Proof
For some reason I'm not allowed to upload lvclass files, so I'll describe it instead (using LV2014SP1):
 
1) Create a new class and save it on disk as class1.lvclass. No member data nor methods, file size on disk is 8 kB.
 
2) Add one piece of significantly sized (to easier see the issue) member data, I added a 1000x100 array of DBL (with random default data in it). Save the class again, and now class1.lvclass is 4604 kB (why so much, should be around 1000 kB?).
 
3) Delete all member data again and resave the class. File size on disk is now 1171 kB, I'd have expected 8 kB.
 
4) I can't ever get rid of that extra data in the lvclass file, not even when I "save as" to create a similar class.
 
Questions
A) What's the reason behind this issue?
 
B) Is there any way to really delete stuff from a class file, or is the only way to recreate every class from scratch if you want something truly gone?
 
C) Is there a list (perhaps internal to NI) of which problems this issue causes? Here I'm talking about stuff like this and numerous other threads about class data suddenly not being updated or member data or methods not being called correctly with DD.
 
Cheers,
Steen

I have a data file EMG signal .tdms, the signal represented by number of samples and amplitude (24bit data). I want to perform this signal into a time domain to perform spectral analysis EMG signal. 
I look forward to help me continue my project.
I send all write file and read file the signal EMG signals
Thanks so much.
P/s: Read EMG Signal read data file sEMG_1.tdms
EMG monitor write EMG signal acquisition to sEMG_1.tdms
 
Read EMG Signal.vi
EMG monitor_.vi