NI MAX corruption

[sesinfo]

Whomsoever seeing this post, personally after seeing certain community post and with personal experience I have always seen that due to abrupt shutdown NI-MAX gets corrupted now one has to mainly reset the configuration, and one should either should rebuild the tasks that were created and for that case one should always keep the .nce files as a backup, but my concern is that this is still not a very robust solution so can we anyone tell me whether is there any other way where I can prevent NI-MAX corruption due to abrupt shutdown of system?

[GerdW]

Hi sesinfo,

---

@sesinfo wrote:

is there any other way where I can prevent NI-MAX corruption due to abrupt shutdown of system?

---

Yes: don't allow such "abrupt shutdowns"!

[Jacobson · Accepted solution]

I know this isn't exactly a solution but I generally avoid relying on tasks/scales that are defined in NI MAX and try to define all of those tasks in LabVIEW for this reason (among others). If you do that and NI-MAX gets corrupted then the only information that's lost is generally hardware aliases.

[crossrulz · Accepted solution]

---

@Jacobson wrote:

I know this isn't exactly a solution but I generally avoid relying on tasks/scales that are defined in NI MAX and try to define all of those tasks in LabVIEW for this reason (among others). If you do that and NI-MAX gets corrupted then the only information that's lost is generally hardware aliases.

---

I go a step further and define the channels and tasks in a JSON file.  This makes it really easy for my application to adapt to a new MAX configuration.

[santo_13]

I always configure DAQmx Tasks and associated configurations in the application when setting things up. This ensures no additional work in replicating the application across test systems.

Of course, the alias must be properly configured in NI MAX.