You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are dealing with a device that claims to be Sunpec-compliant, but fails to respond to reads of holding register 0, making it impossible to use the standard discovery process as implemented in the sunspec module.
Some options to resolve the issue:
Time out reads, so the process could proceed from 0 onwards
Enable specifying the starting address for discovery
The text was updated successfully, but these errors were encountered:
I think I'll add a discovery config struct for those two things:
structDiscovery{/// Addresses to check for the SunS identifier (default: [0, 40000, 50000])info_model_addrs:Vec<u16>,/// Timeout to be applied for every `read_holding_register` callread_timeout:Duration,}
Hi,
We are dealing with a device that claims to be Sunpec-compliant, but fails to respond to reads of holding register 0, making it impossible to use the standard discovery process as implemented in the sunspec module.
Some options to resolve the issue:
The text was updated successfully, but these errors were encountered: