Leaderboard

The typecast node will never use the input buffer for the output. In fact not only will it copy the entire buffer, on Intel processors it will visit each element to put it into big endian format then visit each element to put it back to little endian. If an API requires users to typecast significant amounts of data, I would consider that a deficiency in the API that should be redesigned. For cases where the array elements are the same size, it would be possible to write a DLL that took both types and swapped the array handles. Be sure to configure both parameters as pointer to array handle then swap the handles.

I opened a thread in the idea exchange for this: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Inplace-Typecast/idi-p/1771970

No direct calls to a dll. I use this http://lavag.org/files/file/146-opp-push-file/ with the widcomm. If you are having difficulties, then you could try this http://bluetoothinstaller.com/

Hi All, Here in the UK we have just completed our annual NIDays conference where we were lucky enough to get the first public preview of something R&D have been working on. There is an app for iPad and Android tablets to allow you to monitor shared variables and web services on a configurable graphical display. This is currently in internal beta but you can see the preview by going to the National Instruments channel on IET.tv and looking for the future technologies in LabVIEW video.

http://tv.theiet.org/channels/ni/12076.cfm

Well what can I say. I am posting this from my new ..... Wait for it Ipad2 Yes, at the weekend I went into a shop and help both a Zoom and an IPad in my hands at the same time and played with them and the IPad won for me. Mind you all Sunday, I wanted to throw it in the bin. I was updating to IOS5 and it failed so went into recovery, then nothing I could be would get it working again. I uninstalled iTunes and reinstalled it, tried a laptop and a PC. On Monday morning somebody at work had a go and it worked first time. I did not know if I was really please or really pissed off. Anyway, I have had working a couple of days now and really like it, Lava looks great on the IPBoard app Cheers all Danny

This is what I actually did for getting rid of the buffer allocation, basically switched from array of I32 to an array of cluster of I32 and SGL as type for the RTFIFO for the interloop communication. Now the typecast is done in a lower priority loop where I can tolerate the timing/jitter induced. The general question remains... is there a way of an inplace typecast in LV?

Very nice...I always use the VariantDataType VIs, and have never thought about using Flatten to XML to get more info out of a refnum than what those VIs provide. Your approach looks solid...find the <Name> tag under the <ActiveXType> tag and you should be good: <LvVariant> <Name>Variant</Name> <Refnum> <Name>ActiveX Container</Name> <RefKind>ActiveX</RefKind> <ActiveXType> <GUID>{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}</GUID> <Name>Acrobat.CAcroApp</Name> </ActiveXType> <Val>0x00000000</Val> </Refnum> </LvVariant>[/CODE] It's not often these days that I get to add something new to my LabVIEW bag of tricks...

How about this? It may require more testing to eliminate things like String controls that contain the search text, but that's easy enough (depending on the application).