search

OpenStuder / openstuder-gateway

Gateway enabling access to Studer Innotec devices from Web or via Bluetooth
MIT License
3 stars 1 forks source link

Communication conflict between openstuder gateway daemon and openhab3 modbus binding - same port /dev/ttyUSBx #11

Open Jusufs opened 1 year ago

Jusufs commented 1 year ago

It is a conflict between loaded openstuder-gateway daemon and modbus binding in Openhab 3 ! Openhab2 doesn't have a problem. So sorry for disturbing. Problem should be clarified on Openhab3 forum. But 1550 Parameter Problem is still open. I wrote some ticket to Studer.

Jusufs commented 1 year ago

Openstuder works fine but with change of params is written only in flash ! I'm missing temporary write params only to RAM from openstuder interface.

Some questions to Studer developer:

  1. Last FW684 - parameter 1550 (flash write enabled) still doesn't memorise state in a system with Xcom CAN and Xcom485i adapter. Memorised NO value after fully DC disconnected xtender from battery doesn't work in this configuration. Memorising works perfect if a Xcom CAN module isn't present in the system ! Writing in flash is not guarantied after aprox. 1000 writes.

  2. Are all parameters writable only to RAM ?

  3. Are there a limitation according change only in non powered state ?

  4. What about new gpg ? curl -s --compressed "https://www.openstuder.io/ppa/KEY.gpg" | sudo apt-key add - Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))

Thanks for answer, maybe this should be addressed to studer service. A discussion option in this github repo would be great.

P.S. Modbus Studer Xcom485i https://github.com/studer-innotec/xcom485i works fine, also with correct write only to Ram and into flash !!!

Serial communication via Xcom232i doesn't work correctly. https://github.com/zocker-160/xcom-232i This would be fine to get working. Lot of users have 232i adapter.