Jump to content

i2dx

Members
  • Posts

    683
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by i2dx

  1. I had the same problem almost a year ago. I also tried (hard) to get comfortable with Perforce but finally I decided that Perforce is not suitable for me and removed it from my disks .... that was the nice version: In fact I am convinced that Perforce is just crap. I've never used a piece of software that made me more headaches than this one! This "workspace and change-list stuff" really drove me crazy.

    The sad thing is, that VSS has no trial version, so what I do now is: use some (self written scripts) which retrieve my LabVIEW work directory once a day, and make a backup. Maybe this solution is not that secure but it is comfortable and at least I have "some" security. I decided to write my own SCC for LV, but this project is idle until I have more time - which will probably happen not before 2056 ;)

    Maybe you want to check out CVS/SVN but I - for my part - am to lazy to set up a linux server and get it running - sorry, but I have still to much work :)

  2. QUOTE(Sarfaraz @ Oct 10 2007, 01:32 PM)

    Hi,

    Does anyone know how to program CIF DP60 a PCMCIA profibus card (manufactured by Hilscher, Germany) using LabVIEW. Is it necessary to know which type of PLC this hardware will connect to, to program it? Well i am making an application in LabVIEW which has to communicate with a PLC using CIF DP60 or DP50 hardware on my pc. Thanks in advance... Any help will be highly appreciated.

    you need:

    1. the hardware and the driver for this card installed on your system

    2. the hilscher OPC-Server, which should be on the driver CD installed and running

    3. then you can create your items with the OPC-Server

    4. you can use the datasocket VIs to access the OPC-Items to read and write the items

  3. QUOTE(orko @ Aug 24 2007, 05:16 PM)

    Just an FYI in case anyone tries to reach me via email in the next week. They've really pulled the stupid card now, since I was transitioned over to a new email system last night and taken off of my existing account...and no one bothered to give me the login information. :headbang:

    just strike back and

    WRITE LETTERS!

    ... and of course send them all by official US Postal Service! (even those, which go to your colleagues next door, and your boss!)

    :D

  4. by the way and just to add some fuel to the fire :D

    If NI would ask me (of course it does not, but if it does ;) ) what is more important for the further development of LabVIEW

    a) LVOOP

    b) an Atmel AVR Module for Labview, which allows the user to programm an Atmel µC in a way the FPGA Module does ...

    I'd answer b! ... and again I have famous support :D

    med_gallery_17_57_612668.jpg

  5. QUOTE(Michael_Aivaliotis @ Aug 25 2007, 01:42 AM)

    Question, how do all of you perform testing on your LabVIEW VI's?

    hmm: that depends on the VI. I mostly work "bottom UP" and the testing is done during development. I have (developed) a tool for tracking the "review" status, which uses persistent tags and gives me the ability to view the "review status" of a VI hierarchy. I can mark a VI as "unchecked", "tested and OK", "needs review" ... etc

    1. simple VI: enter the expected inputs, hit the run button and take a look at the outputs. If the result are as expected, I assume my code is correct and I test what happens, if the VI gets unexpected values. Maybe it should drop an error on unexpected inputs or deliver default values, etc ...

    2. modules, e.g. a DAQmx functional global: I create a testing shell, where I can run that module "standalone" and watch the outputs, the timing behaviour, etc. If all looks fine, that VI gets the "approved mark". I also test "more complicated algorithms" within a test shell ...

    3. integrating VIs: I Put all my modules, simple VIs, etc in and make the "big bang" test. Mostly this takes a little bit more time, to debug/test those VIs

    4. Main VI: the Main VI is under constant testing, because I use it as the test shell for the simple VIs, modules, etc. It's probably the most tested VI in my whole application.

  6. QUOTE(orko @ Aug 24 2007, 05:16 PM)

    Screw it, I'm keeping the rant tag open for now. :wacko: Anyone want a slightly mistreated CLD in Washington?

    hmm, ok, I am a little late, but: if you want to work in Germany, just let me know :)

  7. QUOTE(Ben @ Aug 23 2007, 07:39 PM)

    That may be just enough time for me to complete the paradym shift.

    Ben

    :)

    just to add some more explanation:

    I am not against LVOOP in principle. But the only thing that counts in my business is to deliver good quality within time and budget, which means, there is little room for experiments. If I make experiments and my tools are buggy or are in their fledgling stages, that will cost me extra time, nerves and money. I'd simply like to avoid that.

    I can state that I will use LVOOP, if I have an advantage in my business. In the meantime, I'd like to thank developers like Tomi for their patience and there enthusiasm to test and improve new technologies and AQ for improving LV - I hope you have enough stamina ;)

  8. QUOTE(Michael_Aivaliotis @ Aug 23 2007, 07:10 PM)

    Even without classes, work can still go on as usual - until NI forces us to use classes (which they probably will). I'm in favor of classes, I'm using classes in customer projects, but the more gotchas you present, the harder it is to convince people.

    I hope nobody will force me to use classes. Nobody forces a C Programmer to switch to C++! And IMHO it's a bad idea to force a programmer to use a specific feature. If that feature gives him an advantage (faster, better, cleaner code, etc ..) he will use it. That would be the only "force" I'd accept.

    Besides:

    med_gallery_17_57_40060.jpg

    I consider the first LVOOP features as a stepstone to a new programming language (maybe called G++ ?) which needs - accoording to the statement of Dr. T - at least 15 years for widespread addoption :)

  9. my answers are:

    I have tried it, but I do not use it in major appications and I am waiting for by reference objects.

    my reasons:

    first, I am stuck with the c++ object model: I create a class and use instances of them in my code. LVOOP does not fit in my "what objects are and how to use them" - world

    second: I have lots of work and I am allways short on time, so I take the risk of using a new feature and maybe needing extra time for learning only if I am sure, that new feature will save me time later. I do not believe, that LVOOP at the current stage can speed up my development.

    third: I am used to the heavy usage of old style / functional globals. The big advantage (in my eyes) is, that all data of that "module" are stored inside that VI and I don't have to drag the wires across my application (except the error cluster). As far as I experienced LVOOP classes do not automatically store their members and I have to drag lots of wires again.

  10. QUOTE(Michael_Aivaliotis @ Aug 19 2007, 09:08 PM)

    I suggest you all check it out and go to the http://forums.ni.com/ni/board?board.id=nilabs' target="_blank">NI Labs forums to request that they FINALLY RELEASE VI SCRIPTING. I can't see a better venue for this. What do you think about this?

    I would be a really good day for me, if NI releases scripting, but I am unsure whether that is the right place/way?

    e.g. If there were hundreds of users of my ADO toolkit, who would request a special feature in my forum, I guess, I'd consider this as spam. Second, I am not sure, if it is usefull to make extra pressure? I think NI knows that there is a strong demand for this feature, but NI does not want to spread this feature right now (most probably due to "who should support this stuff"-reasons?). NI is a company and if there is any chance to sell a feature or increase the value of a current product by adding a new feature, I am allmost sure, they will do it.

    third: I tried to make a post at the ni.com forums, but I don't know how. I have definitively an account and I am a registered member, but I couldn't find the response button to your post :blush:

  11. QUOTE(Omar Mussa @ Aug 19 2007, 05:47 PM)

    what's so bad about using the international SI notation? come on, squarepounds per inch or lux per acres does not seem to be an "easy to use" unit to me :P

    QUOTE(Jim Kring @ Aug 19 2007, 07:33 PM)

    But, I do love European food -- there's a good restaurant that Michael takes us to that has the best Euros.

    Yes, that's Döner Kebap. There is a big community of turkish people living in berlin, you can maybe compare that to china town, and you get Döner Kebap allmost on every corner. BTW: it's the most popular fast food, in germany. McDonalds and BurgerKing together can't beet Döner Kebap <yumm>

    and if you like beer, and if you visit europe some day, don't miss this: http://www.andechs.de/brauerei/

  12. QUOTE(Tomi Maila @ Aug 19 2007, 09:36 AM)

    who got your bribes? ;) *

    QUOTE(Tomi Maila @ Aug 19 2007, 09:36 AM)

    Off topic. North Korea got it's own domain .kp finally. Now this thread and LAVA forum is tagged for secret service investigation from North Korea
    ;)

    huh? :question: :question: If you wanted to confuse me, you were successfull ...

  13. QUOTE(Aristos Queue @ Aug 19 2007, 09:15 AM)

    that was me, I hadn't that much to tell, so I left my post unfinished :P

    QUOTE(Aristos Queue @ Aug 19 2007, 09:15 AM)

    What is Europe?
    :P

    the place where the combustion engine, the telepohne, the computer and the rocket were invented. Most probably all these inventions were made under heavy influence of the best beer the world knows! :P

  14. QUOTE(Aristos Queue @ Aug 19 2007, 08:18 AM)

    You didn't even mention the LAVA logo appearing on the LV splash screen.

    hmm ... and NI didn't mention the biggest LabVIEW community in Europe in it's keynote :P ... and I guess (just to be mean) it didn't even consider to mention ...

  15. QUOTE(David Boyd @ Aug 18 2007, 04:47 AM)

    I would've liked to have had one of those colorful tie-dyed T-shirts at NIWeek with the message "Keep Austin Wired". I actually mentioned this in jest to a couple of the NI folks at the registration booth, but of course it's a non-starter idea for the following reasons:

    - it's too local a joke

    - the joke doesn't translate

    - it would probably infringe on the original, which is copyrighted

    - it's too geeky even for them

    Dave

    you're right

    I have absolutely no idea what the jokes mentioned above wanna tell me ... :unsure:

×
×
  • Create New...

Important Information

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