Modbus exception error

Z

Thread Starter

Zeeshan

I am having an issue talking to a SEL 2030

So far I have been able to talk to the SEL 2030 via the front port and gather the following info, but I am still not able to talk to it on port 14 via MODSCAN.

Below is a capture of my Comm. history with SEL.

Looking at this, could you please tell me what Device ID should I be using when I am
connecting to port 14?Port 16 is what the utility is reading from.

And should I be reading at register 40001? Should I be reading Holding register, coil status, input register?

who

COMMUNICATIONS PROCESSOR-S/N 2003216292 Date: 09/19/08 Time: 09:15:16

FID=SEL-2030-R116-V0-Z002000-D20020719 FID=SLBT-2030-R103-V0-Z000000-D20010122


Port# Device Protocol Parameters Identification

1 SEL-351S SEL 19200,8,2,N 34.5KV FEEDER 52-1

2 SEL-351S SEL 19200,8,2,N 34.5KV FEEDER 52-2

3 SEL-387 SEL 19200,8,2,N XFORMER 1 SEL 387

4 SEL-351S SEL 19200,8,2,N 69KV MAIN 152 SEL 351S

5 Unused

6 Unused

7 Master SEL 38400,8,1,N Teltone DS100

8 Master SEL 9600,8,2,N

9 Printer Ascii 9600,8,2,N

10 Unused

11 Unused

12 Other IED Ascii 19200,8,1,N SECOND WIND

13 Unused

14 Master Modbus 19200,8,2,N COMBINE HILLS 2030

15 Unused

16 Master Modbus 2400,8,2,N COMBINE HILLS 2030

F* Master SEL 2400,8,2,N

*>>sho p 14

Port communications settings for Port 14

PORT:14

DEVICE = M

PROTOCOL= M

MAP_TYPE= I

START_ID= 0

SETTLE1 = 0.0

SETTLE2 = 0.0

BUSY_DIS= N

ADDRESS1= OFF ADDRESS2= OFF ADDRESS3= OFF ADDRESS4= OFF

ADDRESS5= OFF ADDRESS6= OFF ADDRESS7= OFF ADDRESS8= OFF

ADDRESS9= OFF ADDRESS10= OFF ADDRESS11= OFF ADDRESS12= OFF

ADDRESS13= OFF ADDRESS14= 10 ADDRESS15= OFF ADDRESS16= OFF

ADDRESS17= OFF ADDRESS18= OFF

PORTID ="COMBINE HILLS 2030"

BAUD = 19200

PARITY = N

*>>sho m 14

Mathematical/move equation settings for Port 14

1 # SCADA DATA

2 000h = 01:METER:p(MW)*10

3 001h = 01:METER:Q(MVAR)*10

4 003h = 01:METER:IA*10

5 004h = 01:METER:IB*10

6 005h = 01:METER:IC*10

7 006h = 01:METER:VAB(V)/100

8 007h = 01:METER:VBC(V)/100

9 008h = 01:METER:VCA(V)/100

10 009h:0;B = 1:TARGET:OUT105 # BREAKER FAILURE

11 009h:1;B = 1:TARGET:OUT107 # TRIP COIL FAILURE

12 009h:2;B = 1:TARGET:ALARM # RELAY FAILURE

13 009h:3;B = 1:TARGET:COMMT # COMM AIDED TRIP

14 009h:4;B = 1:TARGET:SOTFT # SOTF TRIP

15 009h:5;B = 1:TARGET:TLED16 # INST.50 OC TRIP

16 009h:6;B = 1:TARGET:TLED17 # TIME 51 OC TRIP

17 009h:7;B = 1:TARGET:TLED18 # FREQUENCY 81 TRIP

18 009h:8;B = 1:TARGET:TLED22 # PHASE A TRIP

19 009h:9;B = 1:TARGET:TLED23 # PHASE B TRIP

20 009h:10;B = 1:TARGET:TLED24 # PHASE C TRIP
 
1

1998chevy1500

I have only had experience with the SEL-2032, but I am going to guess that the 2020 operates in much the same way. In the "SET P 14" command you have the option of setting an address for 1-18. What that corresponds to is the Modbus slave address assigned to that port. Ex. if you set ADDRESS01=100 then accessing the data for port 1 will be under Modbus slave 100. Also if you type "MODMAP (port number) (data region) F" it will spit back the Modbus address for that chunk of data. You can use that address directly for a 3x request or add 1 to it to use it in a 4x request.

I am just learning the SEL comm processor setup, but if you have any more questions about it let me know.
 
Top