Hello haythem, I don't have a d900 to test, but the vidi help online indicates native mode communication will work. Here's a link to the vidi software help support.cognex.com/docs/isvidi_140/web/EN/Help_ISViDi/Content/Topics/IndustrialCommunications/comms_native_mode.htm?TocPath=Communications%7CIndustrial%20Communications%7CNative%20Mode%20Communications%7C_____0 If that doesn't work do a google search for cognex vidi native mode help. The get value command looks to have a different format in vidi software. You'll have to read the help. I can email you the VI. Leave your email address in the comments and I'll send it to you. (You can delete your email later) If the code helps you and you sell it send me some $ on paypal. That would be great because I'm newly divorced and every dollar helps me get back on track. Thanks for watching the video.
Hey there. Thanks for putting effort to create a labview - cognex interface and for sharing your example on your blog. Really useful so one doesnt have to spend hours on figuring out the communication itself. A note to your video: your implementation shown at 2:23 really doesn't take advantage of the Function Global Variables (FGVs) at all, you simply created a state machine. Your code always open the communication, logs in, executes one command at a time and then closes the communication. One way to improve performance is this: 1. wire a true constant to your conditional terminal 2. move your "command" input outside of the loop and replace the enum constant "INIT" with it. From this point you dont even need a shift register on the "Command" wire (3. I dont see the point of the event input, but I didnt see all your cases. (if its really needed you can move it to the init case and use an FGV like on the reference to store its value from run-to-run).) If you perform the changes above your need to call this VI once with the INIT command and then you can call as many times with the others (and then dont forget to call it with "close" when you stop your main VI). This is extremely common way to use connection references in labview and it saves the hassle and overhead of constantly open and close a connection. In most cases it works fine, one exception if the server camera tends to close the communication after a while if there is no traffic on the bus but that is rare.
Thanks, you're 100% right. Most of my FGV's are structured as you recommended. This one was going to be used by a LabView programmer who doesn't "get" FGV's and want's everything to be state machines. I know from past projects that if I give him a FGV with init and close processes, he doesn't use them and then says my code doesn't work. What I don't understand is LabView Classes.
@@LowtechLLC I guess you should keep away from a person who calls himself a labview programmer without understanding (or the will to understand) one of the basic concepts of the language :) LabVIEW classes are pretty much the same as classes in other language. I mean there is really nothing unique in LV classes, once you understand the concept of classes in general. I didnt work too much with classes myself, but feel free to ask a question and I'll do my best to respond if it is specific enough.
Take a look at my blog post for information and an example. lowtechllcblog.blogspot.com/2022/01/cognex-in-sight-industrial-vision.html There is a simplified .VI that triggers a camera and can get the value of a cell. drive.google.com/file/d/1G3T7LsJA6gZIcHpWeMIAGt_enxl1vMb5/view?usp=sharing If you use this code in a project that you sell I would like to be credited for the work and compensated. Thanks.
very nice description, Thanks
Hi sir , thank you for this fruitily tutorial , but is it get well with the In-Sight D900 ? and can you share the VI to use it please ,Thank you sir
Hello haythem, I don't have a d900 to test, but the vidi help online indicates native mode communication will work. Here's a link to the vidi software help support.cognex.com/docs/isvidi_140/web/EN/Help_ISViDi/Content/Topics/IndustrialCommunications/comms_native_mode.htm?TocPath=Communications%7CIndustrial%20Communications%7CNative%20Mode%20Communications%7C_____0
If that doesn't work do a google search for cognex vidi native mode help. The get value command looks to have a different format in vidi software. You'll have to read the help. I can email you the VI. Leave your email address in the comments and I'll send it to you. (You can delete your email later) If the code helps you and you sell it send me some $ on paypal. That would be great because I'm newly divorced and every dollar helps me get back on track. Thanks for watching the video.
Hey there. Thanks for putting effort to create a labview - cognex interface and for sharing your example on your blog. Really useful so one doesnt have to spend hours on figuring out the communication itself.
A note to your video: your implementation shown at 2:23 really doesn't take advantage of the Function Global Variables (FGVs) at all, you simply created a state machine. Your code always open the communication, logs in, executes one command at a time and then closes the communication.
One way to improve performance is this:
1. wire a true constant to your conditional terminal
2. move your "command" input outside of the loop and replace the enum constant "INIT" with it. From this point you dont even need a shift register on the "Command" wire
(3. I dont see the point of the event input, but I didnt see all your cases. (if its really needed you can move it to the init case and use an FGV like on the reference to store its value from run-to-run).)
If you perform the changes above your need to call this VI once with the INIT command and then you can call as many times with the others (and then dont forget to call it with "close" when you stop your main VI). This is extremely common way to use connection references in labview and it saves the hassle and overhead of constantly open and close a connection. In most cases it works fine, one exception if the server camera tends to close the communication after a while if there is no traffic on the bus but that is rare.
Thanks, you're 100% right. Most of my FGV's are structured as you recommended. This one was going to be used by a LabView programmer who doesn't "get" FGV's and want's everything to be state machines. I know from past projects that if I give him a FGV with init and close processes, he doesn't use them and then says my code doesn't work.
What I don't understand is LabView Classes.
@@LowtechLLC I guess you should keep away from a person who calls himself a labview programmer without understanding (or the will to understand) one of the basic concepts of the language :) LabVIEW classes are pretty much the same as classes in other language. I mean there is really nothing unique in LV classes, once you understand the concept of classes in general. I didnt work too much with classes myself, but feel free to ask a question and I'll do my best to respond if it is specific enough.
Hi sir, can you share the vi shown in this video to use it please...
Sir can you provide me the project to explore more how this works
Take a look at my blog post for information and an example.
lowtechllcblog.blogspot.com/2022/01/cognex-in-sight-industrial-vision.html
There is a simplified .VI that triggers a camera and can get the value of a cell.
drive.google.com/file/d/1G3T7LsJA6gZIcHpWeMIAGt_enxl1vMb5/view?usp=sharing
If you use this code in a project that you sell I would like to be credited for the work and compensated. Thanks.