Animatics dll calls

[systemcrash]

Hello,

Thank you for telling me which dll but when I executed the below command

"regsvr32 Interop.INTEGMOTORINTERFACELib.dll" I got the following error message,

DLL was loaded but dll registerserver entry point was not found. File cannot be registered.

[nkb]

I am not sure, but I think the reason you are having problems using a register command is because this is not a "standard" dll, but a "COM" dll.  That is what I got out of reading some of the earlier posts and why I chose the Active X route (no registration required on my part).

[systemcrash]

That Dll is a .net dll, and when I select the class ISMImotor or ISMIComm, I fget a message

"THis class contains no public constructors".

When I chose Active X refnum I got message "The selected file is not .NET assembly, type library or automation executable.

Where did you find INTEGMOTORINTERFACELib.ISMIComm  module?

[nkb]

Not sure what you mean by "where I found it" but it is installed an dregistered when you download and run the SMI 2.331 install found here: http://www.animatics.com/web/smi.html.  This is the library that the animatics SMI application uses to communicate with motor. After it is installed, you can find it by right clicking on Active X refnum and then browsing to the item highlighted in the screenshot below.

  

[systemcrash]

Thank you, Got the library.

I was playing with VISA to RUN the motor and now will try with the help of Active X

[systemcrash]

I have a some problem when I create a Installer and  when I run my program the motor program does not work, but in edit mode it works perfect.

I doubt I haven't included SMIengine active X file while building a executable.

Do you know where to find that active X dll so that I can include while creating installer.

Thanks

[nkb]

Sorry, I do not know which file(s) specifically need to be included in the installer.  I have always included a seperate install of SMI as part of the installation package.  It's not the most convenient method, but for the volume (a few installs a year) it makes the most sense for me.

[rolfk]

---

@systemcrash wrote:

I doubt I haven't included SMIengine active X file while building a executable.

Do you know where to find that active X dll so that I can include while creating installer.

Thanks

---

You don't simply include an ActiveX DLL into an installer to make it available on a different system. You need to register that DLL on the target system.

This can be as simple as calling regsrv32 on the DLL in a command line prompt or as complicated as running a specific dedicated installer for that ActiveX DLL. Just including it in your LabVIEW project build is definitely not enough.

So you may doubt that you haven't included the ActiveX file in your build, but I'm 100% sure it isn't registered (installed) on your target system. How to get that happening I can't say for sure, but the safest bet is to actually run the according installer on that system and yes integrating installers into an installer to make it a one click experience is sometimes a lot of tinkering.

[dreis]

nkb,

I know its been a while, but i was wondering if you could help with this problem

I have downloaded your .vi and cannot get it talking to my smart motor.  i have it on the right com port, and it throws the error that it cannot open the serial path.  did you run into this problem?  

it's one of those things that I've been trying to talk to this motor in labview for more than a week and i was using the old VISA commands until when I called animatics they said the timing would be all thrown and you need to either use the dll or go through SMI.  but with your .vi, i feel like i'm 97% to the finish line.  your help is greatly appreciated.

dreis

[nkb]

dreis,

I have seen port issues in the past, but typically the solution is straightforward.  Here are some known issues:

1.  SMI interface open when running the vi.  SMI must be closed or it will hold the com port hostage.

2.  Com port settings match (baud, parity, etc.).

3.  USB to RS232 converter issue.  Not sure if you are using one, but I have had trouble with these in the past.  We are currently using a Trendnnet TU-S9 and it has been very reliable.

4.  Win Vista.  The issues we had were very erratic and eventually upgraded to Win 7 to fix the issue.   XP has never been an issue. 

I have this code in probably a half a dozen automated fixtures, some of which are running on a daily basis, and it is very stable.  Most of them are Dell laptops running Win7 and connecting through the USB adapter mentioned above.

Good Luck,

nkb