SIT Issues - Undefined Functions and non-compilation

[RichardJarvis]

Hey Jimmie,

Thank you for the link and help. Sadly we're not at the stage where I could pass a DLL, with the UDP blocks, through there. It's whilst compiling/linking that the error occurs for the UDP blocks. As an aside we're also not using wsock32.dll but instead ws2_32.dll. Could this be an issue?

Using the tool on the basic (non custom UDP) model DLLs shows them to be fine.

Rich

[Jimmie_A.]

Hello Rich,

Can you build the DLL with UDP blocks if you select another template (i.e. not nidll.tlc)? If so build the DLL and then verify the DLL using the tools I mentioned before.

[RichardJarvis]

Jimmie,

When building using something other than nidll.tlc it generates code but doesn't compile/link properly. I think we'll probably end up looking into this at a later time as this is leading me to believe it's something with the way our UDP blocks are coded.

Rich

[RichardJarvis]

Hi Adnan,

Q) From your screenshot, it looks like you are using the Import Shared Library Wizard.  Am I correct?

A) Yes you are correct from the screenshot I gave you

Q) If so, is there a particular reason as to why you do not want to use the SIT Connection Manager?

A) As we need the UDP functionality (to send and receive model data to multiple other systems) we originally planned on using SIT Connection Manager as suggested and our custom UDP blocks. Obviously that is the other issue and whilst SIT Connection Manager gives a block diagram it doesn't seem the easiest to modify to place LV UDP blocks and parsing sub-VIs etc into. Our thoughts were to import using the wizard and setup the functions as required with the LV UDP data communication blocks and parsing done around them. Would this be too tricky?

An easy solution would obviously be to pass the values back to a host and get that to send the data on, however we wish to run the model headless on the cRIO

Q) My next question involves using some of the models that are shipped with SIT. Have you tried the procedure with the sine wave example?

A) All models, including some basic test models we made, seem to work when using SIT connection manager. Haven't tried using import shared library (see above) to see if that gives a similar response

Thanks again,

Rich

[RichardJarvis]

Right,

For fear of trying to deal with too much at once ignore the preceding questions/info.

Q) Is it possible to import an SIT generated DLL using the Import Shared Library Wiard. If so how?

Regards,

Rich

[AdnanZ]

Hi Richard,

It looks like the reason you are experiencing some problems is because the SIT Connection Manager is purposely there to recognize SIT DLLs and is having some trouble importing into LV using the Shared Library Wizard.  Adding code to the block diagram after SIT has generated some code shouldn't be a problem, just do not change anything that is highlighted as something that shouldn't be changed.  The block diagram will say what parts should not be changed.  Also, anything that is added should be placed in a flat sequence structure so it is not removed or changed when SIT generates code again.  I hope this helps. Let me know if you are facing any other issues.