0 Members and 2 Guests are viewing this topic.
I don't belive you can store to <theta> with Axe. At least, I couldn't do it in version 0.1.2.
Well, you can only send two bits at a time, and you don't have to recieve at the right second, either.Although, I'm not a guru on linking. I know that the ports on each calc mimic each other, so it might be a good idea to assign a random bit, high or low, to each calculator, in which case you can only send one bit at a time.
Quote from: SirCmpwn on April 07, 2010, 09:57:02 pmWell, you can only send two bits at a time, and you don't have to recieve at the right second, either.Although, I'm not a guru on linking. I know that the ports on each calc mimic each other, so it might be a good idea to assign a random bit, high or low, to each calculator, in which case you can only send one bit at a time.Well, there are two link lines, but only one bit can be sent at once. The sending calculator pulls either line A or line B low, depending on the value of the bit being sent. The receiving calculator acknowledges by pulling the other line low. Then the sending calc lets its line up, and the receiving calc lets its line up.
I was reading about linking, and would it be faster to have one line be a clock, and then the other line be the bit to be sent? When the receiving calc detects a change in the clock line, it inputs the bit line into memory. Seems like it would be faster? I'm just theorizing tho
Quote from: Builderboy on April 07, 2010, 10:14:56 pmI was reading about linking, and would it be faster to have one line be a clock, and then the other line be the bit to be sent? When the receiving calc detects a change in the clock line, it inputs the bit line into memory. Seems like it would be faster? I'm just theorizing tho The problem here is that bits may be skipped. Not good