??? 06/03/07 20:00 Read: times |
#140213 - Two questions ... Responding to: ???'s previous message |
(1) Why do you wish to transfer data in this way? By that, I mean, "Why must it go via one and only one pin?"
(2) Why on earth would you attempt to do this in Bascom? Have you managed to do it in ASM yet? You do realize that in order to transimit and receive data via a single pin, there must be precise timing and a well-defined protocol. The data must be modulated in a form that is easily recognized and decoded by the receiver. If you use one pin alone, it must present the data in a way that enables the receiver to establish timing synchronization and data framing. An example of this sort of operation is presented in the ETHERNET specification. The data is "Manchester-encoded," which thoroughly entrains timing information in the data, and, with the inclusion of a synchronization header ending in a start-of-frame delimiter (SFD) provides byte framing information as well. Consider how you will handle transmission errors. Consider how you will process the transmitted data frame at the receiver. Consider your bandwidth requirement. Is BASCOM capable of achieving precise timing? Is BASCOM capable of operate at sufficient speed? If you can write the transmit/receive and protocol processing code in ASM and then execute it as a DATA statement, you may be able to do this. RE |
Topic | Author | Date |
data transfer through any port pin | 01/01/70 00:00 | |
Two questions ... | 01/01/70 00:00 | |
Manchester Encoding | 01/01/70 00:00 | |
data transfer through one pin | 01/01/70 00:00 | |
data transfer through any port pin | 01/01/70 00:00 | |
Insufficient Information | 01/01/70 00:00 | |
data transfer through any port pin | 01/01/70 00:00 | |
Normally two pins are needed | 01/01/70 00:00 | |
Not for PWM Methods | 01/01/70 00:00 | |
one only signal pin![]() | 01/01/70 00:00 | |
Does BASCOM have... | 01/01/70 00:00 | |
Looks like... | 01/01/70 00:00 | |
data transfer through any port pin | 01/01/70 00:00 |