https://forge.codesys.com/forge/talk/Runtime/2026-10-16T22:59:44.320000ZRecent posts to Runtime 🇬🇧2026-10-16T22:59:44.320000Z2026-10-16T22:59:44.320000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com3eeb109524bcb62f4a3d064ee83a2d8bc9f6beb5

<div class="markdown_content"><p>sorry, yes stars needed</p></div>

2026-10-15T21:00:19.665000Z2026-10-15T21:00:19.665000Zwollviehhttps://forge.codesys.com/u/wollvieh/https://forge.codesys.comb639de8ce4601f08031b835e739faf2ef34bc4b4

<div class="markdown_content"><p>... the stars needed?</p> <div class="codehilite"><pre><span></span><code><span class="k">[CmpCharDevice]</span> <span class="na">PermittedPath.0</span><span class="o">=</span><span class="s">/dev/i2c*</span> <span class="na">PermittedPath.1</span><span class="o">=</span><span class="s">/dev/spidev0.0</span> <span class="na">PermittedPath.2</span><span class="o">=</span><span class="s">/sys/class/gpio/*</span> <span class="na">PermittedPath.3</span><span class="o">=</span><span class="s">/dev/gpiochip*</span> </code></pre></div> </div>

2026-10-15T20:06:08.449000Z2026-10-15T20:06:08.449000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com0d3417608a08a11660f05de2115529b334bce4b1

<div class="markdown_content"><p>CODESYSControl_User.cfg <br/> <span>[CmpCharDevice]</span><br/> PermittedPath.0=/dev/i2c<br/> PermittedPath.1=/dev/spidev<br/> PermittedPath.2=/sys/class/gpio/<br/> PermittedPath.3=/dev/gpiochipPerm</p></div>

2026-10-15T18:15:36.326000Z2026-10-15T18:15:36.326000Zwollviehhttps://forge.codesys.com/u/wollvieh/https://forge.codesys.com3a6a6e2082ed553778f4c45f82cc7c432dce9a9a

<div class="markdown_content"><p>Hi together, </p> <p>-&gt; I updated my raspberry pi3 with runtime 4.22.0.0, and then no I2C device is running.<br/> -&gt; when i switch back to runtime 4.20.0.0 all I2C devices running.</p> <p>what have i additionally to do, so that I2C Bus is although running in the newest Runtime Version 4.22.0.0 ?</p> <p>I did read something about security changes on the new runtime Version, but i do not clear<br/> understand, what i have do do, do bring the I2C Bus to live again ?</p> <p>... there should be a Dialog in the Runtime Deploy tool, (see the link below) , but im my <br/> Codesys Version 3.5.22.40 i could not find this "Change Service User button" ...</p> <p><a href="https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html" rel="nofollow">https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html</a></p> <p>strange things happen, so what to do, any Ideas appreciated !</p></div>

2026-10-07T06:22:54.841000Z2026-10-07T06:22:54.841000Zpernockhamhttps://forge.codesys.com/u/pernockham/https://forge.codesys.comab8efc89623f245c21d56a47072e39bc3dbbfe5b

<div class="markdown_content"><p>Solved finally, in short by:</p> <p>listening to eventId = EVT_CmpMgr_LicenseState, make a callback, extract the event-parameter which contains the RUNTIME_LICENSE_STATE. </p> <p>This gives me the license state as LICENSED / LICENSED_LOS / DEMOMODE etc. </p> <p>What Im not certain of at this point is this the aggregation of all three licenses or just the RUNTIME? Ie, what if my CONTROL-license is ok but my Visu-license is to low, will that set LICENSE_LOST, or would I need other listeners to find out if my VISU will shut down? </p></div>

2026-10-06T18:27:19.072000Z2026-10-06T18:27:19.072000Zpernockhamhttps://forge.codesys.com/u/pernockham/https://forge.codesys.com692696919c73e1781c14644fe483cf5bf9cb094f

<div class="markdown_content"><p>Third update. I figured that even knowing the level of the license, it will not tell me if its level is enough for the current application. There must be some other way to find this out?</p> <p>I see a component CM write in the Log if starting without license-dongle. "License lost - time left.. "</p> <p>Can I access this CM to check status from inside the application?</p> <p>This function is essential, why is it so hard to find info about implementation?</p></div>

2026-10-06T17:28:47.205000Z2026-10-06T17:28:47.205000Zpernockhamhttps://forge.codesys.com/u/pernockham/https://forge.codesys.comfa1d7b0b133b422b002722b0bf50dd7a4cb6c333

<div class="markdown_content"><p>I think google has fooled me here, the only thing I can conclude so far is what i now from reading the licenseManager, which tells me that my valid license have the following product-code</p> <p>CONTROL - 16#3000<br/> VISU - 16#3003, feature map: 1000<br/> COM - 16#3004, feature map: 0200</p> <p>Will different level of license give different product codes or will I see the active license level by other means? </p> <p>What I am trying to achieve is block Starting a machine with time limited operation should the application be larger than what the license permits. And give this information to the user by an alarm/information.</p></div>

2026-10-06T16:35:30.272000Z2026-10-06T16:35:30.272000Zpernockhamhttps://forge.codesys.com/u/pernockham/https://forge.codesys.com842b73f888c7d990af804933d5e689510666f0c7

<div class="markdown_content"><p>Im trying to read out active license by CmpCodeMeter but am not sure of the combination of ProductCode and FeatureMap that each of CONTROL, VISU and COM / SMALL, MEDIUM, LARGE equals. </p> <p>Started by trying CodeMGetContentByFirmcode expecting error 18 / Not Available if asking for a higher level of license compared to what I know is active, but function just returned the requested productcode and a featuremap </p> <p>Is this the way or is it better to use CodeMOpen? Which seems to also require a featureCode. Where can I find info on required featureCode?</p> <p>ProductCodes according to google:<br/> Control (PLC Runtime) <br/> Small (S) 16#00002FFF 12287<br/> * Medium (M) 16#00003000 12288<br/> Large (L) 16#00003001 12289<br/> Visualization (WebVisu) <br/> Small (S) 16#00003002 12290<br/> Medium (M) 16#00003010 12304<br/> * Large (L) 16#00003003 12291<br/> Communication (Com) <br/> * Small (S) 16#00003004 12292<br/> Medium (M) 16#00003005 12293<br/> Large (L) 16#00003006 12294</p> <p>Thanks!</p></div>

2026-09-07T06:43:39.823000Z2026-09-07T06:43:39.823000Zmariussanduhttps://forge.codesys.com/u/mariussandu/https://forge.codesys.com2d33006c7c61875887ebe1cd180fa18bfd743485

<div class="markdown_content"><p>I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30.<br/> Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.</p></div>

2026-09-07T06:43:36.943000Z2026-09-07T06:43:36.943000Zmariussanduhttps://forge.codesys.com/u/mariussandu/https://forge.codesys.coma33fb3b513708c76497d810ed69958736cef8bc3

<div class="markdown_content"><p>I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30.<br/> Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.</p></div>