Falevoz Y.

Hi, Thanks for your answers. With your explanations, I think that the FPGA IRIG-B decoder match better for what I want to do. I played a little more with it, and it seems that it can do the job with a few modifications. BR Yann

Hi, I have to deal with IRIG B protocol on a compat RIO. It's a 9074 and the IRIG signal is wired on a 9402. I searched on the NI website and found 2 libraries that seems to decode IRIG : IRIG-B Implementation in LabVIEW FPGA FPGA Timekeeper I played with the first one and succeed to get day of the year and hour, but not the year. As the second is recommended by NI to be used with 9467 and it is said to be compatible with IRIG protol ("The NI FPGA Timekeeper is LabVIEW FPGA IP designed to integrate the CompactRIO onboard field-programmable gate array (FPGA) clock with external timing sources such as SNTP, IRIG-B, and GPS."), I thought it would be a better solution. My problem is that there is no example of the use of timekeeper with IRIG protocol and I don't know how to use it in this way. Does anyone has already use timekeeper with IRIG B protocol and can give me an example? Thanks in advance BR Yann

My team answered NO...

Dealt with that on my first experiments... I was a bit desapointed, but I think it's logical because subclasses are not in memory. I found a tips to do that manualy... The object connectors of subclasses methods are parents classe type. So, I can call them by reference in the parent methods. It's a bit heavy, but it work... The OOP aproach is less interesting with the loss of dinamic dispatch, but it keeps the interest of encapsulation...

Hi, That's what I thought, but when we asked to NI France on the feedback they had on the use of LVOOP with TestStand, they answered that nobody tried in France and asked the US R&D. We have no answer yet. We are worried of dealing with youth bugs. I'd like to start my new project this way, but the rest of team think the risk is too important. bye

Hi, Did you already used the LVOOP and the factory patern with TestStand? What is your feedback? Could you give an exemple? thanx

Hi, I know you can edit the test cases in a text editor or in Excel. Maybe you can write your tests before coding this way... Or create empty VIs and write your tests before coding them... BR Yann

great!

ok. Thanks for your explanation. Apart from this example, don't you think the possibility of swap and permutation on more than 2 inputs elements would be interesting? Yann

It would be great if it allow to do circular permutation or symmetric swap on more than 2 inputs elements. I used a few times the RCF plugin that build an array of references, and references were always in the revert order than the one I wanted. It would be great if your tool allow to reorder automatically. Yann

I'm a big fan of freemind! I mainly use it for brainstorming animation and organizing information from different sources before writing a summary. When you are familiar with shortcuts, I think it's a very powerful tool. Yann

All right. I was mainly thinking of singleton that is, in C++, implemented by a static pointer. I figured that we could do the same in LabVIEW with a ref stored in a private fonctional global. But I understand your arguments. Yann

The recent arrival of the ability to manipulate objects by reference should allow to simplify these design patterns, isn't it? Yann

I agree that your lamp class is too simple to justify an OOP implementation. But, with not much more complexity, it can be justified by flexibility that it bring... Even more if the requirements are not so stable... Yann

CITATION(shoneill @ Dec 17 2008, 05:31 PM) I use to say that the class diagram has to be as close as possible to the real world. It make the development more intuitive and the code more comprehensible. I this case, I had a class "houseplan" that is composed of "stairs", and "stairs" are composed of "room". A particular room is the "staircase" (inheritance). On walls of the "room", you can find "openings" that can be "door" or "window (inheritance and polymorphism). After that I wonder what I need to know for each element. The houseplan attribute is its scale. For "room" and "openings", attributs are position and dimention. Then I wonder what I want to do with these elements. I want to save, load, draw, move... them. Here are the methods of each class... Yann