Jump to content


  • Content Count

  • Joined

  • Last visited


Community Reputation


About dhuff

  • Rank
    Very Active
  1. first of all, what data do you mean, is the ID looking strange? What type of CAN and what baud rate are you using? There are a few examples on the NI.com webpage that might help. Check there for starters. NI CAN help
  2. 1. Open NI Measurement & Automation Explorer (MAX) 2. Create some Fieldpoint items 3. Save Fieldpoint Configuration File (.iak) with a non 8.3 filename, for example "my configuration to save.iak" 4. Close NI-Max 5. From Windows, double click above named .iak file to work with it. 6. Note that the file name is listed as "my~1.iak" indicating MAX CAN NOT HANDLE THE NON 8.3 FILE NAME. If you try to do a save, it also seems to not work right, meaning any changes will not be saved. 7. Press F5(refresh) and note that does not fix the problem. If you open MAX and right click and use the O
  3. I agree with everything stated so far, but would add 2 simple things 1. I use the Process Explorer <Process Explorer>From Sysinternals.com This FREE utility will allow you to see what is running in the background, and optionally disable it. There is also another FREE utility at the sysinternals site called AutoLogons which will allow you to easily browse and diable stuff that starts when Windows boots (it is easier than browsing the registry). 2. Video Acceleration This has been an issue with Labview in the past, if the video acceleration is too high it will cause glitches trying to
  4. I am assuming you mean the .dbc file assocated with CAN traffic. This is the Vector CAN message traffic database file. It defines the CAN message identifiers, repition rates, and data variables. If you go to the Vector website you can learn more. <www.vector-informatik.de>
  5. OK, a few quick things, The CAN interface for the CAN Init Start.vi (the middle VI) shows that the channel might not be setup correctly in your interface. You usually tell the task to send on channels like CAN0 or CAN1. Those channels are defined in NI MAX (Measurement & Automation Explorer) So you need to start NI Max, and define the CAN channels. This tells Labview which physical CAN port is CAN0, and details associated with it. Second Thing: CAN communications require at least 1 listener and 1 CAN sender, otherwise the CAN interface will report a CAN bus error. So you need to s
  6. As far as recompiling everything, Labview only includes the ability to recompile VI's back 1 version. So if You want to convert a VI from version 7.1 to version 6.1, you need to follow the steps below. open the VI in Labview 7.1, and save for previous version 7.0 open the VI in Labview 7.0, and save for previous version 6.1 As for compatibility between versions, labview 6.1 will not open a VI written in 7.1. You have a few options here. 1. Write everything in 1 version of Labview 2. Write ALL you VI's in the earlier version of Labview, and treat them as read only. You can then call
  7. I will also say I have heard good things about beyond compare, but never used it myself. I have used a homebrew method, using MD5 checksums. I use MD5summer (free download at http://md5summer.org) to create a MD5 fingerprint of each file and store it in a data file, then I call routine in Labview to calc the MD5 of a file. If it does not match the one stored in the data file, I have a problem. I like MD5 because it is better defined than a 32bit CRC, and the MD5summer can read and write in a format understood in Windows or Linux. I also second the idea of using some source code contro
  8. OK, before we get into flame wars, my suggestion was to use an easy DOS command, basically it is no extra software to build or buy, so everybody relax, I was trying to get a simple point across. Some important questions: Why do you want to know the contents of the window DURING RUNTIME? Is there something there in the DOS window that will not be there when it finishes? Does this DOS sequence involve many steps or commands? Does it involve keypresses or user input decisions too complex for the computer? Is this on a remote platform or other special platform that does not facillita
  9. does your dos command finish quick? I have used the DOS output redirect command to pass results to somewhere I can find. Then you just read the results back into labview. For example, the command below will "redirect" the output of the dir command into a file called output.txt: C:\dir *.* > C:\output.txt I have used this for a quick and easy way to read the results of DOS commands issued in Labview back into Labview.
  10. and for you firefox fans, http://www.funnyfox.org
  11. have you looked at the System Exec.vi (located on the Communications Pallette)?
  12. First, you must have the Labview Application Builder installed, it is an additional package for the Labview development system, it comes with with the more expensive versions of Labview. (Labview Full Development Version, or Professional Development Version) If it is installed, open Labview, and click Tools >> Build Application or Shared DLL. A window should pop up, allowing you to specify files to include and such. The main thing to remember is to click on the pull down menu for build type, and choose Application (.exe) There should be more info on the NI website, search there for mo
  13. I found a strange bug where saving or updating custom Type Defs will not change their revision numbers, and I was wondering if anybody else has seen it as well. It appears that the revision history does not update when you modify them, and it does NOT prompt the user for description when one is changed. So if one of the people working on a HUGE vi project changes your defined Type Def, ALL vi's will see something has changed in the type def, but you are probably out of luck figuring out what changed in the type def. Here is the sequence to follow to find it 1. Go into the Labview Revision
  14. dhuff


    I have a Garmin GPS18, and I found that the GPS will output data format is changeable, it will output data in Garmin Format, or NMEA, but not both at the same time. Mine came from the factory sending data in the Garmin format instead of the NMEA format that I needed, so I had to change it using the software tool on the Garmin website. (go to <http://www.garmin.com/products/gps18oem/> and click on Downloads, and click on the Unit Software) Second thing, is that your computer will make a "virtual serial port" after you install the drivers for the USB converter. You can use NI Measurem
  15. If you are running Windows, you can invoke the .exe using the SystemExec.vi in the Communication Pallette. This VI will let you execute any DOS command with parameters, just invoke the Perl code using the command input. By the way, you should also look at the following link to see about interfacing to Perl without building the Perl code into an executable. <http://www.jeffreytravis.com/lost/labperl.html> Hope this helps,
  • Create New...

Important Information

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