KR970056275A

KR970056275A - How to solve loopback during communication

Info

Publication number: KR970056275A
Application number: KR1019950055215A
Authority: KR
Inventors: 최재홍
Original assignee: 전성원; 현대자동차 주식회사
Priority date: 1995-12-23
Filing date: 1995-12-23
Publication date: 1997-07-31

Abstract

이 발명은 통신중 루프 백(loop back) 현상 해결방법에 관한 것으로서, 리시브 인터럽트를 디세이블하는 제1단계(S21)와; 데이터를 전송하는 제2단계(S22)와; 리시브 버퍼가 풀인지를 판단하여, 풀이 아니면 체크를 계속하는 제3단계(S23); 상기 제3단계(S23)에서 리시브 버퍼가 풀이면, 리시브 버퍼의 내용을 지우는 제4단계(S24)와; 데이터 전송이 모두 완료되었는지를 판단하여, 완료되지 않았으면, 데이터를 전송하는 제2단계(S22)로 돌아가는 제5단계(S25)와; 상기 제5단계(S25)에서 데이터 전송이 모두 완료되었으면, 리시브 인터럽트를 인에이블하는 제6단계(S26)를 포함하여 이루어져서, 데이터 통신중에 발생하는 루프 백 현상을 해결하여 통신 에러없는 안정된 데이터 송수신을 할 수 있게 하는 효과를 가진 통신중 루프 백 현상 해결방법에 관한 것이다.The present invention relates to a method for solving a loop back phenomenon during communication, comprising: a first step (S21) for disabling a receive interrupt; A second step (S22) of transmitting data; Determining whether the receive buffer is full, and performing a check if it is not full (S23); A fourth step (S24) of deleting contents of the receive buffer when the receive buffer is full in the third step (S23); A fifth step S25 of determining whether all data transmissions are completed, and if not, returning to a second step S22 of transmitting data; If the data transfer is completed in the fifth step (S25), and comprises a sixth step (S26) to enable the receive interrupt, to solve the loop back phenomenon occurring during the data communication to perform stable data transmission and reception without communication error The present invention relates to a solution for a loopback phenomenon during communication with an effect of enabling the communication.

Description

How to solve loopback during communication

본 내용은 요부공개 건이므로 전문내용을 수록하지 않았음Since this is an open matter, no full text was included.

제2도는 이 발명의 실시예에 따른, 통신중 루프 백 현상 해결방법을 나타내는 흐름도이다.2 is a flowchart illustrating a loopback phenomenon solution during communication according to an embodiment of the present invention.

Claims

A first step of disabling a receive interrupt; A second step of transmitting data; Determining whether the receive buffer is full, and if not, continuing checking; A fourth step of clearing the contents of the receive buffer if the receive buffer is Perl in the third step; A fifth step of determining whether all data transmissions have been completed, and if not, returning to a second step of transmitting data; And a sixth step of enabling a receive interrupt if all data transfers are completed in the fifth step.

※ Note: The disclosure is based on the initial application.