• Replies 9 replies
  • Subscribers 582 subscribers
  • Views 593 views
  • Users 0 members are here
Options
Related

[Error] Invalid settings UNIT 001d PORT1_SNMP Hikvision Error_in_CMD-3 1 Generic 000029 Driver 00000258 (0x102)

Giancarmine

HI,

in the log file I have this error. If I try to read a variable with SNMP, I display #BAD. 

The device is a camera (Hikvision). This camera has not public fields (OID start with '.1.3.6.1.2.1') but has only private field (OID start with '.1.3.6.1.4.1').

HELP ME. I don't understand, In the same project I already read other snmp variables of another device and it works.

Thanks

Parents
  • The I/O device configuration could be an issue. I once downloaded a SNMPII example project with multiple I/O devices in it.
    Configuration was like this:

    BOARDS definition: 1 board called 'BOARD1'; type 'SNMPII'; address '0'

    PORTS definition: 1 port per device called 'PORT1', 'PORT2', etc.pointing at BOARD1; port numbers were unique; special options field contained a reference to the dbf with the OIDs and variable addresses: 'SNMPVARS1.DBF', 'SNMPVARS2.DBF', etc.

    I/O device definitions:
    'IODev1': number 1; address '192.168.0.99 public'; port 'PORT1'
    'IODev2': number 2; address '192.168.1.215 public'; port 'PORT2'
    etc.

    Variable addresses were unique across all devices (addresses of IODev1 were not used in IODev2 variables).

    Tag names in Variable.dbf must match the NAME field in SNMPVARS*.DBF
    Tag addresses in Variable.dbf must match the INDEX+SNMPTYPE fields in SNMPVARS*.DBF
    I/O device names in Variable.dbf must match the DEVNAME field in SNMPVARS*.DBF
    Data types in Variable.dbf must match the CTYPE field in SNMPVARS*.DBF

    The SNMPNAME, OID, SNMPTYPE and R/W fields in SNMPVARS*.DBF must match the MIB entry you want to read/write.

    I always fill and edit these DBFs in Excel because I never get the MIB2CIT tool to work. I don't know if it is even supported nowadays.
Reply
  • The I/O device configuration could be an issue. I once downloaded a SNMPII example project with multiple I/O devices in it.
    Configuration was like this:

    BOARDS definition: 1 board called 'BOARD1'; type 'SNMPII'; address '0'

    PORTS definition: 1 port per device called 'PORT1', 'PORT2', etc.pointing at BOARD1; port numbers were unique; special options field contained a reference to the dbf with the OIDs and variable addresses: 'SNMPVARS1.DBF', 'SNMPVARS2.DBF', etc.

    I/O device definitions:
    'IODev1': number 1; address '192.168.0.99 public'; port 'PORT1'
    'IODev2': number 2; address '192.168.1.215 public'; port 'PORT2'
    etc.

    Variable addresses were unique across all devices (addresses of IODev1 were not used in IODev2 variables).

    Tag names in Variable.dbf must match the NAME field in SNMPVARS*.DBF
    Tag addresses in Variable.dbf must match the INDEX+SNMPTYPE fields in SNMPVARS*.DBF
    I/O device names in Variable.dbf must match the DEVNAME field in SNMPVARS*.DBF
    Data types in Variable.dbf must match the CTYPE field in SNMPVARS*.DBF

    The SNMPNAME, OID, SNMPTYPE and R/W fields in SNMPVARS*.DBF must match the MIB entry you want to read/write.

    I always fill and edit these DBFs in Excel because I never get the MIB2CIT tool to work. I don't know if it is even supported nowadays.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.