jgcode Posted January 19, 2012 Author Report Posted January 19, 2012 Getting old, I posted in that thread but didn't remember it. Where is the smiley with grey beard? I wouldn't worry - I frequently embarrass myself. You just get used to it after a while... 1 Quote
matt.baker Posted November 15, 2013 Report Posted November 15, 2013 Apologies for reviving an old thread, but would anyone be able to save this GUID toolkit for LV2009? For what it's worth, attached is a zip containing three Create GUID implementations consistent with IETF RFC-4122:GUID LV11.zipVersion 1: TimestampVersion 3: MD5Version 4: RandomThe V3 implementation requires the OpenG MD5 library. Also included is a VI that generates a 100 ns base timestamp (used in the V1 implementation, actually works as advertised now), along with a typedef that is used in the implementations.There is no V5 VI, I haven't tracked down the SHA-1 library you have been talking about, but it should be trivial to modify the existing V3 VI (replace the checksum call with a SHA-1 and modify the version bitmask) if it doesn't already have the functionality you describe.If there's interest in having the Is A GUID method perform a basic timestamp validation for V1 GUIDs, I can throw some code together.-m Quote
jcarmody Posted November 15, 2013 Report Posted November 15, 2013 No apologies necessary. GUID_LV9.zip Quote
Popular Post mje Posted November 15, 2013 Popular Post Report Posted November 15, 2013 Since there's interest, I'll post a more up to date library I've been working with for the last few years, ported back to LV9. This library focuses on producing version 1 timestamp based GUIDs and is incapable of producing the same GUID twice assuming OS clock settings are not fiddled with. The caveat being if you somehow manage to run out of GUIDs for a given timestamp, the VI will yield to obtain a new timestamp, so this method can't be used in FPGA applications. It also fixes a subtle issue with random number generation. Note I have no idea if current hardware would even be able to exhaust GUIDs for a timestamp (it would require 16383 GUIDs to be generated within the resolution of the value returned by the LabVIEW time primitive), but suspect that if anything could, an FPGA may be able to. The non-timestamp methods have been removed-- I didn't see a use for them since there was the possibility of collision with those (however small it may be). LabVIEW.GUID LV9.zip Edit: sorry, originally posted the wrong zip. Fixed. 2 1 Quote
matt.baker Posted November 15, 2013 Report Posted November 15, 2013 That's great, just what I needed Thanks Quote
matt.baker Posted November 15, 2013 Report Posted November 15, 2013 Edit: sorry, originally posted the wrong zip. Fixed. I did wonder about that when I saw the same file size Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.