Our online shopping is experiencing intermittent service disruptions.

Support teams are actively working on the resolution.

DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Kenny_K

Update Validation tool to verify that the Safe to Destroy VI was updated properly

Status: Declined

Hello @Kenny_K 

We are declining your request. We prefer to focus on the error that has caused the problem.

 

That said, thank you for your input. It is most appreciated.

Please keep those ideas coming!

 

Note regarding the update process: It is essential to upgrade from one version to the next and not try to go from an old version to the latest version.

Also, checking the code after each Validator step is a good practice. 

At some point during one of the upgrades from an older version of DQMH to DQMH 6.1, one of the upgrade VIs errored out (sorry, I don't have what the error was).

 

But the end result was that the Safe to Destroy Refums.vi was not properly upgraded, resulting in an issue where if there are multiple instances of the modules running, the module may never actually close and stop.

 

what was missing?

 

the input empty?  was not present, and therefore the boolean wire was not created from the Clone Registration: Remove vi.

Kenny_K_0-1686754549559.png

None of the Sempahore handling was on the block diagram of the Safe to Destroy Refum, it was a while loop from an older version of DQMH.

(I manually upgraded, so it is not exactly in the same format with comments, etc as the formal code).

 

Kenny_K_1-1686754679564.png

FYI - DQMH 6.1 Version of the Safe to Destroy Refnum vi

 

Kenny_K_2-1686754839622.png

 

 

 

Kenny

1 Comment
Olivier-JOURDAN
Active Participant
Status changed to: Declined

Hello @Kenny_K 

We are declining your request. We prefer to focus on the error that has caused the problem.

 

That said, thank you for your input. It is most appreciated.

Please keep those ideas coming!

 

Note regarding the update process: It is essential to upgrade from one version to the next and not try to go from an old version to the latest version.

Also, checking the code after each Validator step is a good practice. 


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!