<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/</id><updated>2020-02-27T15:57:57.804000Z</updated><subtitle>Recent posts to CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</subtitle><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#e105" rel="alternate"/><published>2020-02-27T15:57:57.804000Z</published><updated>2020-02-27T15:57:57.804000Z</updated><author><name>elconfa</name><uri>https://forge.codesys.com/u/elconfa/</uri></author><id>https://forge.codesys.comf81fe04dc23fa454bee5d7f3d26351c69a29608f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I will wait for the update because after having struggled 2 days to update Raspberry 3 with the new 3.5SP15 runtime that I use for my home automation, I had to go back to the 3.5SP14 version, otherwise nothing worked.&lt;/p&gt;
&lt;p&gt;I thought it was my problem, I tried with Raspberry pi-0W, with raspberry pi3B + but enabling it i2c nothing worked anymore.&lt;/p&gt;
&lt;p&gt;I am happy that an update will be released in the coming weeks.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#20f6" rel="alternate"/><published>2020-02-27T15:57:57.034000Z</published><updated>2020-02-27T15:57:57.034000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.com95179ef087242616e5149a46d670bba23f7e684d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
19th of September is the release date for 3.5SP15Patch1&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#4e6f" rel="alternate"/><published>2020-02-27T15:57:54.791000Z</published><updated>2020-02-27T15:57:54.791000Z</updated><author><name>fixstuff555</name><uri>https://forge.codesys.com/u/fixstuff555/</uri></author><id>https://forge.codesys.comd000b946abb3a650a31883e7d0c85a69cdde0dad</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I see that the patch isn't in the store yet?  Any ETA on this?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#f0d5" rel="alternate"/><published>2020-02-27T15:57:53.909000Z</published><updated>2020-02-27T15:57:53.909000Z</updated><author><name>Anonymous</name><uri>https://forge.codesys.com/u/*anonymous/</uri></author><id>https://forge.codesys.comc7553882619cb83894b857305e85b99bbb2d9416</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;em&gt;Originally created by:&lt;/em&gt; phenixrb&lt;/p&gt;
&lt;p&gt;the patch 3.5.15.10 seems to have solved the problems:&lt;br/&gt;
with runtime package 3.5.15.10 in raspberry&lt;br/&gt;
and codesys control 3.5.15.0 for the device ,3.5.15.10 wasn't in the list.&lt;/p&gt;
&lt;p&gt;with active SPI and I2C services.&lt;br/&gt;
reboot raspberry from the pc: ok&lt;br/&gt;
reboot from raspberry: ok&lt;br/&gt;
PC / PI connection: ok&lt;br/&gt;
webvisu: ok&lt;br/&gt;
no raspberry freezes&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#2fe0" rel="alternate"/><published>2020-02-27T15:57:51.192000Z</published><updated>2020-02-27T15:57:51.192000Z</updated><author><name>Anonymous</name><uri>https://forge.codesys.com/u/*anonymous/</uri></author><id>https://forge.codesys.com5d2146fe1512671230671921b95ad7f8a1359124</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;em&gt;Originally created by:&lt;/em&gt; phenixrb&lt;/p&gt;
&lt;p&gt;hello Edwin,&lt;/p&gt;
&lt;p&gt;I thought I was the only one to be faced with this problem.&lt;br/&gt;
waiting for the fix.&lt;/p&gt;
&lt;p&gt;thanks for the answer,&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#599a" rel="alternate"/><published>2020-02-27T15:57:50.091000Z</published><updated>2020-02-27T15:57:50.091000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.comb6944505d8d31c882fbdc567536b9fd0aac2590b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
all this should be solved hopefully with the release of 3.5SP15Patch1 on September release.&lt;br/&gt;
Will send you a release candidate to check.&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CONFLICT BETWEEN I2C ACTIVE ON PI AND CODESYS V3.5.15.0</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/def4fcaaa4/?limit=25#30fe" rel="alternate"/><published>2020-02-27T15:57:48.964000Z</published><updated>2020-02-27T15:57:48.964000Z</updated><author><name>Anonymous</name><uri>https://forge.codesys.com/u/*anonymous/</uri></author><id>https://forge.codesys.com852e0ff2d4fd00893ccab6e8e3b77b312f0b9967</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;em&gt;Originally created by:&lt;/em&gt; phenixrb&lt;/p&gt;
&lt;p&gt;Hello everyone,&lt;br/&gt;
I noticed problems between the latest version of raspbian and codesys, after an update of raspbian.&lt;/p&gt;
&lt;p&gt;defects found: &lt;br/&gt;
no connection pc / pi.&lt;br/&gt;
no webvisu.&lt;br/&gt;
no raspberry reboot&lt;br/&gt;
and freezes raspberry.&lt;/p&gt;
&lt;p&gt;I think this stems from a conflict between the management of the codesys and rasbian I2C service.&lt;/p&gt;
&lt;p&gt;I did the following tests:&lt;/p&gt;
&lt;p&gt;"The reboot requests are all from the raspberry and not from the codesy interface on PC"&lt;/p&gt;
&lt;p&gt;first test:&lt;br/&gt;
raspbian installed: reboot OK&lt;br/&gt;
then, raspbian update: reboot ok&lt;br/&gt;
then, raspbian upgrade: reboot ok&lt;br/&gt;
then, SSH, VNC, SPI, I2C services active: reboot ok.&lt;br/&gt;
then, installation of runtime codesys: reboot requested, the raspberry turns off but never turns on again.&lt;/p&gt;
&lt;p&gt;second test:&lt;br/&gt;
raspbian installed, update, upgrade, no VNC, SPI, I2C.&lt;br/&gt;
the SSH service is active.&lt;br/&gt;
runtime installation codesys: reboot ok&lt;br/&gt;
installing the codesys license: reboot ok&lt;br/&gt;
start runtime on raspberry: reboot ok&lt;br/&gt;
loading a codesys program into the raspberry: reboot ok&lt;br/&gt;
running the codesys program in the raspberry: reboot ok&lt;br/&gt;
start SPI service in raspberry: reboot ok.&lt;/p&gt;
&lt;p&gt;SPI and I2C active in the raspberry  the start of the codesys program in the raspberry:&lt;br/&gt;
 -no connection between the PC and the raspberry,&lt;br/&gt;
-and reboot the raspberry asked, the raspberry turns off but never turns on again.&lt;/p&gt;
&lt;p&gt;SPI and I2C active in the raspberry  running the codesys program in the raspberry: reboot ok&lt;/p&gt;
&lt;p&gt;third test:&lt;br/&gt;
Starting the raspberry with SPI and I2C services enabled before reboot:&lt;br/&gt;
running request of the codesys program on the raspberry:&lt;br/&gt;
no pc / raspberry connection.&lt;br/&gt;
no webvisu&lt;br/&gt;
and after that, it freezes raspberry.&lt;/p&gt;
&lt;p&gt;fourth test:&lt;br/&gt;
runtime codeys installation&lt;/p&gt;
&lt;p&gt;when the services: SSH, SPI and I2C are active on the raspberry, it is almost impossible to install the codesys runtime.&lt;br/&gt;
and when it's possible after several minutes of waiting,&lt;br/&gt;
the reboots are degraded, as before.&lt;/p&gt;
&lt;p&gt;by enabling only SSH installation is possible.&lt;/p&gt;
&lt;p&gt;that's what I see, I'm not a pro of lines of codes, far from it ....&lt;/p&gt;
&lt;p&gt;if you have some ideas to follow, I'm interested.&lt;br/&gt;
thank you&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>