5-11under

@wolfy62, for you I'll upload a video. All was working great until the MicroSD card went flying out of the spring-loaded socket. InShot_20240307_165918533.mp4

It (the original RTO I sold) failed because a) it took me too long to get started on the first batch, b) it took too long to assemble the batches, c) the PiRTO came out after only two batches were made (probably that's a good thing, though), and d) some expected it to work on every system, even though it was never advertised that way. It did not fail because of lack of a video. A video would only tell someone that one cart worked at one point in time.

Okay, thanks for your concern, then.

Sorry, I don't have too much time for this conversation with you, especially because you seem to be trying to make fun of me. The original RTOs I sold had a disclaimer on the sales site, for the prospective buyer to investigate the product to see if it's right for them. The new PiRTOs I sell will have a stronger disclaimer (because, as already discussed, it's not my design). The original RTOs I made were not half-assed - a lot of time and money was spent in getting it to look good and to work well (within the limitations of the original product/design). Trust me (or don't, I don't care, and it doesn't really matter), there was no profit from the original RTO I sold. I don't blame anyone for that except myself, but I am definitely decreasing my risk for the PiRTO.

Nope. IF it was my design, AND IF I wanted it to go beyond the experimental stage, THEN I would perform testing on more types of Intellivision systems. However, this is not my design. Therefore, I'll only be testing each cartridge I assemble on the systems that I have at home, to ensure the circuitry is connected with no shorts or opens, i.e. matching aotta's schematic. At that point I'll declare that the individual cartridge functions as a PiRTO cartridge. Beyond that, it will be buyer beware - it's an experimental device that may or may not work on all systems. This will all be made clear on the eventual sales page. The risks will be known, and people can make their decision based on that. There are of course other options, including making your own PiRTO, or buying a BackBit Pro.

It's a PiRTO. I'll be advertising it as experimental.

Thanks. You can open the shell, reprogram the board with PAL or NTSC versions as per your github site, and screw the shell back together again. For some stupid reason, I also tried a cheap Chinese Pico (a USB-C version), and it didn't work.

I'm making a batch of these for anyone who wants to try this out without having to make one themselves. I made a new board layout so it fits inside an injection molded case, and added a light pipe to see the status LED (it's near the middle of the television on the label). The schematic, though, is the aotta design.

I'm not running any PAL consoles. I do see, though, that aotta has uploaded several different compiled speed options that you could try.

These batch is ready to be shipped to me, so they should arrive in a week or two.

Thanks Oscar! There's not much missing compared to IntyBASIC anymore.

I'm transitioning to aotta's Pi version. I still need to do more testing, especially for the Model 1.

The reply is on the bottom of the page.

Awesome! Thanks Oscar!

I am definitely looking forward to this!

What's the sequence of events at boot-up? I've built one, but it's not working yet. Without the code, I'm running blind on this. What should be happening to the LED and on the screen and to the reset line? Also, when there's no microSD card installed, I get the 4 LED blinks with 2 second pause between cycles. Should anything be on the screen at that point, or not?

Update: the supplier got back to me with a completion date for new LCDs... March 15. I'm assuming I'll have them in hand a week and a half later, approximately. Add a few days for testing, so these should be in my store by the end of March.

Is there any advantage to starting with just the multiplication, and saving the division by 16 until the very end?

Based on the circumstances, send it when you can, then, and then we can be done with this.

Update to the above. Offer good until February 29 for North American orders (longer for the more recent out-of-NA orders). I'll respond within 24 hours for any requests. Have package postmarked on or before that date. @Crash7, I know you wanted to send it out in 3 weeks, but I think the end of this month is fair. If you don't want it, there's no reason to wait 3 weeks.

On the sales page at my store, I wrote the disclaimer "Before purchasing, please investigate exactly what the RTO Flash Multicart is, as well as my revisions from aotta's work". I did make some modifications to aotta's design, because I didn't like the small screen, and the reset circuitry wasn't working for me (his newer versions match mine, it looks like). I also added the "delays.txt" file capability, so if people needed to, they could adjust the timing settings without having to upload new firmware to the Teensy inside. Beyond that, however, the main part of the design is not mine. That's why I wrote the first part of the disclaimer. There were no secrets that there could be issues with some consoles. I have not tried to be flippant in any response, except for the "I did say" to you (but only because I deemed your comment to be in poor taste). The fact is, I don't know the correct timing settings for all the systems. I know the default works for the 3 systems I have here. I don't know whether the values should be increased or decreased, or exactly what the values mean. If anyone has one that doesn't work for them, send me a PM, and you can return the item back to me, all in good physical condition. I'll refund the product price.

The new version should be more readily available because it's easier to build. That's the plan. Barrage will take some time yet, but regular progress is being made. It's kind of a spare spare time project, though.

I did say.

FYI, I'm transitioning to aotta's Pi version, PiRTO. All assets are prepared... box and label designs are completed and ready for a print test. A small quantity of boards and parts have been ordered, for testing. I've got a lot of parts leftover from the original, but that's life - it's not worth continuing that version, because it's way too difficult to assemble both the shell and the board. The PiRTO has some advantages, such as easier-to-source parts, and easier-to-assemble design.

I don't know if this helps anyone, but I thought I also had a dead 2600+. I had tried with a couple of different USB-C power bricks, but I guess they were expecting to communicate as high-powered chargers. I'm not a USB-C protocol expert, but it looks like a "legacy" cable that connects to USB-A, for instance, works better for this application. I hooked up a USB-A to USB-C cable to a crappy USB-A power brick, and it worked fine.