orko

QUOTE(yen @ Jul 27 2007, 06:30 AM) MIME types (media types) are also relevant in all HTTP response headers and are given in the "content-type" header on all HTTP 1.0 and 1.1 requests for files. That's one of the reasons I asked if the default browser was handling the requests for files (vs. NI using native TCP and parsing out the headers themselves). If they are just passing the request to IE or Netscape, then they might not have access to all of these server response headers in the Datasocket VIs themselves. One other caveat is that each protocol that is supported (ftp,http,psp,dstp,opc,etc) would require special handling to support grabbing the content-type, if that information is available at all. The DataSocket Read VI is still my choice in retrieving files from the internet, but when I need to know more information out of the HTTP headers (like content-type) I think the easiest method is to use TCP to get them (via a HEAD request). http://forums.lavag.org/index.php?act=attach&type=post&id=6480''>http://forums.lavag.org/index.php?act=attach&type=post&id=6480'>http://forums.lavag.org/index.php?act=attach&type=post&id=6480

Hmm... that's the way I understood the type input. The "[text]" or " " endings on the URL's are still are a mystery to me, since they don't seem to behave any differently from one another.This test returned true (they were equal) no matter what type of file (jpg,pdf,html,txt) I was trying to download from the internet: http://forums.lavag.org/index.php?act=attach&type=post&id=6466 Since I can't seem to find any documentation on the differences between these two, I'll just assume they react exactly the same. I was just wondering if there were other capabilities (other "[tags]") inside the Datasocket Read primative that behaved differently. Thanks for your time, and sorry for hijacking this thread a bit

QUOTE(yen @ Jul 26 2007, 12:23 PM) ...as opposed to what? Are there other "[tag]" operations that can be done with the Datasocket primatives to obtain data in another form? I'm confused because the "type" input of the primative is what I thought defined the data type.

QUOTE(LV Punk @ Jul 26 2007, 10:25 AM) Okay, thanks. I understand mime types, and how they are used in HTTP headers, but I'm a little confused on how they are used in the datasocket implementation. Am I wrong in assuming that the Datasocket Read VI only supports a limited subset of these mime types? Which ones does it support, if this is true? I know [text] and work, but are there others?One thing I noticed is that even though "html" is accepted, it isn't a real mime type since it's actually "text/html". In fact "text" isn't a valid mime type either, its "text/plain". I'm assuming that the Datasocket VI's are coded to only allow certain "keywords" of supported types rather than mime types as valid in the URL. I'm not even sure it really handles "[text]" and "[html]" differently...does it?

QUOTE(MikaelH @ Jul 25 2007, 06:17 PM) I really like this one :thumbup: The cool thing is that you can download binary files such as pictures, movies, pdfs, etc. using this method. *Note! This works great if you're saving a text file (txt,html,xml,etc) but if you're saving a binary file (jpg,pdf,etc) you'll have to write the string to the "write to binary file" primative versus the "write to text file" primative or you'll get data corruption. Just because you are able to download it through the datasocket using the [text] format doesn't mean it's a text file... Question: does anyone know of a complete list of URL format speficiers ( [text], , etc) somewhere I can stare at? I also am curious what is handling these specifiers... is it your default browser, or some core TCP/IP functions of the OS?

QUOTE(MK07 @ Jul 26 2007, 01:50 AM) You'll find a lot of information on this subject (as well as most others) in the help inside of LabVIEW. Click on "Help->Search the LabVIEW Help" and type "installers" in the index search. Also, there are tutorials and examples on the ni.com website if you search for "Application Builder tutorial". Particularly this one. QUOTE(MK07 @ Jul 26 2007, 01:50 AM) and how to i connect GBIB device with labview?? if any example please provide me.. Again, look in the help. There are also examples if you click on "Help->Find Examples" and Browse by task under "Hardware Input and Output". You'll find that after familiarizing yourself with the basics and the vast knowledge that is inside LabVIEW's built-in help, you'll be well on your way to understanding the LabVIEW environment. Hope this helps!

Welcome, MK. You'll soon find that the LAVA forums are a great source of information. I can't count how many times I've benefited from an answer to a question I didn't even know I had.

