Jump to content

mhenz

Members
  • Posts

    10
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by mhenz

  1. Has anyone tried to generate a client/server certificate for the NI OPC UA toolkit using the Encryption Compendium? I had no success, but it seems, that it has somethinh to do with incorrect attributes. BTW: The hexadecimal output of the ECL Sign.vi seems to have a final/additional 00h character at the end in the "Signature[HEX]" output. The "Signature[BYTES]" output is correct. The problem is located in RSA.lvlib:RSA_sign.vi, DSA.lvlib:DSA_sign.vi and ECDSA.lvlib:ECDSA_sign.vi. I can correct this, but don't know if this is a bug or a feature 😉
  2. here tested with LabVIEW 18.0.1f4 on windows 10 - no hang or crash and on LabVIEW 20.0.1 the same - no hang and LabVIEW 17.0.1f3 - no hang
  3. I've never done somethig like this. I used the LevenshteinDistance to compare a lot of smaller strings (between 8 and 12 characters long). Because each of the strings was more or less significant, I used an additional factor for each of the strings and finally generated some king of an overall coefficient.
  4. Thanks for the 2019 VIs. I compared the three algorithms. Levenshtein works different. For better comparison, I normalized the value with: 1 - LevenshteinDistance / (Length(a)+Length(b) Dice: Sørensen–Dice coefficient CSC: Compare String Confidence.vi Lev.: Levenshtein
  5. Regarding Levenshtein: Wladimir Levenshtein developed 1995 an algorithm for this. It is called the Levenshtein Distance. Some years ago I developed a VI to calculate the Levenshtein Distance. Here it is (LabVIEW 2016). Can you post your VIs in LV2020 or 2019, please. Levenshtein Distance.vi
  6. LabVIEW also caches DST. That's not funny if you measure some data at 1500 local time in USA (with or without DST), then go to europe (with or without DST and with or without restart of the program). Then load your data and want to see the correkt measurement time in all possible cases.
  7. now in LabVIEW 18 2400 swI Linear Stair MeasV.llb
  8. You created a couple of global variables. This is not thread save. double *Re_zArr, *Im_zArr, *RelErr_Arr, *Re_wArr, *Im_wArr; double complex z, w; int Npts; int i;
  9. Hello Sarah, I've seen your example at labviewforum.de. If the 'RS 232 Test 1' button is true, you transmit the data on COM3 (instead of COM5). This looks confusing and might be the problem.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.