01-24-2006 04:04 AM
01-25-2006 05:03 AM
01-25-2006 06:28 AM
More Info on problem:-
LabVIEW 7.1 Windows XP SP2
I’m trying to control 2 SNMP instruments as part of a test setup. One is an APC power switch, the other a Picture Quality Analyser. I have some LabVIEW SNMP ‘driver’ software written by my customer. This uses LV’s UDP functions for communications.
The PQA (Omnitek) instrument was developed using the windows SNMP API agent functions, so the Windows SNMP services need to be running.
I can control the APC power switch fine until I start the Windows SNMP service running. This seems to take complete control of the SNMP port - port 161, stopping any LV UDP communications with this port. I receive the error message:
‘Error 60 occurred at UDP Open in Send_Receive UDP.vi->Simple SNMP Communications.vi’
Whenever I try to do any UDP comms on port 161 from LabVIEW with the service running.
I have tried to find out whether the SNMP toolkit has the same problem. I have not received a response from my emails so far.
Davith
01-25-2006 07:03 AM
01-25-2006 08:28 AM
Adam
Thanks for your comments.
It looks like the only way forward is to develop a manager interface using Windows SNMP API calls.
I’ll probably do this by developing a DLL using CVI to interface to the SNMP API. I think its better to use CVI rather than LabVIEW for this. Its easier to interface to the odd data types that Microsoft seems to like using. I will then call this DLL from LV.
It is a shame that the SNMP Toolit people do not respond to emails. I suspect their code uses UDP calls, as it looks like it was developed before the Windows SNMP API was available.
Davith
01-25-2006 12:16 PM
08-28-2006 11:48 AM
08-29-2006 02:14 AM
Hi Serene,
I have not used the toolkit to receive traps. I use a loop with a UDP call monitoring port 162, with a 2s timeout. I then decode any information I receive. I suspect the toolkit does something similar.
The most likely reasons for you not receiving traps on a ‘Windoze’ machine is that the Windows SNMP services are turned on. All SMNP services should be disabled on the machine running the LabVIEW code. The next most likely reason is that the equipment generating the traps has not been set to send traps to the IP address of the LabVIEW machine.
Good luck
Davith
08-29-2006 04:20 AM