QUOTE(spaceboy @ Jul 25 2007, 11:42 AM) I think what tcplomp was refering to was why you didn't use the "double-click" event on the obstacles control instead of the boolean "Delete". By using the double-click event, one of the nifty values you get inside the event is "row". Also, there is no need to use a local variable to reset your Add Row button if you use a latch mechanical action and place your control inside the event that it triggers (this is good practice on any control event). Avoid the use of locals if you can help it. See your modified VI below: http://forums.lavag.org/index.php?act=attach&type=post&id=6454''>http://forums.lavag.org/index.php?act=attach&type=post&id=6454'>http://forums.lavag.org/index.php?act=attach&type=post&id=6454 Notice also that I wired the shift register through in your "timeout" event. Without this, if you established a timeout then you would lose your info on that event. Hope this helps, PS. You may want to add "8.2.1" to your personal profile. Right now there is only LV6 listed as being used.

QUOTE(John Rouse @ Jul 25 2007, 10:24 AM) Could you elaborate on this a little? I just looked at this vertical mouse and was very impressed with its design. What was uncomfortable about it? QUOTE(John Rouse @ Jul 25 2007, 10:24 AM) The Zero tension is extremely comfortable and I can use for long periods with no pain. Only problem is the accuracy really stinks so for LabVIEw it is not working for me but everything else works fine. This design is one that I've never seen before (kind of looks like a joystick instead of a mouse). Was the accuracy problem inherent in the mouse itself or is this something that you would think would become better after using/getting used it? I'm seriously looking at trackballs and vertical/semi-vertical mice, because I've been noticing the tell-tale signs of carpel tunnel in the last couple of years. However, I don't want to explore the touchscreen/pen option at this time, since funds for this kind of thing are pretty tight at the moment. What I'm looking for is a less-than $100 option that I can sell to the boss. So far the evoluent has been the closest fit for me and the budget...so I'm very interested in more reviews of this style of vertical mouse.

QUOTE(ntward @ Jul 25 2007, 07:42 AM) I heartily recommend the Basics I&II and Intermediate I&II courses described http://sine.ni.com/nips/cds/view/p/lang/en/nid/10548' target="_blank">here. They are well worth the cost if you seriously want to learn the fundamentals and recommended programming styles of LabVIEW.

QUOTE(crelf @ Jul 24 2007, 08:07 PM) Awesome! I wouldn't have pictured Steve Carell as Maxwell Smart, but now that I think about it he might be perfect. Although I hope he doesn't get confused with his other character he's voicing over in http://imdb.com/title/tt0451079/' target="_blank">this film (also coming in 2008 with Jim Carrey!).

QUOTE(Tomi Maila @ Jul 23 2007, 11:07 AM) I'm very interested in seeing this one! It looks like this might have to wait until I get home though, since my employer has been blocking all youtube videos through the firewall (yeah, it sucks since many people are going in that direction now). Thanks in advance, Tomi!

QUOTE(jzoller @ Jul 19 2007, 03:57 PM) Yes. I've seen it done two ways: 1) You can use the "Class Name" property on the control reference and wire it up to cases that handle each type of control you're passing into the subVI. http://forums.lavag.org/index.php?act=attach&type=post&id=6424 2) Wire a "to specific class" to the reference and provide a constant of the type you want to test it for. If you get an error, then it isn't that type of control. http://forums.lavag.org/index.php?act=attach&type=post&id=6425

Hey, they did this with the phones, why not do it on a laptop?

QUOTE(tcplomp @ Jul 19 2007, 11:18 PM) This is really cool!!! :thumbup:

Have you tried to use the instrument driver found on the NI developer network? Its initialization works fine for my 34970A. Download it here. I think this will clear up your problem, since you said the instrument is working in MAX it is probably just the way you're initializing things.

