How to trace Code interface node

[Ali Afzal]

Hello and Good Day!!

And Thanks to all the people who are around to help other people like me on each step when needed

well related to my question I have been given a project which need upgrade so code is pre written and have now documentation related to that project so it include Code interface nodes (CIN) to communicate with different cards like Transputer and Taxi ...

so i want to track down the CIN c files can anyone help me or define the steps to track down c file

thanks in advance

Regards

Muhammad Ali Afzal 

[A_Person]

If I understand your issue correctly, you have existing LabVIEW code that is using Code Interface Nodes (CIN) and you want to find the C files defining the code for each node.

The first thing is that the CIN functions do not call .c/.cpp files directly.  The code has to be compiled to a .lsb file that the CIN function calls.  Unfortunately, the CIN function does not, as far as I know, give the specific path to the .lsb file it is calling.  You may be able to get a hint as to where it's looking my right-clicking the function and choosing Reload Code Resource From...

Now, the problem is that even if you find the correct .lsb file, it's location may not have any relation to the location of the original C file.  The project used to build the .lsb file will likely have the same name but it is not a guarantee.

Basically, it is going to be difficult to find the C file without having any documentation as to its location.  If I didn't address your question or if you have further questions, please let me know.

[Ali Afzal]

Dear Alex 

thanks for your reply . Yes you got my whole question in right direction.... And still my question is same can you guide me so I can give it try to this matter... I know I don't have documentation and I am stuck on this so I have to find some way..

waiting for your guidance

Regards 

Muhammad Ali Afzal

[smercurio_fc]

Your question may be the same, but unfortunately, so is the answer. There is simply no way to get the information you're looking for from LabVIEW. As noted, CINs load compiled code. You need to perform a search on your computer, or wherever you got the code for .c file that look like they are the source code for the .lsb file.

[Dennis_Knutson]

To further complicate things, the lsb file is usually part of the VI itself and not external. That means that unless someone there developed the driver for these cards, there would be no lsb or c code at all that you can look at. If someone there developed the code, it could be anywhere and unless you have good documentation control or source code control, could also have been deleted. Do you even know where the CINs came from? Do you know where the boards were purchased from?