Skip to main content

Writing a binary (bcd) clock in Forth for RC2014 and Minstrel 4th

 A

nother idea I had for using the 8x8 LED Matrix is a binary clock.  It fits very neatly into 8x8 pixels 

(The 8x8 matrix looks way better in real life than it does in these videos. It's very difficult to photograph or film.)

Eventually I want to learn to use interrupts on the RC2014. An interrupt routine would update a counter very accurately and independently of the main program, which could be divided for accurate seconds, minutes and hours.

In the absence of that and no counter (as far as I'm aware) in CP/M (the OS I use on my RC2014) it was necessary to write a 'jiffy clock' that you'd call from your main loop. Here it is:


The idea is that you call clinc every 1/60 second and it gives you hrs mins and secs words for access to those numbers. If you can't call it exactly every 1/60s, then it allows for calibration and by coincidence, the main loop of my program happens to loop almost at that rate, hence the number 62 at line 27. 

I was trying to be clever here and use a recursive routine. That's a very neat way to update a string of bytes (eg for a score) where each counts up to a certain value before tripping the next. In this case we want to count each up to 60. Except that we don't. The first may not be 60 as it's used for calibration, and the last needs to cycle back to zero at 24. Hence the 'wrapper', clinc, which handles those things and uses the recursive word for seconds and minutes. For the Minstrel version, discussed a little later, I dropped the recursion idea, thus lengthening the code a bit making it more readable.

The full RC2014 code is available here: (see BINCL-RC.F and jiffy.f)  
https://github.com/shieladixon/8x8_matrix_toolbox/tree/main/forth

(NB I use DXForth, the code may need to be altered for your favourite Forth.)

Porting to the Minstrel 4th

I was looking forward to taking advantage of the counter (FRAMES) within the Jupiter Ace system. This is a 4-byte counter which is updated by the interrupt routine, so it counts steadily, independently of your program.

My code for 'reading' FRAMES, adapted from an example in the manual, is this:


You simply call time at least once per second and you can read the secs, mins and hrs variables. That works, and works really well if you're just printing the time to the screen, say.  But when used within the matrix refresh loop, causes quite a blink, because of all the double-length maths involved. 

The problem is that the frame counter is simply a counter, so calculating the seconds, minutes and hours from it is quite an overhead. 

I spent some time trying tricks such as dividing the work up or inserting matrix refreshes between the calculations. That ended up with messy code and still a flickery display. 

In the end I've worked in the same jiffy clock as the RC2014 version. The advantage there is that the counter maintains 4 bytes as jiffies, seconds, minutes and hours.  So those can be accessed immediately without causing a delay. 


My latest code for this is also at https://github.com/shieladixon/8x8_matrix_toolbox/tree/main/forth - see BINCL_ACE.F

[update] Both of these versions now allow the user to input the time when the program starts. The standalone executable for RC2014 is also there.


Comments

Popular posts from this blog

RC2024/10 - my entry

A while ago I made this MIDI module for RC2014: It works but a better design would have its own serial chip and port decoding.  As it is, it provides the MIDI interface and a clock signal for the second SIO2 serial port. This means that it requires a little setting up and will only work for RC2014s with an SIO2 (and port B not already used). I think people might reasonably expect it to be plug-and-play and self-contained, ie do all the serial itself. My challenge to myself is to:  learn how to connect a serial chip (probably 68B50 ACIA) to receive the incoming MIDI and to serialise outgoing MIDI design the module, including the port decoding write a library so that it can easily be used on any RC2014. Potential applications include a MIDI sequencer and using incoming MIDI to trigger notes on the AY or SID sound chips. Entering the Retro Challenge 2024 (aka RC2024/10)  has given me an incentive to get on with this! I'm happy to see several more entries in the RC2014 catego...

IM53 8080 birthday cake

 Each year I've been trying to get more creative with ideas for Spencer's birthday cake. The plan this year was to incorporate LEDs in place of candles. I eventually settled on an Altair / IMSAI / PDP -style computer since those are the type of computers that inspired his RC2014. The IMSAI 8080 has the most colourful switches as well as a name that I could twist. The thought that it could show randomly flashing lights (as if the computer were running) and that it could also play a game of 'kill the bit' was very appealing. A plan formed to use a capacitive touch pad on the cake itself. The first job is to bake the fruitcake. I often use a 7" square tin and one of those cut in half and rearranged makes a cake of suitable proportions.  Even after taking a slice off the faces to make them nice and square, there are still some rounded corners, so after putting on the marzipan, I used more marzipan as a filler to flatten the whole thing. Even though I wanted to end up w...

Using the Speccy BEEP routine and a beeper speaker on my Orton 3C

W hen I first learned about the Orton 3C and its very clever serial routine which toggles A15 (meaning that the max 32k of ram appears twice in the address space) I've wanted to repurpose this for driving a beeper speaker, just as you might have done with the early PETs*  I'm writing this post after successfully playing a tune. The video is embedded near the end of this blog post if you'd like to skip straight to that. Yes, it certainly would be possible to toggle a pin on the digital i/o by 'out'ing to port zero. This would potentially allow for 'bit-banging' multiple voices, with a lot more work than I've put in so far. However, what I love about the Orton 3C is the 'bare bones'ness of it. The whole point is that it can work using only three chips and to that end I've unplugged my digital i/o for this. I didn't go to the trouble of removing the port zero protection shim (3C-PO) but its one logic chip isn't being used here since I...