Return-Path: Delivered-To: craig@sbc-85.com Received: from gator4254.hostgator.com by gator4254.hostgator.com with LMTP id 8PcBJUy8umYh6AoAcizydQ (envelope-from ) for ; Mon, 12 Aug 2024 20:52:12 -0500 Return-path: Envelope-to: craig@sbc-85.com Delivery-date: Mon, 12 Aug 2024 20:52:12 -0500 Received: from p-impout003aa.msg.pkvw.co.charter.net ([47.43.26.134]:47575 helo=p-impout003.msg.pkvw.co.charter.net) by gator4254.hostgator.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1sdghn-0032fQ-0k for craig@sbc-85.com; Mon, 12 Aug 2024 20:52:12 -0500 Received: from GeorgeAdams ([74.131.139.95]) by cmsmtp with ESMTPA id dghYs8PybQBe7dghaskcwV; Tue, 13 Aug 2024 01:51:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cinci.rr.com; s=c20240129; t=1723513920; bh=W0ddvwZXCk+iKG9frcvUYMHrKTj9jtbJFMWU0Ikq4Hw=; h=From:To:Subject:Date; b=ZtRFtkvhsto8AAf55sSiuZcjjULu7ZWaifxbzF38pAj5JQjbLNorQQS3SdCGcaBMU ISFeJcanibQKqtXEnkW5f95/NjfshQi4bIQ3NqBwYZsuyZQamuV/uGjd0x2oNzg1pt nL6sSIGl5XJjEAP6CiLLQRFoEmJ4KsSTW5KCLFxUW2SHIZ9eWYDjPVWiTzw9Do15EQ MUo3iBJvTm0eCyrJ4JuduazWf1Phi4Xrl/ZJzbyVOGm3W8qxdZqG0E8J4SZXr+PYha OP7CNCVgt3m4vacD6aQhbg7gjXZQjoN85/pnXYOCKrX7OjA4bwC7HbvdBBocSHESJN aycZxbvWOmM3Q== X-Authority-Analysis: v=2.4 cv=N4IvFX9B c=1 sm=1 tr=0 ts=66babc3f a=hl8TJCE9z2sxp+2MqBjxnA==:117 a=hl8TJCE9z2sxp+2MqBjxnA==:17 a=DAwyPP_o2Byb1YXLmDAA:9 a=_6GpL_ENAAAA:8 a=pjFtwf3W2yp5tMuggdoA:9 a=CjuIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=4d2D4LtiAAAA:8 a=23oC-oOBhePJ88On164A:9 a=TKyIJXf-d0-ZzPso:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=lqcHg5cX4UMA:10 a=hJnrvW8ITIrk0Oi8sSDQ:22 From: To: "'SBC-85'" Subject: Serial dongle code (2708-27256 version) Date: Mon, 12 Aug 2024 21:51:56 -0400 Message-ID: <000001daed23$62c09f00$2841dd00$@cinci.rr.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01DAED01.DBAF4D20" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdrtIrw8LecIdpbJQZ20VYGLg/CRVg== Content-Language: en-us X-Antivirus: Avast (VPS 240812-14, 8/12/2024), Outbound message X-Antivirus-Status: Clean X-CMAE-Envelope: MS4xfNyiXGgCr7P20xY5AUQcmcChxY24x/RAgF3X8NJ/kB8DfNCg5eR3S8jZmieV2JhHh3bPvRV41108Rj4lHWu9lGnoIhRLYaCUKT7VYkBM/fFqPq4k5XGg KZQucIHUfq8kmdGOtsuPmumGulH/rhzIE0bQlCtHRW9psGaPWciPVx6w+ta15RvWliMFM2AhyzZHFw== X-Spam-Status: No, score=-4.3 X-Spam-Score: -42 X-Spam-Bar: ---- X-Spam-Flag: NO This is a multipart message in MIME format. ------=_NextPart_000_0001_01DAED01.DBAF4D20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Craig, I finally got around to the 2708-27256 project and am having an issue with the code I have developed. When the dongle is only sending data to RS232, it works with no issues. When I read a character from the dongle, and try to write it back, I causes framing errors on the other end. I figured out that the CI routine I have written is the cause, but it works as designed and reads the correct character from the dongle. It doesn't seem to play well with the CO routine. The stop bit seems to be the issue. The code is written to read a character, write the character and loop over and over. The looping and calling the CI routine is causing the framing errors. I think this is due to my choices of high/low, idle/mark but have not had much success with changing these without breaking the code. Any chance you could share the code you show in you show in your video #114 so I can see your method of reading and writing to the dongle? Any help would be appreciated. Regards, George -- This email has been checked for viruses by Avast antivirus software. www.avast.com ------=_NextPart_000_0001_01DAED01.DBAF4D20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Craig,

= ;

I finally got around to the 2708-27256 proj= ect and am having an issue with the code I have developed. When the dongle = is only sending data to RS232, it works with no issues. When I read a chara= cter from the dongle, and try to write it back, I causes framing errors on = the other end. I figured out that the CI routine I have written is the caus= e, but it works as designed and reads the correct character from the dongle= =2E It doesn’t seem to play well with the CO routine. The stop bit se= ems to be the issue.

The code is written to read a character, write the c= haracter and loop over and over. The looping and calling the CI routine is = causing the framing errors.

<= /o:p>

I think this is due to my choices of high/low= , idle/mark but have not had much success with changing these without break= ing the code.

Any chance you could share the code you show in you show in= your video #114 so I can see your method of reading and writing to the don= gle?

Any help would be appreciated.

Regards,

George

Virus-free.www.avast.com

------=_NextPart_000_0001_01DAED01.DBAF4D20--