I was not sure where to post this, but I made a calc-to-calc serial cable!

I ended up finding two sets of headphones with the right size tips (not sure what they are called), so I cut them up with an ample length of wire. I also have a bunch of jumper wires that I got for my Raspberry Pi, so after cutting the headphone wires, I exposed the three sets of wire, used an abrasive to strip off the enameling, and spliced each wire with a female tip of a jumper wire. From there, I can connect them with male-male jumpers and it properly transmits data between my calcs!

The reason that I didn't just splice the two sets of wires together directly is because now I can plug in other items. For example, I connected male leads to an electric motor and LED-- it lets me control them through the link port now! I can also hook them up to a breadboard if I wanted to, making it possible to connect more calculators, or I can directly plug them into the GPIO board on my Raspberry Pi. A few months ago I did this and wrote a Python program and a calc program that could communicate with each other (basically just sending a string in Ans to the Pi, and have it displayed in the terminal).

Unfortunately, I lost the Python program due to a crash, but I still have the calc programmed backed up on calc. My plan is to come up with some working routines from scratch since I am still pretty terrible with figuring out the link port. It took me forever to figure out that the receiving calc can't change the lines.

Yeah, I should solder them as the connection was shaky before I taped them. I was going to, then I never got to it

I think the issue with the link routines and only being able to send one direction at a time is a hardware issue. I've tried changing the lines using the "receiving" calculator and it doesn't work. I think it's that it can't change it from a 0 to a 1 unless it was the calc that set it to 0 (by sending a 1).

I dunno, it was a pain in the butt, but I did find the program I was working on, which is awesome. It can send and receive bytes or packets of data and allows the user to exit the receiving end by pressing Clear if there is no activity (so no infinite loops!). Currently I can just send a string in Ans from one calc to the beginning of RAM, but that is only because I didn't have access to a computer at the time I made it and couldn't remember the _CreateStrng bcall.

My plan is to make a link protocol where a calc can:

-Send a packet of data to be written to predetermined location in RAM
-Send a file to another calc
-Request from the other calc a file
-Request a list of files (for FileSyst, this would allow the other calc to inspect folders in order to make requests for files).
-Request current key presses

Pretty neat stuff Xeda!

Could I use two of these hooked together with a usb female to female adapter?

That would most definetily not work due to how the Silverlink works @Minty !. That being said. Link cables are cheap enough on ebay. If you shop around something to the tune of less then $2usd a piece.

As for @Xeda112358 How did your link shenanigans go? I will honestly suggest looking into CalcNet2.2 by KermM It fits most of your criteria ;P and from personal experience is pretty robust and fast. I do realize that would have been outside of the scope of you making your own to learn though~