sv/tsun-gen3-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

allow only one MODBUS retry

Browse Source 
- More than one retry usually makes no sense, as
  random errors are usually corrected. If the
  first retry also fails, the chance that a second
  or third retry will be successful is very small
This commit is contained in:
Stefan Allius
2024-05-21 19:37:55 +02:00
parent 9e38cb93ea
commit da2388941e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
app/src/modbus.py
View File

@@ -83,7 +83,7 @@ class Modbus():
'''Response handler to forward the response''' '''Response handler to forward the response'''
self.timeout = timeout self.timeout = timeout
'''MODBUS response timeout in seconds''' '''MODBUS response timeout in seconds'''
self.max_retries = 3 self.max_retries = 1
'''Max retransmit for MODBUS requests''' '''Max retransmit for MODBUS requests'''
self.retry_cnt = 0 self.retry_cnt = 0
self.last_req = b'' self.last_req = b''
@@ -103,7 +103,7 @@ class Modbus():
self.tim = None self.tim = None
def __del__(self): def __del__(self):
logging.info(f'Modbus __del__:\n {self.counter}') logging.debug(f'Modbus __del__:\n {self.counter}')
def build_msg(self, addr: int, func: int, reg: int, val: int) -> None: def build_msg(self, addr: int, func: int, reg: int, val: int) -> None:
"""Build MODBUS RTU request frame and add it to the tx queue """Build MODBUS RTU request frame and add it to the tx queue