thebean

Hi Greg, Thanks for your help, after further inspection the final 4 bytes of the packet appears to be the lower 4 bytes of a 64 bit nanosecond timestamp with the reference timestamp located near the start of the packet. This is a black box reverse engineering exercise, so unfortunately we don't have manuals to assist us. Thanks for your help. Regards, Mark

Hi, I'm currently trying to use RevEng to find the CRC for an ABB Protection Relay protocol. I have lots of packets with example CRC's but with little control over the packet contents. When I try and run the RevEng search with some sample packets I get the following message repeated over and over and no apparent progress towards a CRC identification after a couple of hours. ./reveng -w 16 -s 00481582bd6b1f73824ccf9d058c0800040100000000fffffffeffffffffffffffffffffffffffffffff000000000000000001fe0da6ffffffff0000000088880000e97fbfd3000009fa1f873865...

Counter - Create Event does not generate a counter event

Add ability to create command events from web ui

Ability to specify time when triggering an event

New keyword to reset outstation to default

Ability to create non-sequential DNP3 point lists

Keyword works 50% of the time. The other 50% immediately retrying the keyword will...