Re: Taskbar icon?
Thanks! That is exactly what i am looking for. Hmmm, the SysTray II.cin demo only works for LV5.1 as far as i can see (i am using 6.02) :-/
Re: Error in the call of a DLL function
Obatistor [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi all, I have a problem with the call of a function from Labview through the Call Library Function Node. I configure the Node with the correct convention (the same as the developer), the correct parameters (despite the fact that there are some differences like the change from int32 to long) and browse correctly the name of the DLL. But when I try to run the VI, I obtain the next message: Labview: An exception occurred within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW. VI func_x.vi was stopped at Call Library Function Node 0x240 of subVI func_x.vi I've tried to change the parameters in order to know if that was the problem, but I've obtained the same result. Can anyone help me? Passing data between LabVIEW code and dynamic link libraries is always a hard thing... In order to help you, please send the whole signature (dll call like you would normally do it with C++) and a screenshot of labviews dll call configuration dialog! THX, Sebastian Dau
Re: State machine diagram editor
Howard, John [EMAIL PROTECTED] write: It lets you create state machine based LabVIEW programs by 'simply' drawing a state diagram. You can switch between diagram view and code view. It probably mostly useful for documentation, where state diagrams are needed. It is not part of any version of LabVIEW, you have to pay for it separately. The price is $995. (the standard price for any LabVIEW tool from NI) I am selfishly hoping that no one buys it so that they may change their mind and include it LabVIEW Professional or something like that. (For $995 I'll keep using Visio to draw the few state diagrams I need) Well we usually use SmartDraw www.smarttdraw.com instead. It's about 1/10 of the price of Visio and does IMO just a good job at creating state transition diagrams or whatever your favorite state machine documentation is. I have looked at the State Machine Toolkit and believe that it is fine for the standard state machines a lot of users usually encounter but my state machines usually always tend to be just a tiny little bit more involved so that I would have to hand edit the generated state machine afterwards anyhow and once modified manually you can't seem to go back to continue with the State Diagram Editor. If it would be part of the Professional Developer version of LabVIEW I might give it another try ;-) Rolf Kalbermatter CIT Engineering Nederland BVtel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijkhttp://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
RE: State machine diagram editor
One tip that I would offer is to consider using a Strict TypeDef Enum to drive your state machine rather than a string. Part of the reason for this is to prevent accidental coding errors such as mis-typing a string or forgetting to implement a case. Also, if you further develop your state machine into a component (based on LabVIEW Component Oriented Design (LCOD) - see the book A Software Engineering Approach to LabVIEW for details) which uses a LV2 style global approach to locally contain component information, the Enum turns into a very simple way of accessing the components functions. (perhaps I should have broken up that 'sentence' a little) One minor drawback is having to save the Strict TypeDef Enum in a separate .ctl file. However, I have also taken advantage of this when implementing multiple components which share the same states/functions. Anyway - just my thoughts. John Howard Scott Serlin 01/16/04 12:17PM Thanks for the info. I was hoping for a faster way to add and modify states to the state machine. Also, does anyone have any state machine tips that they can share? I typically use a string driven state machine. I then call out each state from other states. I also use a nextstate local variable so that I can reuse particular states in the machine over and over again and not have to replicate the state throughout the machine. Let me and the email list know your tips. Thanks. Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, January 16, 2004 7:48 AM To: [EMAIL PROTECTED] Cc: Info LabVIEW (E-mail); 'John' Subject: Re: State machine diagram editor Rolf K. wrote: I have looked at the State Machine Toolkit and believe that it is fine for the standard state machines a lot of users usually encounter but my state machines usually always tend to be just a tiny little bit more involved so that I would have to hand edit the generated state machine afterwards anyhow and once modified manually you can't seem to go back to continue with the State Diagram Editor. The inability to go back to the editor after you manually edit is true of most computer-aided wizards. The fundamental problem is that the wizard knows how to maintain a state machine under certain conditions and how to modify various pieces when you change something in the editor. Once you introduce a non-standard component, the wizard has no idea how to handle that component as the system changes. The once-you-manually-edit-you-can't-go-back-to-automatic problem covers the State Machine, Express VIs, and a lot of tools built by just about every piece of helpful software ever written on this planet. It requires either a sophisticated AI to recognize all the components that can be introduced into a system by a user or a very restricted set of things the user can introduce. Notice how HTML editors handle non-standard tags. Pojundery, Stephen R. Mercer -= LabVIEW RD =- I do not believe that Hell is a physical place. I believe that Hell is an hour of the morning. -- Jan 16, 2004
Re: DT2828 Labview driver
You should be able to download data acquisition Omni CD from data translation web site and test the board http://www.datatranslation.com/support/data-acq.htm HMPang pirotte pascal [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Thank you for the answer, Dennis. I bought this acquisition card $35 two weeks ago (at a second hand computer shop). Either they didn't known what kind of card they sold me (it was the only one in their stock), or the card is dead... I don't wanna spend $200 in order to test an acquisition card which might be unusable. I would like to get enough information (internal card registers addr. and registers functions) in order to make my own driver. If I find an already made driver (even a very simple driver), of course I'll be happy... Pascal Dennis Knutson wrote: Data Translation sells DT-LV Link. You can get pricing and ordering info A href=http://www.datx.com/datx/products_pricing/prod_DT-LV_Link.jsp;here/A. You can also get specs from the DT web page.
Re: for loop break
I don't recall that there is a way to break a for loop, but you can certainly replace it with a while loop so that you control the conditions which stop the loop. Sergey Yakovlev [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Could someone suggest me how to break running For Loop cycle?
sonfiguration port //
Hi all, How can I configure the // port for data acquisition labview version : 7 can any one help me?
for loop break
Could someone suggest me how to break running For Loop cycle?
OPCserver-Datasocket connection
I've this problem with OPCServer-DataSocket connections. I must read some variables from an OPCServer and I can subscribe these variables in my vi, but after twenty/thirty minutes the value that is read from OPC-variable doesn't change and it remains fixed to the last correct values read. No error-signals appear and the vi seems run without problems. I've tried with front panel datasocket connection and with datasocket read function, but it's the same thing. Could someone help me? Thanks. Jo
Need help.
I need program that build one dimension array , were we can find integer numbers : 1,2,336 , but they can't repeat and they are in disorder ( randomize position ) . I am using lab view 6.1 I need it now , so please , help mi . [EMAIL PROTECTED]
acquiring min and max values from continuous data values
Hi, I am relatively new to LabVIEW but am not sure how to acquire minimum and maximum values from a constantly changing data value. The value changes continuously and I need to be able to log the minimum and maximum values that have been displayed during a period of time. As I understand, the single data value needs to be inputted into a waveform, which can then be analysed as a graph. However I'm not sure how to do this! If anyone has a relevant VI, I would be extremely grateful. With many thanks
Re: acquiring min and max values from continuous data values
a simple way to do this is to constant compare the present value with the low value and the high value. if the current value is lower than the the min value, then the min value is changed to the current value. Same for the max value. Just initialize the min value with +infinity and the max value with -infinity.
Re: Is there a Color-coding Convention for ICONs in LabView?
There is no Color-coding convention per-say.. However, you'll notice that Agilent (HP), RS, NI (and others) use typically the same color schemes. I followed their trend and select a color scheme by functionality. Use one color for RF, another for digital IO, etc. That way, they are easier to group and create libraries. But as far as an established rule on colors, I am not aware of anything formal. Let the artist in you come out in your icons... ;o) -JLV-
Re: How can I write and read byte by byte at one choosen sector on my HDD
Thanks a lot for response. I'll try both ways but may the best will be by using API-functions. Once again Thanks Wolfgang
Re: acquiring min and max values from continuous data values
should read constantly compare
Re: Generating BCH Codes for Forward Error Correction
Oh I see, that makes more sense now. I am not sure but you may be able to find an open source compiler that you can use on the Web.
Re: Digital output on a pci-6601
Thanks, this suggestion works fine.
Re: State machine diagram editor
It lets you create state machine based LabVIEW programs by 'simply' drawing a state diagram. You can switch between diagram view and code view. It probably mostly useful for documentation, where state diagrams are needed. It is not part of any version of LabVIEW, you have to pay for it separately. The price is $995. (the standard price for any LabVIEW tool from NI) I am selfishly hoping that no one buys it so that they may change their mind and include it LabVIEW Professional or something like that. (For $995 I'll keep using Visio to draw the few state diagrams I need) John H. Scott Serlin 01/15/04 05:53PM Can anyone tell me what the state machine diagram editor toolkit does and which version of labview it is part of? Thanks in advance. Scott
Re: State machine diagram editor
Rolf K. wrote: I have looked at the State Machine Toolkit and believe that it is fine for the standard state machines a lot of users usually encounter but my state machines usually always tend to be just a tiny little bit more involved so that I would have to hand edit the generated state machine afterwards anyhow and once modified manually you can't seem to go back to continue with the State Diagram Editor. The inability to go back to the editor after you manually edit is true of most computer-aided wizards. The fundamental problem is that the wizard knows how to maintain a state machine under certain conditions and how to modify various pieces when you change something in the editor. Once you introduce a non-standard component, the wizard has no idea how to handle that component as the system changes. The once-you-manually-edit-you-can't-go-back-to-automatic problem covers the State Machine, Express VIs, and a lot of tools built by just about every piece of helpful software ever written on this planet. It requires either a sophisticated AI to recognize all the components that can be introduced into a system by a user or a very restricted set of things the user can introduce. Notice how HTML editors handle non-standard tags. Pojundery, Stephen R. Mercer -= LabVIEW RD =- I do not believe that Hell is a physical place. I believe that Hell is an hour of the morning. -- Jan 16, 2004
State machine diagram editor
Can anyone tell me what the state machine diagram editor toolkit does and which version of labview it is part of? Thanks in advance. Scott
Re: Autostarting LabVIEW VI in Linux
At 13:18 -0800 01/15/2004, Jason Dunham wrote: I'm using Linux (RH8) and trying to get a LabVIEW VI to run when the system boots up. I added a line to /etc/rc.local, but it doesn't seem to have an effect The line was /usr/local/lv70/labview /home/jason/myvi.vi The computer already boots into a normal X-window session Any ideas or tips? Is there a list of command-line switches for LabVIEW/Linux? I am not up on Linux but under OS X (free bsd un*x) the command would be open /usr/local/lv70/labview /home/jason/myvi.vi the open command tells the OS to open the application associated with the VI. You need to launch the application and then tell it to open the document. But I just checked and it can also be done by executing LabVIEW with a VI file as the argument. (again at least on OS X) but I think it works as well on Windows/linux. So for my installation it would be: /Applications/National\ Instruments/LabVIEW\ 7.0/LabVIEW.app/Contents/MacOS/LabVIEW ~/Desktop/PCdynamicevents.vi (all on one line with a space in front of the vi file name). Be sure that the VI is set to auto-run at launch. -Scott
RE: State machine diagram editor
Yes. When you customize a control, the ring in the control editor may be set to three values: 1) Control 2) Typedef 3) Strict typedef In these last two, it is the word typedef or type definition that is important. It defines a datatype, which exists even if the control itself is never loaded onto a visible front panel. Pojundery, Stephen R. Mercer -= LabVIEW RD =- I do not believe that Hell is a physical place. I believe that Hell is an hour of the morning. -- Jan 16, 2004 |-+ | | Scott Hannahs| | | [EMAIL PROTECTED]| | | du | | | Sent by: | | | [EMAIL PROTECTED]| | | a.army.mil | | || | || | | 01/16/2004 03:15 | | | PM | | || |-+ --| | | | To: Scott Serlin [EMAIL PROTECTED], LabVIEW -Info [EMAIL PROTECTED] | | cc: | | Subject: RE: State machine diagram editor | --| At 14:25 -0600 01/16/2004, Scott Serlin wrote: I do not have any controls to access in my vi state machine. As an example, I control a piece of equipment that labview turns on, gets some measurements, logs those measurements to a database, and then shuts down. I do not access any front panel controls to run my via. All of that is done through a test executive. My state machine is set up by placing a string in each case statement that refers to the next state. The initial string is set outside of the while loop that makes up the state machine. Can I still utilize the strict type def enum solution in a similar manner or better? I think so. If it is an enum then the case statement will automatically allow intermediate states to be created with the correct case when the enum is modified. As an enum you can use the increment primitive to go to the next state in a sequence. As an enum defining the next state to go to is not susceptible to typos. -Scott
RE: State machine diagram editor
At 14:25 -0600 01/16/2004, Scott Serlin wrote: I do not have any controls to access in my vi state machine. As an example, I control a piece of equipment that labview turns on, gets some measurements, logs those measurements to a database, and then shuts down. I do not access any front panel controls to run my via. All of that is done through a test executive. My state machine is set up by placing a string in each case statement that refers to the next state. The initial string is set outside of the while loop that makes up the state machine. Can I still utilize the strict type def enum solution in a similar manner or better? I think so. If it is an enum then the case statement will automatically allow intermediate states to be created with the correct case when the enum is modified. As an enum you can use the increment primitive to go to the next state in a sequence. As an enum defining the next state to go to is not susceptible to typos. -Scott
Re: Autostarting LabVIEW VI in Linux
Jason, I'm not sure if this is your problem, but make sure that X is ALREADY running, or else there will be no display for LabVIEW to use. You ensure this by putting the VI launching command in your X startup script (where the window manager is launched). Take a look at Chs 22-24 of LabVIEW Graphical Programming 3rd Ed for a step- by-step. Good luck, -Jim Jason Dunham [EMAIL PROTECTED] said: I'm using Linux (RH8) and trying to get a LabVIEW VI to run when the system boots up. I added a line to /etc/rc.local, but it doesn't seem to have an effect The line was /usr/local/lv70/labview /home/jason/myvi.vi The computer already boots into a normal X-window session Any ideas or tips? Is there a list of command-line switches for LabVIEW/Linux? Thanks, Jason Dunham SF Industrial Software, Inc. --
Re: Detect keyboard strokes outside LabVIEW?
Thanks, Dan. I have to build this application in LabVIEW 6.1 which does not have these functions. I didn't think at first I could export LabVIEW 7 vi.lib functions to LabVIEW 6.1, but I found there is a way to do it (save the VIs such as Acquire Input Data.vi as a copy outside vi.lib, then save for previous version 6.1, and copy the lvinput.dll to the LabVEIW 6.1 directory). So it was nice to solve my problem staying wholy with LabVIEW, even if I had to kidnap some VIs from a different version. Thanks, Jeffrey On 1/16/04 6:53 AM, Bookwalter, Dan [EMAIL PROTECTED] wrote: Jeff Not sure if it will work for you but you can use the Acquire input data.vi from the input device control pallete to read KB input no matter which program has the focus Dan Bookwalter N8DCJ Hi-Stat a Stoneridge Co. 345 South Mill St. Lexington, Ohio 44904 (419) 884-1219 Phone (419) 884-4172 Direct (419) 884-4195 Fax [EMAIL PROTECTED] -Original Message- From: Rolf Kalbermatter [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 3:46 AM To: 'Jeffrey Travis' Cc: Info LabVIEW (E-mail) Subject: Re: Detect keyboard strokes outside LabVIEW? Jeffrey Travis [EMAIL PROTECTED] wrote: Does anyone know of a way to detect keyboard strokes even when LabVIEW is not the active application (eg, detect typing in MS Word from LabVIEW)? You will need to install low level system hooks for something like that. The way this is done is you install a callback function through a WinAPI function SetWindowsHookEx() for a pecific type of event and the system then calls this callback function every time before it dispatches an event matching the hook you installed to the currently active window. LabVIEW can not really generate callback functions to be installed like that so you would have to write a small DLL in C which does this for you. The whole story and its implications are however very involved and system callbacks have to be very specific. If they do not return as fast as possible your entire system is going to crawl like a snail so dispatching those events to LabVIEW through a queue or something is quite out of question unless you only want to snoop at the key strokes but not influence them in any way. Also the events you receive are as far as I remember raw key scan codes. Translation into actual characters and keys would then be necessary. If you are interested in further information I would recommend you to read through http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwui/html /msdn_hooks32.asp (line may be wrapped). Rolf Kalbermatter CIT Engineering Nederland BVtel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijkhttp://www.citengineering.com Netherlandsmailto:[EMAIL PROTECTED] _ This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please send an electronic mail message to [EMAIL PROTECTED] -- Jeffrey Travis Studios http://jeffreytravis.com 512.371.3614[EMAIL PROTECTED]
Re: LabVIEW Project Management IDE (was Wish list)
Hi, On Friday 16 January 2004 10:24, Rolf Kalbermatter wrote: [...] An IDE like that would not only have to support things like VI and documentation management, Application Building, or Source Code Control with a system like CVS or better maybe SubVersion, but also provide a facility to integrate automatic Unit Testing to be useful for really professional work. [...] Yeah, well, a complete IDE would be very nice indeed, but the first step would be to make LabVIEW in itself Source Code Control 'compatible'. As long as the compiled code is stored INSIDE a VI file, it makes it a great burden if not outright impossible to do concurrent development on one project by many people using standard SCC tools. We do this (using subversion, it's great!), but it's a PITA to keep all VIs from being modified whenever someone loads a freshly checked out version of the project. Next on my list are namespaces (not just for different projects, but also just some libs you share between projects and/or teams), and VI linkage problems (not storing the path to the linked VI inside the VI, for example). IMHO, NI should try to (optionally) save the compiled code and any 'on the fly' generated info for any VI in a seperate location, as it can be rebuilt automatically, just like now. This would also allow for something like a human-readable VI file format (just dreaming...). Well, I should stop now before I really get started, Joerg -- Leading SW developer - S.E.A GmbH Mail: [EMAIL PROTECTED] WWW: http://www.sea-gmbh.com
Re: DAQ OPC on Windows XP?
Rolf, You were right about security for navigating the hive. I had to give permissions at the HKEY_LOCAL_MACHINE\SYSTEM level before I could navigate further down. However, this did not fix my problems with OPC. I still get the same error message when trying to browse OPC Servers on remote computers. My next step is to try getting this to work on a Windows 2000 computer to see if it makes any difference. Thanks! John Rolf Kalbermatter 01/15/04 03:43AM John Howard [EMAIL PROTECTED] wrote: If I try to view the registry keys on the remote computer using 'regedt32', I can not view anything below HKEY_LOCAL_MACHINE\SYSTEM, even though I have modified security for the following keys to make sure DCOM should work. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers ... I gave Everyone full access to these keys just to be sure security wouldn't be a problem. I have no experience both with OPC DAQ as well as XP but here it goes: Windows security is tricky at its best, maybe every security is like that. However I do believe that the inability to browse the hive in regedit may have to do with the fact that a key has rights to both view as well as enumerate (expand) it. So in order to browse to your key you might need to allow on all keys from HKLM\SYSTEM down to the one you want to get at the enumerate privilege for the user in question. There are actually a whole bunch of different privileges one can request for when opening a key. Maybe XP has changed somehow that it will in its RPC implementaiton just enumerate the keys hierarchy level for hierarchy level until it gets at the one it needs and that would fail when the enumerate privilege is not enabled. Or DAQ OPC or Windows RPC request one of the many privileges to much when trying to open a key, failing on that one although it may not be needed for the operation in question. As Microsoft has become more concerned with security in the past year or two such small but under certain circumstances far reaching modifications to core elements have become more the rule than the exception. Rolf Kalbermatter CIT Engineering Nederland BVtel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
RE: State machine diagram editor
Thanks for the info. I was hoping for a faster way to add and modify states to the state machine. Also, does anyone have any state machine tips that they can share? I typically use a string driven state machine. I then call out each state from other states. I also use a nextstate local variable so that I can reuse particular states in the machine over and over again and not have to replicate the state throughout the machine. Let me and the email list know your tips. Thanks. Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, January 16, 2004 7:48 AM To: [EMAIL PROTECTED] Cc: Info LabVIEW (E-mail); 'John' Subject: Re: State machine diagram editor Rolf K. wrote: I have looked at the State Machine Toolkit and believe that it is fine for the standard state machines a lot of users usually encounter but my state machines usually always tend to be just a tiny little bit more involved so that I would have to hand edit the generated state machine afterwards anyhow and once modified manually you can't seem to go back to continue with the State Diagram Editor. The inability to go back to the editor after you manually edit is true of most computer-aided wizards. The fundamental problem is that the wizard knows how to maintain a state machine under certain conditions and how to modify various pieces when you change something in the editor. Once you introduce a non-standard component, the wizard has no idea how to handle that component as the system changes. The once-you-manually-edit-you-can't-go-back-to-automatic problem covers the State Machine, Express VIs, and a lot of tools built by just about every piece of helpful software ever written on this planet. It requires either a sophisticated AI to recognize all the components that can be introduced into a system by a user or a very restricted set of things the user can introduce. Notice how HTML editors handle non-standard tags. Pojundery, Stephen R. Mercer -= LabVIEW RD =- I do not believe that Hell is a physical place. I believe that Hell is an hour of the morning. -- Jan 16, 2004
LV7 Event Structure - Vkey Enum oddity
I have this problem on ONE LV7 machine and not another. I dont mess with LabVIEW.ini to see how this can be but . I cant get the Event Structure Vkey from the Key Down Event to connect to a Vkey in an cluster Or to even have it connect to an indicator!. (The cluster is prototyped correctly) Do the following: 1. Drop in an Event Structure, Add Key Down as an event. Right-click on the Vkey output node and Create Constant 2. Drag the Vkey constant outside the Structure build it into a cluster. 3. Pass the cluster into the Key Down Event unbundled by name and try to wire the Event Vkey value into the cluster. 4. I get a broken wire and an Error Enumeration Type Error the Enum type must be exactly the same. 5. Disconnect the cluster from Vkey Right-click on the Event Structure Vkey node and Create Indicator when I wire the indicator I STILL get a broken wire! This code works in LabVIEW 6.1 just fine. Jack Hamilton Hamilton Design [EMAIL PROTECTED] www.Labuseful.com 714-839-6375 Office
RE: State machine diagram editor
Hi John, I do not have any controls to access in my vi state machine. As an example, I control a piece of equipment that labview turns on, gets some measurements, logs those measurements to a database, and then shuts down. I do not access any front panel controls to run my via. All of that is done through a test executive. My state machine is set up by placing a string in each case statement that refers to the next state. The initial string is set outside of the while loop that makes up the state machine. Can I still utilize the strict type def enum solution in a similar manner or better? Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Howard, John Sent: Friday, January 16, 2004 12:49 PM To: [EMAIL PROTECTED]; Scott Serlin; Thorpe, R. Mark Subject: RE: State machine diagram editor One tip that I would offer is to consider using a Strict TypeDef Enum to drive your state machine rather than a string. Part of the reason for this is to prevent accidental coding errors such as mis-typing a string or forgetting to implement a case. Also, if you further develop your state machine into a component (based on LabVIEW Component Oriented Design (LCOD) - see the book A Software Engineering Approach to LabVIEW for details) which uses a LV2 style global approach to locally contain component information, the Enum turns into a very simple way of accessing the components functions. (perhaps I should have broken up that 'sentence' a little) One minor drawback is having to save the Strict TypeDef Enum in a separate .ctl file. However, I have also taken advantage of this when implementing multiple components which share the same states/functions. Anyway - just my thoughts. John Howard Scott Serlin 01/16/04 12:17PM Thanks for the info. I was hoping for a faster way to add and modify states to the state machine. Also, does anyone have any state machine tips that they can share? I typically use a string driven state machine. I then call out each state from other states. I also use a nextstate local variable so that I can reuse particular states in the machine over and over again and not have to replicate the state throughout the machine. Let me and the email list know your tips. Thanks. Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, January 16, 2004 7:48 AM To: [EMAIL PROTECTED] Cc: Info LabVIEW (E-mail); 'John' Subject: Re: State machine diagram editor Rolf K. wrote: I have looked at the State Machine Toolkit and believe that it is fine for the standard state machines a lot of users usually encounter but my state machines usually always tend to be just a tiny little bit more involved so that I would have to hand edit the generated state machine afterwards anyhow and once modified manually you can't seem to go back to continue with the State Diagram Editor. The inability to go back to the editor after you manually edit is true of most computer-aided wizards. The fundamental problem is that the wizard knows how to maintain a state machine under certain conditions and how to modify various pieces when you change something in the editor. Once you introduce a non-standard component, the wizard has no idea how to handle that component as the system changes. The once-you-manually-edit-you-can't-go-back-to-automatic problem covers the State Machine, Express VIs, and a lot of tools built by just about every piece of helpful software ever written on this planet. It requires either a sophisticated AI to recognize all the components that can be introduced into a system by a user or a very restricted set of things the user can introduce. Notice how HTML editors handle non-standard tags. Pojundery, Stephen R. Mercer -= LabVIEW RD =- I do not believe that Hell is a physical place. I believe that Hell is an hour of the morning. -- Jan 16, 2004
RE: Long filenames (LV61 Win2000)
I have read that the path length restriction is less severe for drag-and-drop operations than for file dialogs. -Charlie Lasnier Subject: RE: Long filenames (LV61 Win2000) From: Rolf Kalbermatter [EMAIL PROTECTED] Date: Thu, 15 Jan 2004 22:31:16 +0100 Hi Michael The problem is not with the length of the filename. The problem is the total character length of the path including the filename. I don't know the details but the limitations are a combination of directory depth, directory name length and filename length. Rolf, i assume it works for you because you are saving to root. I assume it is not working for Martin because he is in a subdirectory that has a long name certain levels down. With file name length I do refer to the total length of the path actually and the limit there is as I have said 259 characters This is a Windows API limitation and can only be overcome with quite some humbo bumbo using Unicode API functions and special path name syntax with an added \\?\ before the actual file name. As it seems to turn out at least some of the LabVIEW functions do have a limit of 128 character for each hierarchy level in a path. This is not entirely logical as the hierarchy level elements are stored as a short Pascal string internally which would be able to handle 255 chars and LabVIEW does that in most places actually. It may be however possible that in the function to convert a LabVIEW path into a platform path sring, there might be a small bug using a signed char at some place during the conversion for the lenght of such an element. It shouldn't be a serious problem in most cases as the path itself is limited to 259 characters on Windows anyhow. Rolf Kalbermatter CIT Engineering Nederland BVtel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijkhttp://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
Wireless field measurement system - ideas?
Hi, everybody This is a little off topic, I apologize! But I couldn't resist the oppurtunity to get some good advice from this excellent forum. We are about to design or procure a wireless field measurement system. Any ideas about the design in general or possible existing hardware would be appreciated. The system should consist of two or more synchronized A/D converter units and one controller unit. Distance between the units can be up to 200 m and it can be a rather bad EMC environment. Requirements: * Max 100 us between samples * Synchronized sampling within 1 us (not necessarily by hardware) * Max voltage 100V AC * Amplitude accuracy 0,02% - 0,05% I see two main ways in which the synchronization can be achieved - please add your own thoughts: 1) A radio signal of some kind either synchronizes the sample clocks of the two A/D converters or trigs the measurement. They must however start simultaneously within 1 us. 2) Another way that does not demand such high level of synchronism of the hardware, would be to have 2 channels per A/D unit and let the second channels sample a known, common, sinusoidal reference signal. That way, the data processing can use the reference channels to phase shift the signals so that they become synchronized. Further, I imagine some GPS device could do the job. By supplying either a sinusoidal reference signal or a trig pulse. Any thoughts and ideas are welcome! Does anyone perhaps know of a suitable hardware? Regards, Andreas Nilsson, SP Swedish National Testing and Research Institute mailto:[EMAIL PROTECTED]
