Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by mbrowne

  1. You can use the timeout event to run code every 10 minutes If no other events occur the timeout case will run every 10 minutes..
  2. The Word indicator whish I set to display numeric data in binary format, shows the binary data with MSB on the left down to the LSB to the right (as you would expected) ! Therefore it shows 1100001101001101 which is equivalent to C34D hex! When you probe an array, index 0 is on the left with the index increasing to the right. Therefore when you probe a boolean array the LSB will be shown on the left and the MSB on the right. This is why the probe of the boolean array is the reverse of what is shown in the Word indicator!! But they both represent the value C34D Hex.
  3. That is the Replace Array Subset (not Reshape array), and from the help description it "Replaces (not appends) an element or subarray in an array at the point you specify in index." It our case it replaces a 5 bit subarray in an 16-bit array starting at index 11. It will replaces: Y[11] with N[0] Y[12] with N[1] Y[13] with N[2] Y[14] with N[3] Y[15] with N[4] So the resultant output array is {N[4],N[3],N[2],N[1],N[0],Y[10],Y[9],Y[8],Y[7],Y[6],Y[5],Y[4],Y[3],Y[2],Y[1],Y[0],} Probe the wire to see what data is on the inputs and output to see this working Again you are heading in the wrong direction using Type Cast conversion, use the Number to Boolean Array instead!! The Number to Boolean Array "Converts an integer number to a Boolean array" which is exactly what we need here, not a type conversion!! But the Type Cast help clearly states the difference between the 4.x data and normal typecast converstion is how boolean data is handled.
  4. Here is how you can convert a voltage to the correct format and send it using visa write. No type casts needed. For what you are trying to do use the Number to Boolean Array
  5. Here is a version that will work in LabVIEW 8.2+ Convert.vi
  6. The following should do the job .. The Boolen Array to Number nodes need to be setup correctly ... In the Properties (right click menu) set the Output Configuration to I16 And make sure the Sign Extension Mode is set to If Output is Signed (or Always will work here)
  7. Use the "Date/Time to Seconds" to convert 1/1/1970 to a LV time stamp (seconds from 1/1/1904) Then add the seconds returned from your hardware to this value to give you the LV time stamp for the harware. The native LV time stamp for the harware can now be used as an input to the "Format Date/Time String" function etc.
  8. It is just the Index Array in the Array Sub-Palette [from the LabVIEW Help] When you wire an array to this function, the function resizes automatically to display index inputs for each dimension in the array you wire to n-dimension array. You also can add additional element or subarray terminals by resizing the function. The connector pane displays the default data types for this polymorphic function. [/from the LabVIEW Help] In this case when you wire up the 2D string array to the array input it resizes to provide a row and col index. Just wire up the col index (leaving the row index unwired) to get the complete column.
  9. QUOTE (crelf @ Nov 8 2008, 06:30 AM) Yes ... I would be delighted to see some of my code in there
  10. Big Thank you to Mark for organizing this challenge :thumbup: . And thanks to everyone who voted for me. QUOTE (mballa @ Nov 7 2008, 04:11 AM)
  11. QUOTE (Ton @ Oct 18 2008, 08:17 PM) Setting the 'keyfocus'=True for any other control will take focus away from the string and cause the value change event to trigger if you were editing the string and had changed it's value.
  12. QUOTE (Ton @ Oct 16 2008, 07:53 PM) An other workaround is to manually set the focus of the string to false before you read the terminal... (and set the string focus back afterwards if you want) see picture... This will cause the correct updated value to be read and the value change event to be fired AFTER the menu event.
  13. QUOTE (torekp @ Sep 16 2008, 12:40 PM) Before both loops are started the state indicator is not initialised and will most likely be set to "stop" from the previous run of the VI. Now if the bottom loop starts execution before the top loop it will check the state indicator which is set to "stop" and the loop will immediatly exit. However if the top loop starts before the bottom loop the state indicator will be changed (to "wait4Init" initially) before the bottom loop checks its value.
  14. The following should work without the need for a batch file...... QUOTE (OrangeAndGreen @ Jul 21 2008, 05:22 PM)
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.