flodo

Thanks for your answer - especially regarding #2 I am waiting for some response from TF then...

Update: If have three problems now: 1) How do I know if all bricklets have already called the callback yet? How long do I have to wait at worst? 2) Do I need mutual exclusion inside the callbacks? (Or is it guaranteed that they are invoked one by one)? 3) Looks like the bricklets-list is not updated anymore after booting up, you can even disconnect a bricklet - the corresponing callback is still invoked when calling ipcon_enumerate(&brick_connection); .

My use case is the following: I am running a self-test after startup which compares all bricklets defined in a config-file to those which are connected. If one is not connected, then the user sees some kind of error-message, the application waits until the user plugs in the missing device and continues to check the next one.

thank you for your answer! I am not sure if we understood each other correctly: My problem is, that the Master Brick is not informed when the connection to a bricklet (like the US Distance bricklet) is interrupted. I tried the ipcon_enumerate(&brick_connection); you suggested, I then diconnected the bricklet from the master brick but unfortunately the distance_us_get_distance_value(...) function does still return sucessfully - which is a bit strange I think^^

Hi there! Is there any way (without rebooting) to update the list of connected bricklets on a master brick? (I would like to check if the "connection" to the bricklet is still good). Cheers, Flo