How to use the link port

[Xeda112358]

I just modified the source a bit and I just now made a program that exchanges Ans with the other calculator if it is a string o.o I used a few spots of assembly, but it works I am going to see if there is some way to make it terminate after receiving a certain byte ...

On another note, I tested this twice earlier by sending 255 bytes 100 times and the checksum worked every time (this was between TI-84+ and TI-84+SE)

[kindermoumoute]

Ok, I identified the problem : when I try between a 83+fr and another 83+fr, it work perfectly. Then when I try with a 83+ and another 83+.. it work perfectly !
The probleme is when I try a 83+ with a 83+fr. :S
After analyzing 25 times, the 83+fr displayed 190 each time, but on the 83+ I have :

• 18 perfect sends (190)
• 181
• 185
• 187
• 189 (twice)
• And twice I needed to force quit because the other calc had finished : 191

So... we have a problem btw 83+ and 83+fr only. FnOff makes no difference, and I wonder if the "port" command could solve the problem? But I really don't understand how it work...  

PS : few people have 83+ in France...

EDIT : I though it could help to understand the problem : link1, link2.

[Xeda112358]

My friend does not like me at the moment (we got in an argument), so I could not test between the 84+/SE and the 83+ (he has the 83+). Also, I am still trying to work on exchanging two different sized strings.

[Keoni29]

I found these. I dunno if it works like this with axe.

[Keoni29]

Sorry for the doublepost, but I really need help on getting to know how the AXE protocol works! It's for my TI-nterface schoolproject which has to be finished before the presentations this wednesday!

Please help me out

[Runer112]

Sorry if this is difficult to follow, I didn't really know how to structure the diagram (if you want to call it a diagram). If you have any questions, just ask. Otherwise, I hope this helps!

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

SENDER RECEIVER ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ Pull ring low Repeat up to [ARG 2]*8μs If ring is not low, abort  | If tip is low, break from loop Pull tip low If tip is not low, abort Release tip Received byte = 0 LOOP 8 TIMES LOOP 8 TIMES  | Release ring, pull tip low |  | Wait ~21μs | Wait until tip == ring  | Rotate byte to send left |    | If 0 rotated out, pull ring low |    | If 1 rotated out, release tip |  | Wait ~12μs | If tip is low, rotate 0 left into byte  | | If tip is high, rotate 1 left into byte Release tip and ring

[calc84maniac]

Well that's... different. I had no idea Axe used a delay-based method.

[Quigibo]

Well, one line acts as a "clock" and the other is the data bit being sent.  The receiver never sends confirmation other than telling the sender to start and thus is necessarily delay based rather than confirmation based.  This is because it is the fastest way to link and guarantees that neither calculator can freeze from dead-lock, interruption, or interference.  However, I do want to overhaul the entire routine at some point because there are definitely cross-compatibility issues such as with 83+ to 83+fr.

[Torio]

Hello, I don't know if it could be useful for your problem, but I coded this routine a few months ago for a 2-player game.
It works perfectly, and takes 3 parameters :
1) - The adress of the variable to store the byte recieved (°A, for example)
2) - The byte to send
3) - The byte to send after you recieved something

Code: Select All | Copy To Clipboard

1 2 3 4 5 6 7 8 9

Lbl RES -1 -> {r1}r Repeat {r1}r != -1 and ({r1}r != 255) or getkey(15) Send(r2,10) Get->{r1}r End Send(r3,50) Pause 1 Return

For example if you want to send 1, and recieve something in A and then send 2 :

Code: Select All | Copy To Clipboard

1	RES(°A, 1, 2)

I separated the byte you send before you recieve, and after you recieve, but it can be the same, though.
If you have any questions, just ask me.

[kindermoumoute]

Code: Select All | Copy To Clipboard

1	{r1}r != -1 and ({r1}r != 255)

Why do you test {r1}r != 255

[Torio]

Because you certainly know that when you don't recieve something from Get, it will store -1 in the variable, but sometimes it could store 255 !
That was a major problem that made me lose a lot of time, I don't know why you can have 255 after a unsucessful Get.

[kindermoumoute]

I think we get the bug... now quigibo you know what you have to do.

Here a new version, I just add a modulo 256 after all Get+1.
EDIT : don't work...

[Xeda112358]

Doesn't Axe return -1 (65535) if it was unsuccessful? (not 255)

[Torio]

I'm quite sure, that was the source of all my bugs.
Test my routine, and you will see.

[Xeda112358]

Oh, okay, so you mean sometimes it is supposed to return -1, but instead it returns 255?