Re^5: Perl calling my.DLL for serial port work.

That means that the module Win32::API is not installed with your Perl. This is unlikely if you are using ActiveState Perl, but if you are using Strawberry Perl, you will have to install Win32::API via CPAN:

cpan Win32::API
[download]

Also, I recommend you read the documentation to Win32::API before modifying the code I posted. The code I posted was not intended for modification - you should have left it as is, and just called the code:

SSC_OPEN( 1, 2400 );
[download]

Comment on Re^5: Perl calling my.DLL for serial port work. Select or Download Code

Replies are listed 'Best First'.
Re^6: Perl calling my.DLL for serial port work. by kansaschuck (Sexton) on Feb 03, 2008 at 18:52 UTC
I'm using ActiveState and did some research and found that `ppm install Win32-API` [download] will install the API. As for code mods: I made the assumption that the 'I' and 'II' were place holders to pass the needed info to the program. The OPEN needs to know com port and baud rate. SSC_OPEN(port,baudrate) . The MOVE needs notified of SERVO number and SERVO location. SSC_MOVE(servo,position) Thanks again.... getting closer :-)	[reply] [d/l]
Re^7: Perl calling my.DLL for serial port work. by ysth (Canon) on Feb 03, 2008 at 19:17 UTC
No, the I and II are literal instructions to Win32::API as to how to pass those parameters. Win32::API->new returns an object that can be used to call the DLL function. You should only do the my $SSC_MOVE = ...; sub SSC_MOVE { ... } once, and then call the defined SSC_MOVE sub as many times as you want with the actual values. -- Online Fortune Cookie Search	[reply]
Re^8: Perl calling my.DLL for serial port work. by kansaschuck (Sexton) on Feb 03, 2008 at 23:16 UTC
Ok... that's working nicely. Thanks!	[reply]