<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for lwalbert</title><link href="https://forge.codesys.com/u/lwalbert/activity/" rel="alternate"/><id>https://forge.codesys.com/u/lwalbert/activity/</id><updated>2022-09-29T13:43:11.990000Z</updated><subtitle>Recent activity for lwalbert</subtitle><entry><title>lwalbert posted a comment on discussion General Discussion</title><link href="https://forge.codesys.com/drv/relay-pi-plate/discussion/general/thread/0e1bf5739b/?limit=25#7ecd" rel="alternate"/><published>2022-09-29T13:43:11.990000Z</published><updated>2022-09-29T13:43:11.990000Z</updated><author><name>lwalbert</name><uri>https://forge.codesys.com/u/lwalbert/profile/</uri></author><id>https://forge.codesys.com/drv/relay-pi-plate/discussion/general/thread/0e1bf5739b/?limit=25#7ecd</id><summary type="html">Hi, I was working on libraries for Pi-Plates in codesys back in 2019 too :) I was struggling with the same issue as you regarding GPIO25. Looks like you cannot access the GPIO25 outside a task eg. changing state within the library for each read/write cycles in a for loop. But I found a workaround: Connecting a optocoupler controlled by CS1 (chip select) to toggle GPIO25 towards Pi-Plate wire. and adjusting SPI communication speed/frequency and delay, I got it working. I decided to update and publish...</summary></entry></feed>