So it sounds like DNP3 as a slave is useful in a traditional PLC? DNP3 Master capabilities are not needed? If this is true, then this is good (a PLC is not a SCADA system). If this is not true, please explain how you would set up a PLC as a DNP master to configure a bunch of DNP3 slaves. Normally, comm is done via polling from master to slave, but DNP3 looks quite advanced for a Master to configure what we call "report by exception" requests in the slaves, causing the "slave" to initiate the transfer? This seems do-able on a peer network like Ethernet, but I'm not sure how it would work in a multi-drop serial network, where you speak only when spoken to?