Permalink
Commits on Jan 5, 2011
  1. Bump to 'v0.2.0'.

    committed Jan 5, 2011
  2. Added a new server example that shows the use of Creationix's "Stack"…

    … library as the handler.
    committed Jan 5, 2011
Commits on Jan 3, 2011
  1. Fix README formatting.

    committed Jan 3, 2011
Commits on Jan 1, 2011
  1. Ensure the quantity is satisfied for "Read Input Registers". This sho…

    …uld be done for all REQUEST / RESPONSE functions.
    committed Jan 1, 2011
  2. try / catch the REQUEST and RESPONSE functions, since they are allowe…

    …d to throw Errors, and those should be emitted on the Modbus stack instance.
    committed Jan 1, 2011
  3. Remove the 'length' property before emitting the application layer ev…

    …ent (for good). It's a protocol detail, and should be hidden at the application layer.
    committed Jan 1, 2011
  4. Don't call `cleanup()` on ModbusResponseStack until after `writeRespo…

    …nse()` or `writeException()` has been called.
    committed Jan 1, 2011
  5. Added `ModbusResponseStack#writeException()` to send an exception cod…

    …e after a MODBUS request from a master (client).
    committed Jan 1, 2011
  6. Ensure that an 'error' is thrown/emitted before any unimplemented fun…

    …ction codes are attempted to be called.
    committed Jan 1, 2011
Commits on Dec 31, 2010
  1. Fire an 'error' event when a slave (server) responds with an exceptio…

    …n code. Don't fire a 'response' event.
    committed Dec 31, 2010
  2. Added 'npm test' script.

    committed Dec 31, 2010
  3. The individual REQUEST and RESPONSE parsing functions no longer need …

    …to parse the Function Code, as it is now handled internally.
    
    Also, READ_INPUT_REGISTERS, and any other "list" type response should directly return an Array instance.
    committed Dec 31, 2010
Commits on Dec 17, 2010
  1. Bump to 'v0.1.0'.

    committed Dec 17, 2010
Commits on Dec 12, 2010
  1. Add MIT license.

    committed Dec 12, 2010
Commits on Dec 11, 2010
  1. A few changes; see below:

     1) Have '_reqNum' be a part of the parent Stream, since a
      ModbusRequestStack instance is only good for 1 request anyway.
     2) Clean up the 'data' listener just before a ModbusRequestStack
      instance emits 'response', and thus the instance is finished.
      TODO: Use a `StreamStack#cleanup()` function once it gets implemented.
     3) Don't use 'EventEmitter#once()`, unnecessary.
     4) Call all REQUEST and RESPONSE functions with 'this' as
      the ModbusRequestStack or ModbusResponseStack instance.
    committed Dec 11, 2010
Commits on Dec 4, 2010
  1. Remove warning.

    committed Dec 4, 2010