Neil Pate

Hmmm, I cannot seem to recreate that behaviour either, but am pretty sure I have seen something similar.

I have always actually disliked the fact that if you duplicate an event the IDE resets the Event Data Node to the full set. I have probably had this bug in the past but never actually noticed it.

Thanks for confirming Antoine. I have filed a bug report (for LV2017).

The first rule of the beta is... ;-)

Hi All, I have recently discovered a subtle, but potentially disastrous, bug that can cause the Event Data Node to get confused as to the order of items which appear. I noticed this bug in LV2013 SP1 and have verified it still exists in LV2015 SP1. Please can somebody try recreate this on their system. I have not bothered installing 2016 and 2017 yet so cannot verify if the bug still exists. To recreate the bug: Open the attached VI. Notice the NewVal output is used. Also notice the Source element has been hidden. Add a new event, the Slide Value Change event to the existing Numeric value Change event. Notice the Source element is now present again and now OldVal is used ES Test.vi

Why don't you just use a classic display and colour the background transparent?

Just so I am clear here you are making the distinction between OPC-UA and plain-old OPC? As long as I can connect to OPC-UA server from an OPC-UA client this is good enough for me.

Don't forget .NET calls in LabVIEW are extremely slow compared to DLL calls, something to do with the managed memory aspect. I seem to remember even simple calls taking several ms to return.

Got this solved "hopefully". I gave up on trying to mimic this in MySQL as my actual system will use MS-SQL anyway. I rolled out a MS SQL instance in AWS and everything pretty much just worked. Specifying the datatype for a column as datetime2 allows me to insert and query with precision of 7 decimal places :-)

Thanks James, I have probably just labelled my code poorly, when I set the "Re-entrant" flag to true it is because I want multiple clones.

Just stumbled on the toolkit from SAPHIR (thanks smithd for the heads-up in the other forum post). Pure TCP/IP implementation. http://forums.ni.com/t5/Example-Program-Drafts/Native-LabVIEW-TCP-IP-Connector-for-mySQL-Database/ta-p/3496603 http://www.saphir.fr/en/produits/gdatabase-for-mysql-7.html Worked first time Now I just need to figure out if it is worth $700 , and I have just realised that this is MySQL specific and I need to actually interface with MS-SQL for my real system. As an aside I am pretty shocked at how simple a basic TCP/IP connector is.

Hmm still not really making any progress with this. My DB definitely has millisecond data in it. I have a table t1 with a single column of type DATETIME and have two records in this table, both with millisecond precision. If I execute the query from the server I get back the milliseconds, but the same query from within LabVIEW drops the milliseconds. It seems this is an issue with the OBDC driver, but I am not sure how to solve this. It has been suggested to perform an on-the-fly conversion to text as per my previously linked thread, but I cannot get this query to work properly. Any ideas?

This is exactly the same method I use. I use it to dynamically launch single instance of VIs that are never expected to be re-entrant, and also re-entrant clones. The only difference for the re-entrant clones is the flags used to open and the VI itself needs to be set to re-entrant. The two flags in the VI below are just the 0x80 and 0x40 flags.

Using the standard DB toolkit I cannot yet retrieve the fractional part using, but this could just be me doing something wrong as I have seen threads (like this) which states it should be possible. I have now confirmed using the mysql tools on the server that I can insert and retrieve fractional seconds using the DATETIME(n) type where n is the number of decimal places. Will do some more digging tomorrow.

Finally upgraded and of course the command to create the table did not work... because I had a mistake in. CREATE TABLE t1 (t dt DATETIME(6)); The "t" above was the remname of another column I had deleted from my query to simplify it, but obvsiously did not delete enough of it. Should be: CREATE TABLE t1 (dt DATETIME(6)); Still don't know if this has worked but getting somewhere slowly.

Update: looks like my LAMP VM appliance is actually shipping with MySQL 5.5 which does not supprt fractional timestamps.. Updating at the moment...

Hi guys, I need to be able to insert and retrieve a timestamp into an SQL database with miliisecond precision (ideally three digits of precision). Complicating the issue is that my final system is going to be hosted in a MS-SQL (so T-SQL) DB, but I am testing locally using a LAMP stack. I have done quite a bit of digging, it seems T-SQL would like me to use datetime2 type, but this is not available in MySQL. Apparently I can should use DATETIME(3) as the type. I am struggling to create a table with this as a valid column. I am using a LAMP VM appliance which I believe is running the a version of MySQL that supports fractional timestamps, but the SQL statement to create the table is failing. CREATE TABLE t1 (t dt DATETIME(6)); Any ideas what I am doing wrong? Secondly, it looks like the NI DB Toolkit has very primitive support for timestamps, and people prefer to use strings? Can anybody share their current "best practice after having done it wrong a few times" with me? Beer on me for solutions Thanks

Filipe, I do not see NI getting into the business of suing the end users of LV FPGA. Not that I disagree with your points, I just think it is unlikely NI would go after anybody other than the obvious primary culprit. Now, even having said that, I am still not going to expose my company (or my clients) to this risk and will choose NI officially sanctioned products over questionably legitimate offerings.

Yeah but haven't EULAs been proven to be pretty much worthless?

Could it be something to do with the fact that those two funny looking icons are expandable XNodes at edit time and expect to be redrawn on the diagram?

But they are kinda ByVal as you wire into an indicator to actually display the image. You cannot just make that association once and then assume it will automatically get updated.

Bingo! Thanks James. So Image refs are just plain old normal U64 size refs? I sometimes wish there was a way to see refs as native "pointers" in a probe rather than the special type (i.e. the image). I suppose I could create a custom probe and just display the U64...

More strangeness (probably just me not getting something). Why are all four Image references the same?

Hi gang, Simple question, can I treat a Vision Images ref just like any other U32 ref with all the rules applicable like forking wires etc? It seems to me that there is some kind of special stuff going on with Vision Image refs. Another related question, in my particular use case I have a piece of code generating a user event with an image as the data at some arbitrary fast rate. The act of Generating the user event creates the a copy, right? Some other code wants to process some of these frames (at a slower rate) and then I use IMAQ Copy to make a local copy, is this IMAQ Copy necessary or could I just hold onto the "Image" reference coming in from the user event? In the code below Images is just a local buffer I plan on using. The reason I ask is I am getting some weird behaviour whereby destroying my Images refs as shown in Capture3.jpg kills my acquisition code as well. (I presume because I am forcing all images to be destroyed, but I am surprised this is happening)