Return-Path: Delivered-To: craig@sbc-85.com Received: from gator4254.hostgator.com by gator4254.hostgator.com with LMTP id EFVEJCjvu2b9RwwAcizydQ (envelope-from ) for ; Tue, 13 Aug 2024 18:41:28 -0500 Return-path: Envelope-to: craig@sbc-85.com Delivery-date: Tue, 13 Aug 2024 18:41:28 -0500 Received: from p-impout004aa.msg.pkvw.co.charter.net ([47.43.26.135]:33749 helo=p-impout004.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 1se18q-003Rwm-0W for craig@sbc-85.com; Tue, 13 Aug 2024 18:41:28 -0500 Received: from GeorgeAdams ([74.131.139.95]) by cmsmtp with ESMTPA id e18esWwt93EPte18eskgfY; Tue, 13 Aug 2024 23:41:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cinci.rr.com; s=c20240129; t=1723592477; bh=Yd68NPEy/Zjfx0s0cYTWpbVtXc9BzAVjJ3AEKwRgNz0=; h=From:To:References:In-Reply-To:Subject:Date; b=o1llCk05AbBHzjHBO3Bey8Lnt0tgEeLILgzNqhBKy5VeubWcih5Pn6zvUOeoAc+FI 5DjaQjVKlTJEMKIrpMjbuTRxMiI1+S32qZlw9yQQ2J+ssRE4Ev9ujk48LLFTPOE3Jc Ua//OaajpM4316Pe8hXext3jqfVNEUp4/zPJaOZXW6cfRSV9Sw0ZGEMQ6JkcCZeHmY /DPwVWWXzSeiKVIqjdjhl/s/I5H+eN1V7TbqbtJotTxC77/xmWPK/+OnWckAENk0fl DmKO9TasxUIuzD2Fr1aOZ9bRKgEYin4zur+oW93v+HtLQDAFC7Iu51iflEPUmfUVmC VytmAeul9EzYw== X-Authority-Analysis: v=2.4 cv=OKQh3zaB c=1 sm=1 tr=0 ts=66bbef1d a=hl8TJCE9z2sxp+2MqBjxnA==:117 a=hl8TJCE9z2sxp+2MqBjxnA==:17 a=DAwyPP_o2Byb1YXLmDAA:9 a=HjitWDSJAAAA:8 a=ayC55rCoAAAA:8 a=_6GpL_ENAAAA:8 a=0Ljr-g5-bLXMg9Abc8MA:9 a=QEXdDO2ut3YA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=4d2D4LtiAAAA:8 a=WV7S0afn1iRKiOUlOKUA:9 a=Q7F_4NcDyq0q_R2s:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=lqcHg5cX4UMA:10 a=IB1QFG2aBfq3amWdyr0s:22 a=hJnrvW8ITIrk0Oi8sSDQ:22 From: To: "'SBC-85'" References: <000001daed23$62c09f00$2841dd00$@cinci.rr.com> <5209BAA1-9E66-4716-B4D8-74439C17A39F@sbc-85.com> In-Reply-To: <5209BAA1-9E66-4716-B4D8-74439C17A39F@sbc-85.com> Subject: RE: Serial dongle code (2708-27256 version) Date: Tue, 13 Aug 2024 19:41:15 -0400 Message-ID: <000c01daedda$4a905f80$dfb11e80$@cinci.rr.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01DAEDB8.C37FF800" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIfRzP/y5L7CXAUjo/7Y9tj52RJYQJUisTPsYp/BxA= Content-Language: en-us X-Antivirus: Avast (VPS 240813-6, 8/13/2024), Outbound message X-Antivirus-Status: Clean X-CMAE-Envelope: MS4xfK4qbPahZiBqeosEVBANYuRbRW5xEaMk6ACkcBALKyhv3Bc7I69dw2wLDRnrxMy/AXXBs34S8FNmBZqIc2ZI84XkKc5+lDZXpfpqNNYOUqUjoZv1Cd33 BcfRRD7jbxDRwxgIgLcTBB9P+VyLEnCmanh6pLTWoJWC3+XplGA0t54vuOp2s7D+zeTy4DQMKFl+cA== 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_000D_01DAEDB8.C37FF800 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Craig, I managed to work thru the code issue and found that the macro I have in th= e CI routine was coded incorrectly. It was causing the transmit line to tog= gle in the middle of the character input bit loop. (SOAH used for read at t= he start, then mistakenly using SOAL in the bit_loop section, causing the p= roblem.) Code works as designed with no delay between the CI and CO routines at 2400= baud. I used the code in the 2k prom serial adapter manual as a starting point, a= nd made changes as required to deal with the stop bits. Thanks for your suggestions on what to try/test. Regards, George From: SBC-85 Sent: Monday, August 12, 2024 10:48 PM To: adamsgl@cinci.rr.com Subject: Re: Serial dongle code (2708-27256 version) Hi George I will look for this code and send it to you. I thought I had code include= d or at least snippets in the manual but maybe that was something else. Do you have a hearty delay between characters? Maybe the stop bit and start= bit are too close for the terminal to delimit. Or as you suggest, maybe y= ou are inadvertently leaving the line asserted between characters when doin= g a CO. When doing CI, you should always be reading from the address that = leaves the line idle. If you do not have a logic analyzer, send one character and halt. Then meas= ure the line with a scope or voltmeter to confirm it is idle. Read one character and make sure the output is not toggling at all and is a= lways idle. If I don=E2=80=99t send the code, please remind me. Regards Craig On Aug 12, 2024, at 6:52=E2=80=AFPM, adamsgl@cinci.rr.com wrote: =EF=BB=BF 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, i= t 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 tha= t the CI routine I have written is the cause, but it works as designed and = reads the correct character from the dongle. It doesn=E2=80=99t seem to pla= y 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 err= ors. I think this is due to my choices of high/low, idle/mark but have not had m= uch 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 Virus-free. www.avast.com -- This email has been checked for viruses by Avast antivirus software. www.avast.com ------=_NextPart_000_000D_01DAEDB8.C37FF800 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Craig,

 

I managed to = work thru the code issue and found that the macro I have in the CI = routine was coded incorrectly. It was causing the transmit line to = toggle in the middle of the character input bit loop. (SOAH used for = read at the start, then mistakenly using SOAL in the bit_loop section, = causing the problem.)

Code works as = designed with no delay between the CI and CO routines at 2400 = baud.

 

I used the code in the 2k prom serial adapter manual = as a starting point, and made changes as required to deal with the stop = bits.

 

Thanks for your suggestions on what to = try/test.

 

Regards,

 

George

 

 

From: SBC-85 = <craig@sbc-85.com>
Sent: Monday, August 12, 2024 10:48 = PM
To: adamsgl@cinci.rr.com
Subject: Re: Serial = dongle code (2708-27256 version)

 

Hi = George

 

I = will look for this code and send it to you.  I thought I had code = included or at least snippets in the manual but maybe that was something = else.

 

Do you have a hearty delay between characters? Maybe = the stop bit and start bit are too close for the terminal to delimit. =  Or as you suggest, maybe you are inadvertently leaving the line = asserted between characters when doing a CO.  When doing CI, you = should always be reading from the address that leaves the line = idle.

 

If you do not have a logic analyzer, send one = character and halt. Then measure the line with a scope or voltmeter to = confirm it is idle.

Read = one character and make sure the output is not toggling at all and is = always idle.

 

If I don=E2=80=99t send the code, please remind = me.

 

Regards

Craig

 

On Aug 12, 2024, at 6:52=E2=80=AFPM, adamsgl@cinci.rr.com = wrote:

=EF=BB=BF

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=E2=80=99t 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

 

V= irus-free.www.avast.com

 

------=_NextPart_000_000D_01DAEDB8.C37FF800--