Re: Timing in Synch Comm.
- From: Joerg <notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Sep 2007 19:56:49 GMT
Vladimir Vassilevsky wrote:
Joerg wrote:
Vladimir Vassilevsky wrote:
Jon Slaughter wrote:
I'm writing a windows app which sends data to the parallel port but because its pre-emptive there can be extreme latency in the timing.
AVR Mega644 is indeed sensitive to the SPI clock irregularities while being programmed.
I believe the OP wasn't talking about SPI. But with SPI you are right.
What else is the PC parallel port can be used for if not for the simulation of the SPI or I2C by bit banging?
Hey, I still print over it. Ok, I have a network printer but also another one here in the office that gets shared by a LPT auto-switch between two PCs. It's quicker to print and I don't have to get off my keester :-)
I keep the 14-year old PC with Win98 exactly for this purpose: it is often the quickest way to get something to work.
Yep, often the old stuff works better than anything that came later. This is also why there are things such as the old Eico tube voltmeter in the lab. That thing remains completely unfazed should a spike come along.
--
Regards, Joerg
http://www.analogconsultants.com
.
- References:
- Timing in Synch Comm.
- From: Jon Slaughter
- Re: Timing in Synch Comm.
- From: Vladimir Vassilevsky
- Re: Timing in Synch Comm.
- From: Joerg
- Re: Timing in Synch Comm.
- From: Vladimir Vassilevsky
- Timing in Synch Comm.
- Prev by Date: Re: Beta degradation quantified?
- Next by Date: Re: Simple spectrum analyzer for pre-compliance
- Previous by thread: Re: Timing in Synch Comm.
- Next by thread: Re: Timing in Synch Comm.
- Index(es):
Relevant Pages
|
