Daryl Posted October 25, 2017 Report Share Posted October 25, 2017 (edited) Labview 2016 XNET signal control does not fire change event. Is this a known issue? XNET event issue.vi Edited October 25, 2017 by Daryl Quote Link to comment
hooovahh Posted October 25, 2017 Report Share Posted October 25, 2017 This was a known bug a few years ago: https://forums.ni.com/t5/LabVIEW/XNET-ECU-Control-does-not-throw-a-Value-Change-Event/td-p/3106333 CAR #426378 was assigned, searching didn't come up with anything but I just tested it in LabVIEW 2016 32-bit in Windows 7 x64, with XNet 2017 installed and it worked properly so I think this is fixed. Just update your XNet drivers and you should be good. You can run 2016 LabVIEW with 2017 XNet. Quote Link to comment
Daryl Posted October 25, 2017 Author Report Share Posted October 25, 2017 On 10/23/2017 at 7:43 AM, Nishar Federer said: Hi, Can anyone suggest me a way to add the hexadecimal string to the notepad file ? Because currently i am getting only junk characters . Oh man, you mean to tell me I KNEW ABOUT THIS A FEW YEARS AGO and forgot about it? LOL, sucks getting old!!!! I will try your fix and see what happens, thanks!! Quote Link to comment
hooovahh Posted October 25, 2017 Report Share Posted October 25, 2017 Oh man I didn't even read the old threads I linked to, didn't realize it was you that originally brought this to my attention. I've done that a few times with TDMS memory leaking bugs that I found only to search the forums to find...I had already found it and posted it. Quote Link to comment
Daryl Posted October 25, 2017 Author Report Share Posted October 25, 2017 Ok, I just updated XNET to 17.0.1 and this seems to be resolved. Thanks again! Quote Link to comment
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.