Jump to content

dannyt

Members
  • Posts

    416
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by dannyt

  1. Though I fully agree with the comments about the quality of the software provided and also the fact that if all source code is provided you can maintain something yourself if you need to, I feel you have raised key point here. To be a open source / free LabVIEW product that gets a Gold or Silver Product recommendation by NI, the Product or community behind it must still be active and vibrant. As said previously the Open Source tools that work all have healthy & active communities behind them look at Bugzilla, Subversion, Python and many more. Without that active & vibrant community behind the tools, they will die off leaving you in a dead end situation when they no longer work with newer version of OS or LabVIEW. Some new user of LabVIEW may never even really get to grips with the tools and use them with some level of support & help. I think the LAVA CR tools & JKI free tools are all example of good and active communities. I regretfully for this reason have concerns regarding the OpenG tools. I am a keen user of the OpenG tools, I have taken part in the OpenG forums and even once posted a possible fix for a tool that no longer works for LabVIEW 8.2.1 or newer. So with apologies to Ton and other who I know have and do work hard on OpenG I must say that to me it no longer fit this criteria. Looking at the OpenG forums there is very little activity and has been for a long time now. In fact the most recent posts are all spam one. As I said this is a personal option, but as LAVA CR's grow & the NI community grow OpenG feel to be faltering. Dannyt
  2. thinking everday, I learn that I know less about LabVIEW than I thought I did the day before

  3. Thank you Shaun, that makes sense, along the lines I though people meant, just asking in case there was any more meaning to it than that. typical topics include JKI state machine how do I model this how many events I am still working my way through these :-) Danny
  4. Hi, I have been trying to catch up on interesting topics I have put to one side in the past and have spent a fun day reading about state machines and different architectures, I still have a great deal more to read and learn. I keep coming across the term Macros / Marco state in a number of the topics and I am not fully sure I understand this term. With regards to the JKI state machine, I think the Marco states are states where no work is actually done but new state transitions are push on the existing queue of states so that can easily find them. I have searched on Lava for this term and though it has lead me to reading a lot more threads about QSM & SM I still have not found out what people mean when using this term. Any explanation would be appreciated. regards Dannyt
  5. I can use notifications to do what I want, but it is not quite what Iwas looking for, more something like the bookmarks on the Dark side.
  6. I see what you mean it the code repository thanks. I had hoped you could do it for general topics Dannyt
  7. Hi, I the settings page there is a tab "Contents I like", I assume this can be used to hold /bookmark, particular forum topics that appeal to me, I cannot however find how to "like" any topics. I know how to subscribe to changes to a topic, but not just bookmark one. Can this be done and if so how. Sorry if this is obvious and I have missed it Dannyt
  8. listening to Gerry Rafferty

  9. Hi, I am using and have used ClearCase for many many years, both for LabVIEW, the last four years or so & for text based languages, for longer than I can remember. I have also used CVS, a little Mercurial Hg and a little Subversion. We have a team of five developers working on around 1500 VI's in ClearCase. LabVIEW does introduces it's very own problems with source control no matter what source control tool you use. There are pros & cons to all of them and all can be used equally as well in the right situation. You do need to ensure that your procedure are tailored to the tool you are using however. The biggest thing you can do to improve source control issues with LabVIEW is to use LAbVIEW 2010 and the "separate compile code and source code" feature. I would be happy to work with any of the three tools. The two main problems with ClearCase are 1) cost (but you already have it installed so not an issue here) 2) you do need a good fast / reliable Intranet to get good performance out of it. But ......... I think you have asked the wrong question, the comparison is great if you have no tool & need to get one, but you are already using ClearCase. So I would change the focus and specify in what way ClearCase is failing you in your needs at present. Get a list of your current problems and issues with using ClearCase and then ask if these other tool solve these issues or not. If they do all well and good but if not you could do all the change over work and be no better off. It might be that you current problems are not with ClearCase but how you are using it and you procedures and if that is the case and you move to a new tool you will just take those problems over with you. I have seen this happen before. regards DannyT
  10. Yep Happy Christmas to all LAVA'rites everywhere. Danny
  11. That will be why the central heating & hot water boiler has broken down :-)

  12. wow lots of snow before christmas, this does not happen in Devon

  13. Hi Ton, Thank you for pointing my that way. I have created a new entry on the Wiki ClearCase and have put in there more details on how to set this up. I will try and over time fill in some more of the heading I have created to make it a more full and worthwhile entry. I hope people forgive my spelling. I am not confident on the categories in the wiki but it would be nice for the Set up differencing capabilities page to actually go to a page with links to settingup subversion, setting up Mercurial, setting up ClearCase etc. rather than just go to the subversion one cheers Dannyt PS you can use spaces in the map file mentioned about so use z_whole_copy compare ..\..\..\..\National Instruments\Shared\LabVIEW Compare\LVCompare.exe z_whole_copy xcompare ..\..\..\..\National Instruments\Shared\LabVIEW Compare\LVCompare.exe rather than z_whole_copy compare ..\..\..\..\NATION~1\Shared\LA9418~1\LVMerge.exe z_whole_copy xcompare ..\..\..\..\NATION~1\Shared\LA9418~1\LVMerge.exe
  14. For me the new separate source and compile code, at last you can develop in parallel with a team and use source control in a really useful way.
  15. Oh I so agree with the new probe window. I think a number of the "windowed" IDE addon's are like that, only half thought out in usability terms. The heirarchy view is next to useless in any real way. Dannyt
  16. Hi all, I have got the LabVIEW LVCompare.exe working with ClearCase on windows. This means that you can do LV differencing using the source control integration with LabVIEW or from the ClearCase explore or the tree view. Would anybody be interested in a step by step guide on how to do this ? For those in the know you just need to edit the ClearCase map file ( C:\Program Files\Rational\ClearCase\lib\mgrs\map ) and change the compare & xcompare type managers for the correct file type. z_whole_copy compare ..\..\bin\cleardiff.exez_whole_copy xcompare ..\..\bin\cleardiffmrg.exechange to z_whole_copy compare ..\..\..\..\NATION~1\Shared\LABVIE~4\LVCompare.exe z_whole_copy xcompare ..\..\..\..\NATION~1\Shared\LABVIE~4\LVCompare.exe but as I said if anybody was interested I could do a step by step guide. Danny
  17. Thanks for correcting me Darren and sorry for making the wrong assumption. Danny
  18. Sorry Suresh, but I am being very slow here and I still do not quite get what you are asking. So your LabVIEW code is written in LabVIEW 8.6 ? You are loading up you code into LabVIEW 2010 and then running the VI Analyzer ? saving the *.rsl file and then starting up LabVIEW 8.6 and trying to load the rsl file ? LabVIEW compatibility matrix look about halfway down, it looks like you cannot do what you want to do.
  19. I assume you are talking about a *.rsl file that you save after running a VI Analyzser test in LabVIEW 2010. I have not actually tried this but as the 2010 VI Analyzser has new extra tests in it that the 8.6 Analyzser will know nothing about I would not expect it to be backwards compatable. What are you actually aiming to do here, it will be easier to offer help / suggestions
  20. Your reply has left me a little confused, I only put the outer for loop in with a simple hardcoded 4 to show you what the output would look like with several lines in it. My answer was only meant as a guide to show you one possible way of doing what you want to do and I was leaving you to put it into your solution How you decide to run you loop generating the data is up to you, it can be a while loop with an exit or whatever you want. If you want to update the output one line at time then just put you string indicator inside the loop. Danny
  21. This may not be the most efficient way but it does work and allows quite a bit of flexibility in you log sting
  22. what display mode do you have on your log sting ? normal display or "\" code display ...... if you have it set to the code display one then yes you line feed will be seen as you say, it will only appears as a line feed in normal mode. As I said before you should look at the format into string method this will help you build up a log string with timestamp and text and other data types. Danny
  23. Hi Madhav It would help if you posted an example or snippet of you code, but if I understand you problem correctly rather than use concatenate, you should be looking at the "Format into String" function, that way you can build up your output string from a number of different input types, ie hex number / time stamp and also easily put in formating like tab or linefeed. hope this helps Dannyt
  24. Hi, Have you done a general Web search of "labview error 1172" there are quite a few hits regarding that error. Failing that you really need to post your VI or at least a screen shot of it for people to be able to help cheers
×
×
  • Create New...

Important Information

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