QUOTE(xtaldaz @ Jul 18 2007, 09:04 AM) Should I not tell you about the new hire last month that graduated class of 2005? Okay, then I won't mention that she was born in 1988 either... the year my wife graduated... Okay, I'll stop with the old jokes (immediately following the jibe I'll be giving my wife when I get home of course!).

QUOTE(DougWilson @ Jul 17 2007, 06:47 PM) Welcome, Doug. I find this site invaluable for not only its resources, but for the teaching experience that only helping others can bring. 1990...well, they didn't have LabVIEW set up in my senior year of high school

QUOTE(anor @ Jul 18 2007, 02:33 AM) Your English is very good, actually Asking for the file name before calling the Express VI should satisfy your need. Seeing now that this program interacts with not only a doctor but also a patient, I can see why you need the pause before saving. Hmm... you may even want to consider waiting on a "Go" button press after obtaining the file location to give the doctor some time to get his patient ready ( 1. "Save"->choose file; 2. "Go"->start test )? This may involve another click, but perhaps would establish more confidence that the program will start the testing sequence when they tell it to start, rather than after closing a file select dialog box. Just an option to consider. Good luck!

Nothing can be worse than Perl's object oriented persistence acronym... I like goop as well, but isn't there already a trademark on it? Of course, as mentioned it could be considered LabVIEW GOOP. What about GLoop? As in the sound it makes when you throw your monitor into the bay... :laugh:

QUOTE(CRoebuck @ Jul 17 2007, 03:41 AM) This is just a wild stab in the dark... The one driver that stands out for me in your above error dump is the tc0832.dll, which is a datalogging interface used by Pico hardware (serial thermocouple, by chance?). The latest version of this driver (which is dated Jan 03 2006), according to its documentation was "tested using LabVIEW for Windows 95 version 4.0". I don't know if you are using the latest driver, since it appears this project is a few years old and I'm not sure if you've updated it. Even if you have the latest, it looks like LabVIEW support for it isn't very high on the priority list for Pico. Is there a way to isolate this driver call out of your program and see if your error still occurs? Like I said, this is just a guess at this point with the info you've given us. BTW, did you notice that the "LINK_DATE" on the tc0832.dll line is way off in the future? LINK_DATE="03/14/2035 01:15:49" UPTO_LINK_DATE="03/14/2035 01:15:49"

QUOTE(anor @ Jul 17 2007, 02:16 AM) It appears that the Write to Measurements express VI is set up to start saving the data as soon as it is called. This is done by using the "reentrant" property in the VI exexution properties. If you do not desire this behavior (although I can't think of a reason... can you enlighten us as to why you need it to halt your data collection until the file dialog is closed?) you are going to have to call a file dialog before calling this express VI, feeding the resulting file path to it(you can use the "open/create/replace file" VI in the File I/O pallete). This way, you can use the data flow of the error clusters to make the Write to Measurements express VI wait for the file dialog to close.

QUOTE(67nate @ Jul 16 2007, 12:28 PM) Sorry I didn't get back to you sooner. For some reason your post didn't show up as new last time I checked the boards... I see what you're trying to accomplish now. When you're dealing with hex characters you are dealing with 4-bit words, which can be tricky if you don't split them up correctly, since the lowest numerical type we have is 8-bit. Even though it looks like you have a solution, here's the way I would attack this: http://forums.lavag.org/index.php?act=attach&type=post&id=6370 http://forums.lavag.org/index.php?act=attach&type=post&id=6369 (LV 7.1.1) Basically, I'm taking the byte out of the XOR loop and splitting it up into its 4-bit hex components, then converting their hex values to strings. Hope this was a help to you, Joe

Your problem lies in the fact that by changing any single element's property in an array you are affecting all elements, so the KeyFocus property for an array element reference doesn't really work as expected (It basically just returns focus to the last element that had focus before tabbing away from the array). However, looking at this NI article it appears that you can use keyboard shortcuts to navigate your way through the array elements. Since Michael has so graciously provided a way to simulate keypresses, one way to work around this would be to catch when a user is on the last element of the cluster in each row and send the appropriate keypresses to navigate to the next row. I whipped up a subVI that tabs down in an array, and modified your VI to use it when the user presses tab while on the last enum in the cluster. I know, it's a hack But I really can't think of another way of doing this. http://forums.lavag.org/index.php?act=attach&type=post&id=6351 (LV 8.2.1)

Just a reminder, there should probably be an "unregister for events" on the end of your event structure loop. If not, the dynamic event handling will still be in memory until the VI closes (even after the event structure loop is done).