<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for zhw618</title><link href="https://forge.codesys.com/u/zhw618/activity/" rel="alternate"/><id>https://forge.codesys.com/u/zhw618/activity/</id><updated>2022-07-22T12:17:21.226000Z</updated><subtitle>Recent activity for zhw618</subtitle><entry><title>zhw618 posted a comment on discussion Forge 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/forge/thread/6ceff9d39e/?limit=25#0a86" rel="alternate"/><published>2022-07-22T12:17:21.226000Z</published><updated>2022-07-22T12:17:21.226000Z</updated><author><name>zhw618</name><uri>https://forge.codesys.com/u/zhw618/profile/</uri></author><id>https://forge.codesys.com/forge/talk/forge/thread/6ceff9d39e/?limit=25#0a86</id><summary type="html">I meet the same problems. One project parallel for 2 GPIO pins, and that is NOT working properly. I use Raspberry PI 4B+, and Codesys v3.5.18.2 After hard work, I found the solution to overcome this problem: 1) MUST put every SoftPWM function block in a SEPARATE IEC-task with high priority (priority 0 or 1) 2) MUST set every Iec-task's cyclic interval small enough! for example, 50us. I found if the interval greater than you need frequency, the PWM signal on the GPIO pin is not as it should be. And...</summary></entry></feed>