<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/</id><updated>2020-02-27T16:58:00.821000Z</updated><subtitle>Recent posts to CoDeSys-Licence during developing a RT-PREEMPT application</subtitle><entry><title>CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/?limit=25#b534" rel="alternate"/><published>2020-02-27T16:58:00.821000Z</published><updated>2020-02-27T16:58:00.821000Z</updated><author><name>Albert Saenz</name><uri>https://forge.codesys.com/u/albert-saenz/</uri></author><id>https://forge.codesys.comdef34a644672551cf0d05d23b3f11d6ea92e5acf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Edwin,&lt;br/&gt;
Thanks again for the information.&lt;br/&gt;
Regarding your kind bluetooth's question:&lt;br/&gt;
We have a Windows GUI that initially used RS-232C/RS-422 (only full-duplex. Half-duplex as RS-485 is not enough). But with RPi3 we would like wirelessly control. &lt;br/&gt;
Our RPI-Application is sending continuously its complete status (throughout a C-Structure of around 1 Kbyte refreshed minimum 10 times per second, i.e. 115200 bps) and furthermore the BT channel is used to send programs or backups and so on in both direction at the same time. Of course that the RPi-Application can be easily controlled through the Windows-GUI in all their aspects.&lt;br/&gt;
That is the reason of the "full-duplex" need! &lt;br/&gt;
Note: if we only transmit or we only receive via BT (similar but it is not exactly "half-duplex" as you know), the bluetooth remains in connection all the time and it never hangs.&lt;br/&gt;
Full-duplex with Raspbian 4.9.47 is working without RT performances. When we have achieved 4.9.47-rt37 is when we have obtained the hunging surprise that the problems with the "full-duplex BT" is hanging suddenly very soon.&lt;br/&gt;
Hope I have explained correctly and straight-forwardly.&lt;br/&gt;
BR and TKs&lt;br/&gt;
Albert&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/?limit=25#2304" rel="alternate"/><published>2020-02-27T16:57:59.868000Z</published><updated>2020-02-27T16:57:59.868000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.com7a40050852680aa20d197a3a2920a901f7d290f9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Albert,&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Zitat:&lt;/strong&gt;&lt;br/&gt;
1. USB-dongle can be a 32Gbytes pen-drive or it must be yours?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;yes it must be our runtime stick&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Zitat:&lt;/strong&gt;&lt;br/&gt;
2. Do you know where could we find information with some successfull RT-Raspbian project please? (We have obtained it but we still have problems with the Bluetooth UART mode that it still hung after a sort while).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;hm.. not really I would give this "Emlid" a ry.. not sure if this is still maintained.&lt;br/&gt;
What is connected on bluetooth in your application?&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/?limit=25#943a" rel="alternate"/><published>2020-02-27T16:57:57.248000Z</published><updated>2020-02-27T16:57:57.248000Z</updated><author><name>Albert Saenz</name><uri>https://forge.codesys.com/u/albert-saenz/</uri></author><id>https://forge.codesys.com6eaf9cefe70183ec80e1da2ab168879f83e94a58</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks a lot Edwin.&lt;br/&gt;
So, I undertood that you recommend better, to buy as many licenses as needed in &lt;a class="" href="https://store.codesys.com/codesys-control-for-raspberry-pi-sl.html" rel="nofollow"&gt;https://store.codesys.com/codesys-contr ... pi-sl.html&lt;/a&gt; (in our case just 2 for trials)&lt;/p&gt;
&lt;p&gt;and one only USB-dongle at  &lt;a class="" href="https://store.codesys.com/accessories/c" rel="nofollow"&gt;https://store.codesys.com/accessories/c&lt;/a&gt; ... mpakt.html&lt;br/&gt;
Is it the best way for countinous SD-image re-generation? (Including on it the CoDeSys Control of course)&lt;/p&gt;
&lt;p&gt;2 simple questions more please:&lt;br/&gt;
1. USB-dongle can be a 32Gbytes pen-drive or it must be yours?&lt;br/&gt;
2. Do you know where could we find information with some successfull RT-Raspbian project please? (We have obtained it but we still have problems with the Bluetooth UART mode that it still hung after a sort while).&lt;/p&gt;
&lt;p&gt;Thanking you for your time again, BR&lt;br/&gt;
Albert&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/?limit=25#35fb" rel="alternate"/><published>2020-02-27T16:57:56.304000Z</published><updated>2020-02-27T16:57:56.304000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.comb7be957037f33a02df3d967e6aaa88554b58023a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
yes if you activate the license on the runtime key, (&lt;a class="" href="https://store.codesys.com/accessories/codesys-runtime-key-compakt.html" rel="nofollow"&gt;https://store.codesys.com/accessories/c ... mpakt.html&lt;/a&gt;)&lt;br/&gt;
then it is independet from your sd-installation. (the Pi which has plugged the USB Key is licensed)&lt;br/&gt;
The other option is use the softlicense and when a reinstall is needed just re-activate the CMLicenseNew.WibuCmRaU again.&lt;br/&gt;
Sure 2 Pi's 2 licenses are needed. (You see in the faqs here in the forum where you need to save this license file after activation)&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CoDeSys-Licence during developing a RT-PREEMPT application</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/ed0545cbfa/?limit=25#7561" rel="alternate"/><published>2020-02-27T16:57:53.699000Z</published><updated>2020-02-27T16:57:53.699000Z</updated><author><name>Albert Saenz</name><uri>https://forge.codesys.com/u/albert-saenz/</uri></author><id>https://forge.codesys.com812342e97de904b71a2c79e828462be787d6c72f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In our App, Hard-Real-Time is much more than essential ... it's critical!&lt;br/&gt;
In our case Raspbian 4.4.50-rt47 (both "Jessie" Desktop and Lite) or 4.9.47-rt37 ("Stretch") are not so easy to obtain and many times, when the new RT-SD image has been reached, it hungs! That means to re-start from zero and re-load again CoDeSys-control again and again.&lt;br/&gt;
Furthermore, the required Bluetooth use, makes it even much harder for obtaining the RT images (and when RT is patched, BT has erratic behavior). Our scenario when implementing new perforances is highly frustrating most of the time. But, even so, we persevere in the attempt for its imperative need.&lt;br/&gt;
Nowadays, we must check our RPi3+CODESYS App during much more than 2 hours and CoDeSys-Licence should be implemented but... the question is:&lt;br/&gt;
Could you please teach us how to implement (or re-init) CoDeSys-Licence in our new SD images in the faster way? &lt;br/&gt;
We'll have two RPi3-B for trials, we understand we'd need two licences, isn't it?&lt;br/&gt;
Thanking you in advance for your quick reply, BR&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>