RE: Extra unexplainable delay

From: Baltissen, GJPAA (Ruud) (ruud.baltissen_at_abp.nl)
Date: 2004-07-16 15:50:46

Hallo Nick,


> minimum "time between bytes" (tbb) which needs to be  maintained. Are you
> meeting this spec with the delay and not without?

The IEC-part of my program [1] indeed waits 100 uS before sending a byte.
But this delay is performed EVERYTIME before sending a byte. In my case this
1 ms. delay is only needed between receiving the $69 command end sending the
first data byte. And then ONLY  for the SECOND (never performed more yet)
IMPUT# command, not the first !!!

FYI: the rest of the data is sent without any extra delay between each byte:
read, send, errorcheck, read, send etc.

[1] the idea is that when the IEEE part works well, I want to use it for IEC
as well. IMHO the only difference between a 2031 and a 1541 is the way the
data is sent, not how it is handeled.


--
    ___
   / __|__
  / /  |_/     Groetjes, Ruud
  \ \__|_\
   \___|       URL: Ruud.C64.org



 



=====DISCLAIMER=================================================================

De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor daarbij overgebrachte virussen.

The information contained in this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail; please delete in this case the e-mail and do not disclose its contents to any person. We don't accept liability for any errors, omissions, delays of receipt or viruses in the contents of this message which arise as a result of e-mail transmission.
       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.