Search the Community
Showing results for tags 'rtc'.
Found 6 results
-
Received a brand-new SIDE3 on Monday. Straight out of the box, I upgraded it to version 0.40 of @flashjazzcat's firmware and installed an 8GB Kingston Micro SD card (class 10, U1) in an adapter. Everything seems to work fine in terms of cartridge loading functionality. However, the RTC seems to lose a significant amount of time - about 20 minutes per day, give or take. At this rate, it looks as though a loss of about 2.5 hours / week will be the rough average. The battery is presumed healthy as it reads dead-on 3 volts outside of the cartridge. Use is in a 600XL with a 64K internal RAM upgrade and an 800XL with both an internal 256K RAM upgrade and UAV. Both machines are powered by 5V 2.5A USB power supplies (ex-RasPi) through cable adapters from the usual suspects. Any thoughts? I'm at something of a loss to explain it.
-
I had a 1040ST in the late 80's early 90's. I purchased a very good 1040STfm and SC1224 (color monitor) on eBay, all seems to be working great. So I have a couple basic questions as I get to know the ST again :-) Thanks in advance. Please see the attached picture: 0) Where can I find good FAQ details about the ST line? 1) What version of TOS do I have? How do you tell? 2) Are these two socketed chips my TOS? 3) I see the Gotek drive replacement option. Is there an option that does not require any case cutting? 4) Is there an external (2nd drive) option for Gotek? 5) See image of my current floppy. Can you upgrade to a 1.44MB drive? If so, what version of TOS would support this? 6) Is there a TOS that can handle Y2K (dates with years like 2019)? 7) Is there a real-time clock (RTC) add-on? 8 - Best source for new TOS?
-
since i've finnished with shipments of boards from previous run, i'm able to make another 100 boards preorder will be open for a month board wasn't altered so there is still a need of adding 2 resistors to RD4 and RD5 signal lines (please see spiflash.org, or previous preorder thread for details) as for now, boards are partially assemble to the point where semiconductors should be soldered in, this means shorter time for delivery realistically it will be 3 or 4 months starting from now (some parts have very long lead time, and aren't stocked) board cost is $50 or 40 euro (170pln), shipment is $7 for up to three boards preorder will be open for a month, and then i'll contact each of you individually with the details please put quantity and target machine type in this thread, it will shorten my paper work and prevent situations i'm having right now (few boards are still undelivered because of missing shipping address or machine type) Sebastian memo
-
I wanted the RTC project to be over but it wasn't long before daylight savings kicked in and I needed to reset the clock. All I wanted to do was be able to run a program on the Atari8 to set the time on the RTC and then have it rerun the SETCLOCK.BAS to update the clock on the Atari8. And as long as I was going to do that I may as well reconfigure the hardware and………. . So by the time I was finished it needed to be called version 2.1. Hardware: When I found Arduino Uno clones for $6.50 it didn't seem cost effective to build my own PCB. Then the price of the bare Sparkfun prototype shield seemed reasonable so I used one of those. The parts list for the shield: Prototype shield and pins RTC module RS232 to TTL converter module Set CLOCK push button 10K Resister LED 330 ohm Resister Micro switch for Arduino reset on shield. (not required, you can hold down set button and turn power off and on) The schematic shows the pin usage and wiring. How you place your components may be different. There is more then one design of prototype shields and components. This time the power for the RTC module is supplied by Analog pin 2 and 3. The pins were set for output and pin 2 was set to Low(ground) and pin3 was set to HIGH(+5V). The RS232 converter is wired to digital pin10 and 11. This allowed the USB serial on pin D0 and D1 to be used for programming and power. The softwareSerial library was used to send and receive data to the Atari8. (This also created the option of using both USB and RS232 ports at a later date.) The set time button is used to activate the routine to receive RTC data from the Atari8. Press the button then power up the unit or press the reset button. The LED should turn on, indicating that the Arduino is ready to receive the data from SETRTC.BAS program. SOFTWARE: The arduino sketch and atr disk image are contained in the .zip file. RTC_v2_1.zip Of course the Arduino software was rewritten. Version 2.0 tested the softwareSerial library. (http://www.arduino.cc/en/Reference/SoftwareSerial) Once that was working the set RTC function was implemented and called v2.1. (I know someone is going to want to know what happened to version 2.0. ) The SETCLOCK.BAS program is still the same program as before and is run by the same AUTORUN.SYS file. The SETRTC.BAS is new. Once the Clock is running and you want to reset the time on RTC; run this program. It sets up the 850 for serial output then gathers the time/date information. Although the Atari Clock uses only the time data, the RTC needs the date data to reset.(who knows, some day you may need the date.) There is no AM/PM option; time will need to be military time. The computer then waits for you to put the Arduino in set time mode. Press the button and then press the reset button. When the LED lights the Arduino is ready to accept the data. Press RETURN on the Atari. The Atari8 then sends the data to the RTC and runs SETCLOCK.BAS to resets the ATARI clock with the new time. Can it be any simpler? Since I expect this to be a one of a kind project. Feel free to use this as reference or modify it to suit your needs. Even if you're trying to use it with your RS232 equipped C64.
-
Part 1 ended with the Arduino/RTC/RS232 shield able to send the time and date to the Dell. The next step was to hook the unit up to the 850 and read the data using Bob Term. Once the Baud rate, translation and duplex were set to 9600bps, ASCII and Full, the time and date were updated every second, just like on the Dell. As I watched the stream of data being printed to the screen I said to myself, "This is going much to smoothly. I bet the RS232 device handler and clock are going to use the same memory." I won the bet. An AUTORUN.SYS file was created that would load the handler and then the clock. Manually setting the clock with CLOCK2.BAS was successful but got a device not found error when opening a channel to the R: device. Messing around with the AUTORUN file made it possible to open "R1:" but crashed when closing the channel. A BASIC program was written to print the value of MEMLO to determine the shared memory and find a new location for the clock code. MEMLO.BAS 10 ? PEEK(743)+(PEEK(744)*256) A couple of system setups were tested and the following was observed. MEMLO: HEX DEC DOS 2.5 $1CFC 7420 DOS 2.5 and Clock $2340 9024 DOS 2.5 and RS232 $2362 9184 This proved that the clock and RS232 handler were trying to use the same memory from $2200 to $2362 and compiling the clock at $2400 should solve the problem. At this time I would personally like to thank Jonathan Buckheit for a well written article. The technical information contained in his article from ANTIC 31 was invaluable. I would also like to say a couple of words about ANTIC not including the assembly code listing on that issue's disk, but won't. The assembly code was typed in, excluding most of the comments using MAC65. It was saved to disk as CLOCK.M65. Several errors in my typing were corrected the first time it was proof read and then two changes were made during the second round of proof reading. ORIGIN = $2400 DOSII? .BYTE 1 ; because I am using DOS2.5 It compiled to CLOCK.SYS without error (the first time). Then line 210 of CLOCK2.BAS was change to point to the new location and saved as SETCLOCK.BAS. A boot disk was set up to autorun CLOCK.SYS and then set the time using SETCLOCK.BAS. Success!!!! The last step was to create an AUTORUN.SYS file to load in the R: handler, load in the clock and then load in the SETCLOCK.BAS to manually set the clock. SETUP.COM from the DOS2.5 disk was used to create an AUTORUN.SYS file to load the RS232 handler and then renamed it LOADRS.SYS. Then another AUTORUN.SYS file to load the basic program SETCLOCK.BAS was created. Renamed that file RUNSETCL.SYS. The three files were then combined using the DOS copy command. Copy LOADRS.SYS,AUTORUN.SYS COPY CLOCK.OBJ,AUTORUN.SYS/A COPY RUNSETCL.SYS,AUTORUN.SYS/A It worked. The RS232 loaded, the Clock loaded and the SETCLOCK.BAS loaded. After entering the hours, minutes and seconds, the time was displayed and the seconds incremented. A channel to the "R:" device was open and closed without a lockup. This .ATR file includes a README.TXT that contains descriptions of the files created for this project(so far). clock rs.atr I'm feeling confident that the SETCLOCK.BAS program can be modified to OPEN a channel to the RS232 port and get the time from the RTC. Only when it has been accomplished will I be 100% sure.
-
In the June 1985 issue of ANALOG (#31), the "ATARI CLOCK" by Jonathan Buckheit was published. It is a machine language program that added an extra text line to the top of the screen display and printed the time once per second. I remember typing in CLOCK1.BAS to create an AUTORUN.SYS file and CLOCK2.BAS to set the time. I also remember using it but soon tired of inputting the time for each REBOOT. Download ANALOG issue #31 for more information. http://www.atarimania.com/atari-magazine-analog_18.html The forums had several links to that issue's disk image. This is one of them. Download AN31 B.atr and check it out. ftp://ftp.pigwa.net/stuff/collections/holmes%20cd/Holmes%203/ANALOG/index.html Almost 5 years ago a RTC circuit was purchased to hook up to the Arduino Uno only so that it would be available for a project. Setting the ATARI CLOCK using data from the RTC seems to be that project. So while I've been waiting for some divine inspiration to point me toward the best way to transfer the data from the Arduino to the Atari, the RTC battery died. I have also tired of waiting for the divine intervention and will start by using the RS232 interface(850 or P:R: Connection) for the link. Step 1. Find information on RTC and Arduino As it happened, the RTC in my parts box is a SainSmart I2C RTC DS1307 module, TinyRTC v1.1.( http://www.sainsmart.com/arduino-i2c-rtc-ds1307-at24c32-real-time-clock-module-board-for-avr-arm-pic.html ) There are several boards and different clock chips that can do the job. I don't have enough information to make a recommendation. Adafruit has a lot of information on their DS-1307 RTC kit. Worth the read. https://learn.adafruit.com/ds1307-real-time-clock-breakout-board-kit/overview Step 2. Arduino Software: Arduino.cc has a library that works with the DS-1307 based RTC. Another source for information and a software example was found at Tronixstuff. John Boxall, author of the book, Arduino Workshop, has written the tutorial. His program does not use a library to set or read the time-date information. This gave me a clearer picture of how it all works. http://tronixstuff.com/2014/12/01/tutorial-using-ds1307-and-ds3231-real-time-clock-modules-with-arduino/ The RTC and Arduino were wired using the tutorial information. Clock - Arduino Vcc -5V Gnd - Gnd Scl - A5 Sca - A4 I copied the code and pasted it into the Arduino IDE. Then I compiled and ran it. The serial port was then monitored to view time and date. This is when I found out the backup battery was dead. When you change the battery or want to set the clock, the program needs to be modified to call the SETDS3231time function. Remove the comment delimiter from line in setup() with the SETDS3231time function and set the parameters. The SETDS3231time function needed to be moved to just before setup() function. An undefined function error occurred until it was moved. The time was now being sent to the serial monitor. Now, put the comment delimiter back in front of the SETDS3231time in setup() and reprogram the Arduino. If you don't, every time the Arduino is powered up the clock gets reset to the time specified in the call. Most if this is explained in the tutorial. (I disconnected the RTC to be sure I didn't accidently reset the time.) Step 3. Communicate through the RS232 shield. The RS232 Shield was plugged into the Arduino and the RTC was wired into the shield. An RS-232 - USB converter was plugged into the computer and RS232 shield. A 9V battery was used to power the Arduino instead of the USB connection because the USB port on the Arduino and RS232 shield share the same pins for data transfer. The converter was defined as COM3 and reproduced the data stream to the Serial Monitor. The RS232 Shield had been used in a previous project and was expecting these results. (Atari 8 bit <-> 850 Interface <-> RS232 Shield <-> Arduino) . At least I know that the RTC module, Arduino, RS232 shield are working properly. I'm waiting for a gender changer to make the connection to the 850. And I'm still waiting for that inspiration.
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord