linking and unlinking a pin based on motion-enabled
13 Feb 2024 17:07 #293238
by linuxfan
Replied by linuxfan on topic linking and unlinking a pin based on motion-enabled
This does work as a sample/hold, but it still connects pin limit3.0.in to a signal limit3source. So pin limit3.0.in is not "writable" anymore. I cant set its value in MDI with setp command - and this is my main goal, having it connected to feedback source, and after enable, removing it with a command like unlinkp, which makes pin free to accept value again.
Please Log in or Create an account to join the conversation.
13 Feb 2024 17:27 #293242
by PCW
Replied by PCW on topic linking and unlinking a pin based on motion-enabled
That is a bit tricky because you have 2 states (feedthrough/hold)
plus a load new value function.
You can do the link unlink in a script but not in real time AFAIK
The cleanest implementation might be a specific component
Also it might be possible to use two stacked mux2's, using one mux2
to enter the new value to be latched
plus a load new value function.
You can do the link unlink in a script but not in real time AFAIK
The cleanest implementation might be a specific component
Also it might be possible to use two stacked mux2's, using one mux2
to enter the new value to be latched
Please Log in or Create an account to join the conversation.
Time to create page: 0.136 seconds