<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text -->
<style>.EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; }</style></head>
<body>
<font size="2"><div class="PlainText">On Friday, 1 May 2026 2:51 am, quoth Moebius, Volker:<br>
> When is the master using this AL Control register? - I assume that an<br>
> implementation of an `id_request` feature would require to synchronize the<br>
> necessary register accesses (0x120, 0x130, 0x134) with those executed by the<br>
> master for other reasons, wouldn't it? Could you give me a hint in which source<br>
> code module the AL Control register is possibly managed?<br>
<br>
It's managed in fsm_slave_config, and used whenever the slave needs to transition AL states. When the slave is in a stable state (PREOP with the app not started, or OP with it running) then there's not much activity with these registers, but they do get polled periodically so that the master can detect unexpected slave state changes.<br>
<br>
> Is there a mechanism to "lock" the accesses to the AL Control register by the<br>
> public API of the EC master?<br>
<br>
There is not. I *think* it should be relatively safe to perform register requests while the master is idle (and the slave is in PREOP); it probably makes the most sense to detect the switch id and then explicitly rewrite into the station alias before communication starts. One caveat is that spontaneous slave reboots during OP phase may be more problematic to recover from without proper support in the master code. You can use the ioctl API from a master app if needed, though it's not the preferred option where proper APIs are available instead.<br>
<br>
</div></font>
<span style="FONT-FAMILY: Gotham, Calibri, 'sans-serif'; COLOR: #231f20"><strong>Gavin Lambert<br></strong>
<br>
Software Engineer<br>
<br>
</span><br>
<br><img style="HEIGHT: 45px; WIDTH: 192px" src="cid:TOMRA_CMYK_final_size_times_two_cd761a01-1d1f-446e-9316-8012271820b6.png" width="192" height="45" border="0">
<br>
<a href="https://www.facebook.com/TOMRA.Food/" target="_blank"><img alt="tomra facebook" src="cid:TF-FB-icon_b77c57e4-4990-4f9d-b3a2-8e6ab45df7f2.jpg" height="30"></a> <a href="https://www.linkedin.com/company/tomra-food/" target="_blank"><img alt="tomra linkedin" src="cid:TF-LinkedIn-icon_d54c4829-dcb9-450c-9187-34b26e85ebaa.jpg" height="30"></a> <a href="https://twitter.com/TOMRAFood" target="_blank"><img alt="tomra twitter" src="cid:icons-social-media-twitter_small_2_4bae5ad2-4add-4314-a352-5b317f784956.jpg" height="30"></a> <a href="https://www.youtube.com/playlist?list=PLDD3B1A7BAE919EC6" target="_blank"><img alt="tomra youtube" src="cid:TF-Youtube-icon_8b2c830c-70d9-48da-a4db-db9191d346ba.jpg" height="30"></a> <a href="https://www.instagram.com/tomrafood/" target="_blank"><img alt="tomra instragram" src="cid:TOMRAinstagram_45b30c55-490a-4f32-8fd3-998c152e3494.jpg" height="30"></a><br>
<span style="FONT-SIZE: 75%; FONT-FAMILY: Calibri, Candara, Segoe, Optima, Arial, sans-serif; COLOR: #6e8186"> <b>TOMRA Food (ANZ) Limited</b>
| 42 Vestey Drive | PO Box 13 516 | Mt Wellington 1060 | New Zealand </span><br>
<p style="FONT-SIZE: 10pt; MARGIN-BOTTOM: 5pt; FONT-FAMILY: Arial; MARGIN-TOP: 0px"></p>
<span style="FONT-SIZE: 75%; FONT-FAMILY: Calibri, Candara, Segoe, Optima, Arial, sans-serif; COLOR: #6e8186"> Phone: +64 96 34 00 88 | <a href="https://www.tomra.com/food">https://www.tomra.com/food</a></span><br>
<span style="FONT-SIZE: 60%; FONT-FAMILY: Gotham, Calibri, 'sans-serif'; COLOR: #6e8186">The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication. </span><br>
<span style="FONT-SIZE: 60%; FONT-FAMILY: Gotham, Calibri, 'sans-serif'; WIDTH: 75%; COLOR: #6e8186">
</span></body>
</html>