setValues is called with incorrect address

[sjlongland]

Hi,

I'll see if I can get some better data, but I've noticed that pymodbus seems to have a bug when performing a register write. Reading works fine, however when I perform a write register, it first validates the address range, which works, but then tries to call setValues with the wrong register address.

2014-08-19 17:42:40,127 mm-da-modbus-slave.unit001[modbus-slave.py: 411] DEBUG validate[6] 2011:1
2014-08-19 17:42:40,127 mm-da-modbus-slave.unit001[modbus-slave.py: 691] DEBUG set-values[6] 1:1
2014-08-19 17:42:40,127 mm-da-modbus-slave.unit001[modbus-slave.py: 695] DEBUG set-values: 1 = 3

Here, I tried writing to register 2011, it validates that it can write to register 2011, but then when it actually calls setValues, it passes in register 1. We're using the pymodbus 1.2.0-2 Ubuntu package compiled on Ubuntu 12.04.

[sjlongland]

Okay, I'm an idiot. Had =+ instead of += in my code. Please disregard and my apologies for the noise.