Hello TinkerUnity!

After I implemented the great feature of rugged "enumerate_callback" using reconnect functionality in C, I detected some problem during dis-/reconnecting sensors bricklets.

When the enumerate_callback is triggered during a LAN or USB disconnect, it working quite well, but don't recognizes if a sensor connection has been lost.

My application is running and reporting values of humidity verry well, but if I disconnect the cable to the humudity bricklet, no detection happens!

The callback of the humidity callback is still triggered (answering with obviousley correct values!), only the value has been changed from 45.00% to 10.00% rH (or 10.10%). It seems, that a disconnect of the cable to a bricklet hasn't been detected by tinkerforge. I tried it with other bricklets as well (voltage, temperature...), same result. Is there any way, to monitor the connection to the bricklets? It's important for me to detect, if a bricklet is not valid or alive! If I receive values I hope that this values are correct Maybe I have to evaluate the return "E_UNKNOWN_ERROR_CODE"?

Thanks a lot in advance for some hints,

Wolfgang

Curious what the TF guys will answer, but may I ask why you need this feature? Once a stack is configured with X bricklets, why you need that configuration to change.. at runtime?

I just disconnected my humidity bricklet during runtime. Even if no hum. bricklet is connected I get a callback from the humidity bricklet. How can I check, that the value which was returned is valid?

It's not the configuration, it's just to know that the returned value is valid.

(Damage of cable, broken sensor ...)

I see. Yes, I agree that the API should, one way or the other, inform the application that a bricklet has ceased to function, or in any case, be available. It is not correct for any getXXXX() to return a value, when in fact the bricklet has not produced that value.

Bricklets are not hotplug capable. Please don't connect/disconnect Bricklets in a running system.

 

Also there is no way for us to detect that a Bricklet is disconnected, so we can't report it.

That sounds logical to me. Even if such a feature would be nice .

Thank you for your explanation.

Wolfgang