Open nickcluteturck opened 1 year ago
At first I thought of using wrong or missing device to clear the data, but this would prevent us from seeing the DID/VID when we are in fact connecting the wrong device. That also made me think, do we want to write the DID / VID when we connect an AOI to a port and change the setting to compatible device? That seems to be the way profinet does it when we use device specific objects on the ports.
I think that would be good so that you get the red LED on the port if you connect the wrong device.
From: jose-sanchez-tcan @.> Sent: Monday, August 21, 2023 5:28:41 PM To: nickcluteturck/IOLinkAOIs @.> Cc: Clute, Nick @.>; Author @.> Subject: Re: [nickcluteturck/IOLinkAOIs] 8IOL AOI - Update Port Info Trigger - Need different approach? (Issue #6)
External E-Mail
At first I thought of using wrong or missing device to clear the data, but this would prevent us from seeing the DID/VID when we are in fact connecting the wrong device. That also made me think, do we want to write the DID / VID when we connect an AOI to a port and change the setting to compatible device? That seems to be the way profinet does it when we use device specific objects on the ports.
— Reply to this email directly, view it on GitHubhttps://github.com/nickcluteturck/IOLinkAOIs/issues/6#issuecomment-1687069078, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BADMXJDVHI4J7IEGHCZAGFTXWPHILANCNFSM6AAAAAA3USZ5VA. You are receiving this because you authored the thread.Message ID: @.***>
Currently the AOI triggers to update Port Info (VID/DID info) based on a change to Process Data Input Valid bits. This works great for when things get plugged in, but it happens too fast when unplugging the data still exists in the block even though the connection has been severed. Currently have a 1s delay timer that works well, but is a timer the best choice here?