KarstenDallmeyer

Hi Folks, there is an open source project called ODF Toolkit. A module of this toolkit is the AODL library, a .net module for the ODF Toolkit. AODL (An Open Document Library) I just tryed to call the AODL via LabVIEW .net access. I only tested a short example, but it worked. So why not, building an OpenOffice access via that library? I attached my quick and dirty coded vi. BB ... Karsten Download File:post-8807-1240328196.zip

I just discovered a really confusing LabVIEW behavior. I was able to edit a running VI!!?!? I started a main VI that calls via VI server several sub VIs. In idle mode of the main VI I opened one of the sub routines to edited it. When I switched back to my main vi it has entered the edit mode. But it was still running. I could turn on the highlight function and my frontpanel was still updated. But I was able to modify all objects and I was able to create new wires. As I saved my project, LabVIEW unfortunately stopped this behavior. So I was not able to make some screenshots. If it happens again I'll create some. Looking forward to new features … Karsten

You can use a broadcast UDP Message to search network devices when you don't know their IPs. When you send an UDP message to IP 255.255.255.255 via a defined port all devices in your subnet receive that message. If the clients listen on the sepecified UDP port they receive your call and can react on it. Now you can start a communication whith the devices via IP. An UDP call on 255.255.255.255 is similar to a "Is anybody their?" message. For example. The UDP Write VI in LabVIEW 8.5 expects the IP as an U32 not as a sting. For this conversion you use the String To IP function in LabVIEW. And this function works different on Windows and RT.

I just discovered an intresting bug. When I use the "String To IP" function in LabVIEW 8.5.1 on a Windows PC the functions works fine for all tested IPs. On a LabVIEW RT desctop target the function works almost fine unless you try the IP 255.255.255.255 for UDP broadcast messages. Windows: 255.255.255.255 >> String To IP >> 0xFFFFFFFF this result is correct! LabVIEW RT 8.5: 255.255.255.255 >> String To IP >> 0x00000000 THAT IS ABSOLUTELY WRONG!!! LabVIEW RT 8.5.1: 255.255.255.255 >> String To IP >> 0x00000000 THAT IS ABSOLUTELY WRONG!!! So you have to work with a workaround when you whant to send an UDP broadcast message via LabVIEW RT 8.5.x Greetz ... Karsten

Hi Folks ... when I used msconfig, I found several NI processes. Most of them are easy to identify. But there is one service called "National Instruments Time synchronization". Is there anybody who can tell me whats the duty of this service? Waiting for ideas ... with best regards Karsten