sweetlilmre
Member
(I can't paste any links since they will trigger moderation, so posting again.)
Thanks! I've just ordered the parts on eBay. Hopefully they will arrive soon.Hi inagy! I spoke to you via the comments on my YouTube video. I look forward to seeing your Tapuino built and working!
Awesome news!
I think you are right. On c64tapes (dot) org wiki you can read the following in the analyzing_loaders article:I seem to remember reading somewhere that wiring the output from a datasette to the input of another wouldn't work without inverting, although I may be wrong!
NOTE about the Hardware: a thing to point out is that during a SAVE operation, on the WRITE line of the Datasette port, “pulse length” is intended as the time distance between two consecutive low-high transitions. During a LOAD operation, pulse length is the time distance between two consecutive high-low transitions, since the 6526 READ line triggers on negative edges. In other words, the signal from C2N to C64 is the negative version of the one from C64 to C2N. That's why tape duplication hardware consists in an inverter (with a bjt and 2 resistors used in a common emitter scheme): the signal from the C2N performing LOAD, intended for being sent to C64, needs being inverted before being sent to the C2N doing the SAVE operation.
Ah that would explain the circuit in the picture, I was wondering what the transistor was for.
It would also be a cool idea to add the ability to read cassettes into tap files directly on the tapuino, although at this point we may be asking too much from the little Atmega chip lol
Saving from the C64's RAM to the SD card already works. I don't see why it would not work when the deck sends the signal not the C64. It's the same thing if we consider the protocol, it's just a different source.
Yes this would definately be possible. I think that building an adapater from vero board and a Datasette connector might work, the track size looks like it might fit.
Then we would be in business.
As far as the code goes I've got the repeat functionality in but that has caused some other unexpected changes that I have to work through in the display code.
I'm going to change all the timing based stuff to use the new system timer that is in and that should fix the issues.