Steve Guidi

Thanks for pointing me in the right direction,@Al_Nafuur. This is indeed the problem. I have a 64-character wifi key on my network which I entered via the Wifi Management Portal. I'm not sure why the initial connection was not successful, but I've since connected to a guest network with a simpler key (via the PlusCart UI) and have no issues. I'll debug this a bit further and send the Device Info photo if I can't figure this out -- don't want to monopolize your time if I can avoid it! 🙂 Thanks for your help so far! EDIT: Everything is setup and working now. I have an embarrassing suspicion that I used the wrong password for my wifi network when first configuring the cartridge. Double-checked the password before submitting, and now the cartridge is online via my main network and also connected to the PlusStore.

Oh, I did try to use my PlusStore username too (sguidi), but the wifi portal page responded with "Connection request for your PlusCart sent, please check your email and confirm". URL is 192.168.4.1/0save?s=sguidi. Is this expected? I wonder if my device is having problems connecting to the public internet. The connection info on the portal always shows 0%, but the cartridge doesn't prompt for "wifi-retry" on power-on and shows a varying degree of connection strength. My router also shows an ESP client connected, so it should be working. EDIT: I should note that I created my PlusStore account via https://plusstore.firmaplus.de/index.php/apps/registration/ and not the PlusCart. I wonder if some account-link information is missing from the cartridge's saved state?

Indeed, it is. I was able to get a registration email sent to an email address that forwards to my @gmail.com account (it was flagged as spam), and created the PlusStore account with that email address. Now I'm attempting to connect the PlusCart to the PlusStore account via the cartridge's webserver, which appears to need another email validation. I have an old Office 365 email that I may try to reuse if the above won't work.

Finally assembled a PlusCart this evening and started to configure it! As part of the setup, I'm trying to create a PlusStore account with my email address. What is the general turn-around time for receiving the validation email? I've registered my email address twice via the admin page (PlusCart in web-server setup mode), and twice via https://plusstore.firmaplus.de/index.php/apps/registration/. No validation email yet . I'm going to bed soon, so I'll check and/or try again in the morning.

SpectraVideo's keyboard product came with a Microsoft Basic implementation that had much more RAM, but it also included other limitations like only being able to edit a line once during program entry.

The paddles are built with a 1M-Ohm potentiometer, which is given 5V from pin 7 in the controller. The system detects the "resistance" by measuring the time taken to charge an internal capacitor. If the capacitor is out of spec, then the charge time will vary and produce a different and incorrect reading of the controller's potentiometer. I suspect this is the case since you've verified the correct behavior on the other joystick port, using the same controller. Here's a link to the schematics showing a .068uF capacitor used on the analog input pins (5,9 for paddle inputs). Perhaps you can just replace the ones used on the misbehaving port. https://www.atariage.com/2600/archives/schematics/Schematic_2600_Low.html

Not ideal, but you can use a battery pack to run the Atari 2600. You need about 7V to overcome the voltage drop off the regulator and get 5V on the output. I've used 6x1.2V NiMh cells with about 2000mAh. That will last about 4h for a 500mAh draw, which is what the original supply is rated for (Atari 2600 Jr., NTSC).

To be honest, I don't remember. I haven't played this one seriously in about 30 years ?

There are some games that requires this, but I don't recall if Raiders is one of them. As for the game play, one of the first rooms you will enter will become sealed and inaccessible after some time had passed.

This guy claims to be selling the complete Zellers collection, but unfortunately your cartridge is not shown. https://www.ebay.com/itm/Atari-2600-ZELLERS-The-Complete-Collection-Video-Game-Console-System-Lot-/293563824995

The kit you have is a very common amplifier replacement that produces a composite video signal. I built one using the schematic and installation instructions from the following page, which I'm fairly certain is practically identical to your circuit board. https://www.instructables.com/ATARI-2600-Video-Composite-mod/ The difference between the kit and schematic is the omission of a resistor from video-out to ground, which darkens the output signal. You can review the instructions above including which components to remove and hopefully you can resolve any discrepancies with other YouTube videos. Also, I did not remove the RF modulator in my installation; no problems by keeping it in place.

That's a great observation. The structure of the program effectively has the screen cleared for a longer amount of time than when the text/time is on the screen. clear-compute-print-repeat v.s. compute-clear-print-repeat

Here is part 2 (of 2) of this series, where I explore the graphics, music, and keypad input features. I also cover some memory optimization techniques that are needed while enhancing the clock program from the "BASIC Programming" manual.

Close enough?

I really enjoyed putting the following video together, exploring what could be done with BASIC Programming. I spent a whole day tinkering with the cartridge and was impressed with what was produced. Yes, there are several limitations -- and they are frustrating if you have a background in computer programming, but somewhat manageable. The keyboard controllers are cumbersome, but you get accustomed to it within hours. It helps that there is some logical organization of the symbols on the overlays. It is also unfortunate on how precious of a resource memory is with this interpreter. Just tracking variables costs memory -- you pay for every character rendered to the screen, visible or not! Lots of fun -- but only knowing full-well what you're getting yourself into when you try to write a "lengthy" program from the manual