Leaderboard

UPDATE: These first few revisions are more or less broken. The first fully working version can be found here. 8 Years ago the first version of the XNode Manager was posted to the code repository, and it hasn't seen an update since 2009. Being a fan of XNodes, but knowing that the XNode Manager is pretty limiting because of its age, I set out to make a new version with similar functionality. I didn't spend too much time on it, and I don't think it replicates all the XNode Manager functionality, but it does have some major improvements. The XNode Manager had a blank XNode, and blank Abilities that it just made copies of. This is fine but then the abilities and XNode are quite old. There were many new Abilities added since version 8.2 and you can't add them using the XNode Manager. My XNode Editor reads your LabVIEW resource and populates the list of abilities to create from the ones that are possible to create. Then VI server is used to create the XNode, State control, and Abilities. This sets up the connector pane like it should and should work with all future versions of LabVIEW, until NI changes something that breaks it. Be aware this uses several private functions, and several undocumented features that could be potentially bad. I did a decent test to make sure memory leaks weren't a problem and I made several XNodes and Abilities and it seems stable. But at the end of the day if it blows up and crashes, don't be surprised, you've been warned. Saved in 2013, but could probably back save earlier if requested. If I get more time I'll add some features, and add it to the Code Repository. XNode Editor.zip

I'll take that as a no...

DISTek Integration is again providing a door prize for the BBQ. This year we giving away an ultra cool "LabVIEW Physical Computing Kit" that includes a Digilent chipKIT WF32 development board and the LabVIEW Home Bundle. The board features built-in WiFi and an SD card slot as well the following: Microchip® PIC32MX695F512L microcontroller (80 Mhz 32-bit MIPS, 512K Flash, 128K SRAM) Microchip MRF24WG0MA WiFi module Micro SD card connector USB 2.0 OTG controller with A and micro-AB connectors 43 available I/O pins Four user LEDs PC connection uses a USB A > mini B cable (not included) 12 analog inputs 3.3V operating voltage 80Mhz operating frequency 7V to 15V input voltage (recommended) 30V input voltage (maximum) 0V to 3.3V analog input voltage range High efficiency, switching 3.3V power supply providing low power operation LabVIEW Home Bundle is targeted at "Makers" (https://www.labviewmakerhub.com). This software is licensed for personal, non-commercial, non-industrial, non-academic purposes. Applications may be distributed only for non-commercial, non-industrial, non-academic purposes.

It might be possible but it is far from just a recompilation of the code. The code was written at a time where nobody was thinking about 64 bit CPUs and no standards existed how one should prepare for that eventualiity. Also it is possible that the script interface in LabVIEW has been cleansed of support for older API standards for the 64 bit version. LabPython uses the first version of that API, but if the 64 bit version of LabVIEW doesn't support that anymore, then the new version documentation would need to be gotten from NI. This is not an official public API.