EWEB reading 3rd Party Device SNMP Data Value

[nakedpanic]

View attachment trace1.pcap.txt

Attached with .txt

 

[nakedpanic]

SocketWriteMsg
Service Type = Write Socket
Service Code = 4e
Class = 342
Instance = {socket} 32111
Attribute = 0

SocketWriteParam.Timeout = 5000 {DINT}
SocketWriteParam.ToAddr.Family = 0 {INT}
SocketWriteParam.ToAddr.Port = 0 {INT} tried 161 here
SocketWriteParam.ToAddr.Addr = 0 {DINT}
SocketWriteParam.BufLen = 213 {DINT}
SocketWriteParam.Buf = .[30]..[5]. {SINT[480]}{in HEX}

 

[nakedpanic]

Changed the source length from 213 to 229 and the message went through.

 

[Contr_Conn]

I see 3 devices doing SNMP
.157 is PC,
.185 and .200 - who is who?

also what is message length?

It is very hard to help you by squeezing little pieces one at the time.
Can you post your program?

EDIT - you beat me posting length - 229 is correct length 213+16=229

 

[nakedpanic]

What's a good format to post it, I'm having difficulty with the size, even zipped.

the .185 is the device call.

 

[Contr_Conn]

If you strip your acd down to 3 messages then it will not take too much room zipped

 

[nakedpanic]

Looks like the read is working. I have to parse the buffer, but the data is there.

 

[Contr_Conn]

Are you sure you need 213 bytes? I think you can make it much shorter without padding 0s

 

[nakedpanic]

Are you sure you need 213 bytes? I think you can make it much shorter without padding 0s

i think so too. Definitely want to streamline this.

Still struggling with getting the size down. I should have started with a new program.

 

[Ian S]

Did anyone ever get this working?

I've got a UPS that I'd like to interrogate over Ethernet, and since I'm already using an EWEB module in my PLC, this would seem like a good way to go.

Regards,
Ian Shaw