<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[comport] lost connection retry failing]]></title><description><![CDATA[<p>Hi, I'm working on a Pd patch that connects to a few sensors via SLIP serial OSC. The serial implementation is based on this example : <a href="https://github.com/CNMAT/OSC/tree/master/Applications/PD" rel="nofollow">https://github.com/CNMAT/OSC/tree/master/Applications/PD</a></p>
<p>Everything works wonders and is really stable; however I run into an issue when a serial connection is lost, for instance when we I reset one of the sensors for calibration purposes. The patch is running headless on a RPI4 and the idea is &quot;never&quot; have to ssh in order to reload the Pd as this is running on a permanent sound installation.</p>
<p>I have created bind USB address on linux using the deviceID and vendorID of my sensors therefore naming on /dev/ is static (/dev/sensor_1, /dev/sensor_2, etc ...). I have also specified a large amount of retries on the [comport] object to allow the sensor to show up /dev/. But when I unplug one of the sensor, I can see [comport] loosing the connection and listing the retries:</p>
<pre><code>error: [comport]: lost connection to port 9999 (/dev/sensor_1), retrying...
errors: retrying 45
</code></pre>
<p>I have also made sure that /dev/sensor_1 is back up on /dev/ while I can see [comport] endlessly trying to connect to it.</p>
<p>I think I'm running out of ideas here ... and would be grateful if someone could give me some pointers on how to either fix this issue; or finding another way around in order to ensure a dropped device will reconnect to my patch.</p>
<p>Thank you</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing</link><generator>RSS for Node</generator><lastBuildDate>Sat, 16 May 2026 18:08:42 GMT</lastBuildDate><atom:link href="http://forum.pdpatchrepo.info/topic/13405.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 16 Apr 2021 00:32:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [comport] lost connection retry failing on Fri, 16 Apr 2021 00:39:22 GMT]]></title><description><![CDATA[<p>Hi, I'm working on a Pd patch that connects to a few sensors via SLIP serial OSC. The serial implementation is based on this example : <a href="https://github.com/CNMAT/OSC/tree/master/Applications/PD" rel="nofollow">https://github.com/CNMAT/OSC/tree/master/Applications/PD</a></p>
<p>Everything works wonders and is really stable; however I run into an issue when a serial connection is lost, for instance when we I reset one of the sensors for calibration purposes. The patch is running headless on a RPI4 and the idea is &quot;never&quot; have to ssh in order to reload the Pd as this is running on a permanent sound installation.</p>
<p>I have created bind USB address on linux using the deviceID and vendorID of my sensors therefore naming on /dev/ is static (/dev/sensor_1, /dev/sensor_2, etc ...). I have also specified a large amount of retries on the [comport] object to allow the sensor to show up /dev/. But when I unplug one of the sensor, I can see [comport] loosing the connection and listing the retries:</p>
<pre><code>error: [comport]: lost connection to port 9999 (/dev/sensor_1), retrying...
errors: retrying 45
</code></pre>
<p>I have also made sure that /dev/sensor_1 is back up on /dev/ while I can see [comport] endlessly trying to connect to it.</p>
<p>I think I'm running out of ideas here ... and would be grateful if someone could give me some pointers on how to either fix this issue; or finding another way around in order to ensure a dropped device will reconnect to my patch.</p>
<p>Thank you</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing</guid><dc:creator><![CDATA[wazounet]]></dc:creator><pubDate>Fri, 16 Apr 2021 00:39:22 GMT</pubDate></item><item><title><![CDATA[Reply to [comport] lost connection retry failing on Fri, 16 Apr 2021 06:30:16 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-a" href="http://forum.pdpatchrepo.info/user/wazounet">@wazounet</a> Pretty sure you will have to route the error message (assuming it arrives on the rightmost outlet of [comport]....?) and when it reaches a set integer (say 45) send comport a [close, open x ( message.<br />
Disconnecting a usb device will break the connection and it will not be automatically &quot;remade&quot; for [comport] because the usb device creates an emulated port and the driver is unloaded on disconnect.  A non-usb port would not suffer from a disconnect as the driver would still be running.<br />
David..</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing/2</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing/2</guid><dc:creator><![CDATA[whale-av]]></dc:creator><pubDate>Fri, 16 Apr 2021 06:30:16 GMT</pubDate></item><item><title><![CDATA[Reply to [comport] lost connection retry failing on Fri, 16 Apr 2021 16:16:56 GMT]]></title><description><![CDATA[<p>Hi David, thank you for your answer and yes this was my worries about the simlink to serial.</p>
<p>I'll be trying your solution this evening, but is there a more elegant way to do this, rather than counting the retries ?</p>
]]></description><link>http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing/3</link><guid isPermaLink="true">http://forum.pdpatchrepo.info/topic/13405/comport-lost-connection-retry-failing/3</guid><dc:creator><![CDATA[wazounet]]></dc:creator><pubDate>Fri, 16 Apr 2021 16:16:56 GMT</pubDate></item></channel></rss>