Reply to thread

Message

<blockquote data-quote="Lightning303" data-source="post: 1083762" data-attributes="member: 97876">Thanks, will have a look at it.Yeah, but AtmoWin is the nearest point to the problem. Maybe it is possible to fix this problem directly? Im guessing AtmoWin does not close the COM port connection when it goes to sleep/hibernate, and does not make a new one on resume, but just keeps the connection. And this then results in problems. Wouldnt it be possible to &quot;simply&quot; close the com port connection on sleep/hibernate and reestablish it on resume? Again im just guessing. If this is not possible, then yeah the best solution i think would be to integrate your work into AtmoWin, so it can restart the com port after a resume.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue&nbsp; &nbsp; :p" loading="lazy" data-shortname=":p" /></blockquote>

[QUOTE="Lightning303, post: 1083762, member: 97876"] Thanks, will have a look at it. Yeah, but AtmoWin is the nearest point to the problem. Maybe it is possible to fix this problem directly? Im guessing AtmoWin does not close the COM port connection when it goes to sleep/hibernate, and does not make a new one on resume, but just keeps the connection. And this then results in problems. Wouldnt it be possible to "simply" close the com port connection on sleep/hibernate and reestablish it on resume? Again im just guessing. If this is not possible, then yeah the best solution i think would be to integrate your work into AtmoWin, so it can restart the com port after a resume. :P [/QUOTE]

Verification