search

sunspec / models

SunSpec Model Definitions
Apache License 2.0
84 stars 52 forks source link

Using model from id range 64900 as a placeholder to keep adresses stable #226

Closed FW22 closed 1 year ago

FW22 commented 2 years ago

Hi @bobfox , some of our customers rely upon static adresses of modbus registers. I'm aware that this is not SunSpec compliant and an initial model scan should be used instead to determine the adresses dynamically. Nevertheless we would like to keep existing applications working.

Therefore we would like to integrate a model from the id range 64900 (experimental use) as a placeholder between model 123 and model 160. This model would have a length that allows us to keep the same adresses for model 160.

I expect SunSpec dashboard to skip models in the 64900 range. Could you please confirm that?

Would this approach be SunSpec compliant?

bobfox commented 2 years ago

I am not sure I completely understand. Would the length of the model between 123 and 160 change over time or is it a one time adjustment?

The dashboard will ignore any models for which it is does not have the associated model definition.

If it is a one time adjustment, I don't think there are any issues with it. I think it would probably be better to get a set of extended model IDs assigned to you so there is no confusion about the context and meaning of the extended model. You can reserve them in blocks of 10 models by just sending a request to support@sunspec.org.

FW22 commented 2 years ago

The length would be a one time adjustment. The idea to reserve a set of extended model ids is good, I'll think about it. But most importantly we don't break something with our appoach. Thank you for your quick response!