Atari st series computers conversion PC

[joska]

There is no LED on the TT keyboard...

[megahz]

i know
you have a capslock led output on your code, connected to IO5 of the Arduino, so i assumed this will light on capslock, regardless there is an led on the TT Keyboard...
.........
#define PS2_PROCESS ps2_keyboard.process()
#define ST_KB_RESET 4 // Reset pulse for the ST keyboard on this pin.
#define CAPSLOCK_LED 5
#define PCMODE_LED_FREQ 1000

[joska]

But I don't use an Arduino. I just use an ATmega 168 on a piece of veroboard. No LEDs I'm afraid.

[megahz]

ok, i let it be as it is now, it runs perfectly with your code on an arduino-nano, the tt-keyboard and its western-plug is attached, the whole system (not fineshed yet) runs perfectly XP-SP3 since 3 or 4 days at a powerconsumion of 19.5Watts @ 13.8Volts! Makes a calculated Runtime of 8.5 hours with 2x6V12Ah PB Batterys.
I will test the runtime with real batteries soon, i think i have to put in 4 Batterys to "stay alive" over night until the PV-Module makes new Power...
Some things are in mind to do: a switchable HDD for Backup, 2 or 3 USB-Sticks inside, a pair of little speakers inside and TOSLINK SPDIF IN/OUT on a USB Soundcard. So this Beast will be able to do nearly anything.

If you read this, Frank: Thank you very much again for this TT-Case and thank you, Joska for your Keyboard Conversation !!!!
As soon as it is wearth, i will put some Photos on here...

Wolfram

[LuckyOldMan]

@Claus:
you could cut a few of the heatsink parts, i did that with a D510MO Mainboard too, so it fits into a 1HE 19" Case.
Doesn't get much warmer........

I could but I won´t. I´ll never touch the board in that way.
But I will give it a try to find other ideas to cool it down enough so that the heatsink won´t boil the kb.
Maybe something like this: iNTEL HTS1155LP

Cheers
Claus

[spiny]

I agree with megahz - you could trim the fins that are in the way, and probably not see any impact with temps. For backup, you could put a small fan in there as well, to blow air over the heatsink.

[LuckyOldMan]

....- you could trim the fins that are in the way, and probably not see any impact with temps.

The fins aren´t in the way - they just touch the kb´s backside. Most 520-kb are bent a bit in the middle after all these years so I guess that´s why.

For backup, you could put a small fan in there as well, to blow air over the heatsink.

I planned that right from the beginning (Scythe 100mm - !.000 RPM) - not only as backup (see pic).



The fan couldn´t be placed right above the heatsink (kb-cover is just placed on top not screwed) but the air circulation is good enough that after 1 hour working with the PC right now the heatsink has less temp than my hand.

Cheers

[megahz]

Great News of my TT-Atom:

i got a Teensy20 and flashed your Firmware, it runs very stable, the PS2 Arduino did forget sometimes the Keyboard...
So now TT-Keyboard an Mouse/Joystick working fine.
But i made some AddOns to the Firmware:
On Analog0 is a 33K/99K Voltage Divider, it measures the 12V PB Battery,
On Analog1 are 5 Resistors and 4 Pushbutton Keys, those keys, if pressed, send a short macro to the PC. Like a login account/pw or a standart text i always need in my ebay auctions
Those 4 Keys will be mounted at the front of the TT Case.
On D6,5,4,3 is a RGB LED connected, D6 is misused as VCC for the LED.
The LED shows me the Voltage of the Battery:
Blue: >13.80V
Blue/green: 13,30V - 13,80V
green: 11,90 - 13,30V
green/red: 10,90 - 11,90V
red: 10,60 - 10,90V
blinking red: under 10,60V

So this teensy has a little more to do.

ToDo: a automatic-hibernate if Battery is too low.

Attached the Listing....

Wolfram

Code: Select all

#include <Arduino.h>
#include <EEPROM.h>

#define ST_KB_RESET 9 // Reset pulse for the ST keyboard on this pin.
//#undef ST_KB_RESET  // Uncomment if you're using a Mega/TT keyboard.                     
#define CAPSLOCK_LED 10
#define PCMODE_LED_FREQ 1000

HardwareSerial ST_kbd = HardwareSerial();

// EEPROM structure
#define get_KBMODE (EEPROM.read(0) ? MODE_PC:MODE_ST)
#define save_KBMODE(mode) EEPROM.write(0, mode)

float volt = 55;
int taste = 0;
int makro_key = 0;

void setup(void)
{
  ST_kbd.begin(7812);
#ifdef CAPSLOCK_LED
  pinMode(CAPSLOCK_LED, OUTPUT);
  digitalWrite(CAPSLOCK_LED, HIGH);
#endif

  pinMode(11, OUTPUT);      // Onboard LED
  digitalWrite(11, HIGH);

  // --------------------------------------------------
  // RGB-LED für Batteriespannung
  // --------------------------------------------------
  pinMode(6, OUTPUT);       // gem.Anode RGB LED
  digitalWrite(6, HIGH);
  pinMode(5, OUTPUT);       // Blau der RGB LED
  digitalWrite(5, HIGH);
  pinMode(4, OUTPUT);       // Grün der RGB LED
  digitalWrite(4, HIGH);
  pinMode(3, OUTPUT);       // Rot der RGB LED
  digitalWrite(3, HIGH);
 
 
  // Check if a ST keyboard is attached.
  reset_st_keyboard();
  delay(100);
 
  // Num Lock on
  Keyboard.set_key1(KEY_NUM_LOCK);
  Keyboard.send_now();
  Keyboard.set_key1(0);
  Keyboard.send_now();
 
  // Init USB joystick
  joystick_init();
}

void loop(void)
{
  if (ST_kbd.available() > 0)
  {
    process_st_key(ST_kbd.read());
  }
 
  // Blinkenlicht
#ifdef CAPSLOCK_LED
  blink_leds();
#endif

  volt = map(analogRead(0), 0, 838, 0, 1630);        // Batteriespannung über 1:3 Teiler 33K/99K
  volt = volt / 100;
  taste = analogRead(1);                                  // analog Werte der Tasten mit 5x 4K7 Widerständen
  if (taste > 900)
  {
    makro_key = 0;   // 0
  }
  if (taste < 490)
  {
    makro_key = 0;   // 0
  }
  if (taste < 520 & taste > 500)
  {
    makro_key = 4;   // 0
    Keyboard.print("Batteriespannung ist ");
    delay (250);
    Keyboard.print(volt);
    delay (250);
    Keyboard.println(" Volt");
    delay (500);
  }
  if (taste < 690 & taste > 670)
  {
    makro_key = 3;   // 0
  }
  if (taste < 770 & taste > 750)
  {
    makro_key = 2;   // 0
    Keyboard.println("user");
    delay (250);
    Keyboard.println("password");
    delay (500);
  }
  if (taste < 850 & taste > 800)
  {
    makro_key = 1;   // 0
    Keyboard.println("Da Privatverkauf, keine Garantie oder Rücknahme!");
    delay (250);
    Keyboard.println("Viel Spass beim bieten!");
    delay (500);
  }
// ------------------------------------------------------------
// Batterie Anzeige
// ------------------------------------------------------------

  if (volt > 13.80 & volt < 15.00)
  {
    digitalWrite (5, HIGH);
    digitalWrite (4, HIGH);
    digitalWrite (3, LOW);
  }
if (volt > 13.30 & volt < 13.80)
  {
    digitalWrite (5, HIGH);
    digitalWrite (4, LOW);
    digitalWrite (3, LOW);
  }
 if (volt > 11.90 & volt < 13.30)
  {
    digitalWrite (5, HIGH);
    digitalWrite (4, LOW);
    digitalWrite (3, HIGH);
  }
if (volt > 10.90 & volt < 11.90)
  {
    digitalWrite (5, LOW);
    digitalWrite (4, LOW);
    digitalWrite (3, HIGH);
  }
if (volt > 10.60 & volt < 10.90)
  {
    digitalWrite (5, LOW);
    digitalWrite (4, HIGH);
    digitalWrite (3, HIGH);
  }
if (volt < 10.60)
  {
    digitalWrite (5, LOW);
    digitalWrite (4, HIGH);
    digitalWrite (3, HIGH);
    delay(250);
    digitalWrite (5, HIGH);
    delay(250);
    digitalWrite (5, LOW);

  }


  }


[LuckyOldMan]

Hi there,

after waiting for a few parts (USB3.0-header-adaptor,...) coming from China I completed my 520ST+ -PC.



I also added a half-PCI-e-board for WLAN & two small HP-Laptop-antennas (front left & right).



Next week I will get a cleaned 520ST+-housing & keyboard almost looking new and then this mainboard-base with all the parts will be transferred.

But already now my Atari520ST+ -PC is working fine!

Done this a new project is already waiting: the Atari 1040ST-PC! Just as done with the 520ST+ the mainboard in 1040 size as base is already finished & the Teensy2.0 fixed.



Hopefully soon the new Gigabyte H-170TN mainboard will be on the market and combined with a Intel Core i3-6300T it could be a nice Atari 1040ST-PC!

Cheers
Claus

[vfrvulcan]

Sorry to drag up an old thread, I wanted to PM Joska directly but my lack of posts precludes me from doing so.

I'm trying to convert my STFM keyboard to use with a Raspberry Pi 3. Due to the lack of availability of the Teensy 2.0 in the UK I've got a Teensy 2.0++, flashed various of Joska's firmwares and always end up with the same result, green LED is lit but no keypresses are received. Swapping Tx/Rx makes no difference.

Flashing the slow or fast blink hex files (blink_fast_Teensy2pp.hex located elsewhere in this thread) results in the device being seen as a USB HID Composite Device but still nothing works. Am I right in thinking the blink slow/fast files do only that and I need another version of ST_tastatur_USB compiled for theTeensy 2.0++ to get the keyboard working?

I believe I have done the wiring correctly from looking further up this thread:

Teensy2 to IKBD keyboard.png

IMAG0067.jpg

Any help appreciated

Aaron

[joska]

Flashing the slow or fast blink hex files (blink_fast_Teensy2pp.hex located elsewhere in this thread)

This is a binary file that will only work with the Teensy 2. You need to recompile the sources for the Teensy 2++. I've attached one, but I don't have a Teensy 2++ to test it with. Same pinout at the Teensy 2 version.

ST_USB_keyboard Teensy 2++.hex.zip

[vfrvulcan]

Thanks Joska,

I'll give it a try and report back

Cheers

Aaron

[vfrvulcan]

Thanks Jo,

Really appreciate the quick response. Duly flashed, detected and able to receive keystrokes.

However keypresses are not as expected with garbage being produced

I don't like to ask for the source to recompile (if I work out how) as it is your code but I also don't want to take up your time compiling/bug hunting.

Aaron

[vfrvulcan]

I've had another play with this tonight and figured I'd try it on a USB 2 port instead of USB 3 (testing on PC before going to the Pi).

It seems that it works fine for half a dozen or so characters then decides that it's going to throw in random characters on a keypress, sometimes two. A lot of the time it will throw in what seems to be F1 as Internet Exploder gets launched and goes to a Windows 10 help page, other times it brings up the search box in Notepad (which is where I'm trying it) or a dialog box with string not found.

After this I have to disconnect the Teensy for a while and plug it back in. I get the same results plugging back into USB 3 so it's not a USB2/3 issue

Any way to check if I have a good Teensy? A bit stumped at mo.

As before, any help appreciated!

[joska]

I suggest you download and install the Arduino software, and then the Teensyduino add-on from the PJRC website. You'll then be able to compile the Teensy example programs and see if they behave correctly.

[roninfourseven]

I've had another play with this tonight and figured I'd try it on a USB 2 port instead of USB 3 (testing on PC before going to the Pi).

It seems that it works fine for half a dozen or so characters then decides that it's going to throw in random characters on a keypress, sometimes two. A lot of the time it will throw in what seems to be F1 as Internet Exploder gets launched and goes to a Windows 10 help page, other times it brings up the search box in Notepad (which is where I'm trying it) or a dialog box with string not found.

After this I have to disconnect the Teensy for a while and plug it back in. I get the same results plugging back into USB 3 so it's not a USB2/3 issue

Any way to check if I have a good Teensy? A bit stumped at mo.

As before, any help appreciated!

I am also sorry to pull up this post after such a while, but I am in the same boat as VFRVulcan. I also have a Teensy 2.0++, and am wired identically.

Something is clearly working, as if I type as soon as I plug in the keyboard, I can type actual words, but within 30 seconds it all goes awry and I just get random characters coming through.

I have tried both the Tennsy 2.0 and Teensy 2.0++ firmware from this thread and the result is much the same, with immediate use showing the correct characters, and 30 seconds later, garbage.

I am more than willing to do any testing to get this to work.

I can confirm that the test programs for the Teensy work fine, and as it was brand new I am willing to believe that is is fine.

[vfrvulcan]

I am also sorry to pull up this post after such a while, but I am in the same boat as VFRVulcan. I also have a Teensy 2.0++, and am wired identically.

Something is clearly working, as if I type as soon as I plug in the keyboard, I can type actual words, but within 30 seconds it all goes awry and I just get random characters coming through.

I have tried both the Tennsy 2.0 and Teensy 2.0++ firmware from this thread and the result is much the same, with immediate use showing the correct characters, and 30 seconds later, garbage.

I am more than willing to do any testing to get this to work.

I can confirm that the test programs for the Teensy work fine, and as it was brand new I am willing to believe that is is fine.

Well, six weeks after giving the Teensy 2.0++ to my cousin to solder properly for me, I finally got it back today. Been itching to get this sorted for ages.

I plugged it in - and it didn't work. Re-flashed the firmware and tried again - success! It has now been running for around 5 hours, initially tested on a PC but then attached to my Raspberry Pi 3, done a couple of RetroPie full updates, used the terminal, kept on typing and not dropped a beat until I plugged an ST mouse in while 'hot'. The characters 513 were displayed on the terminal but pressing ctrl-C cleared the line and all was good. I unplugged the mouse again but really should spend some time trying it, along with a standard Atari joystick instead of using the USB StellAdapter as before.

So Ronin, might be an idea to check your soldering, my original effort is shown in my post above, now it looks like the pictures attached here, and as I say, not skipped a beat in hours! Only difference physically is that I asked him to connect the ground to pin 8 instead of pin 1 on the keyboard end

And a massive thank you to Joska for his sterling work.

Regards

Aaron

full_kit.jpg

teensy.jpg

keyb_connector.jpg

[roninfourseven]

Cool, thanks VFRVulcan, I will try this out as soon as I get the chance, using your wiring as a guide. Can you tell me which firmare you used? Was it the Teensy 2++ hex file posted on here by Joska? I have PM'd him, but this gives me hope ti my just be a poor connection somewhere.

[roninfourseven]

So, I thought it worthwhile trying to swap the ground pin as you suggested, as its a quick and easy thing to do, and the damn thing is working. In fact I've just typed this whole

And that is as far as I got before it went wonky again. I will rewire as per your pic above and will let you know what happens.

[vfrvulcan]

The one posted by Joska for the Teensy 2.0++ a few posts up:

http://www.atari-forum.com/download/file.php?id=30298

[vfrvulcan]

So, I thought it worthwhile trying to swap the ground pin as you suggested, as its a quick and easy thing to do, and the damn thing is working. In fact I've just typed this whole

And that is as far as I got before it went wonky again. I will rewire as per your pic above and will let you know what happens.

I'm not sure changing the ground pin is the answer - it is more likely my ham-fisted attempt at melting wires onto PCBs

[roninfourseven]

Thanks VFR, looks like the firmware I'm using. I'm going to rewire and pick up the ground and +5v from the same place as you, plus make a better connection to the keyboard itself, as mine could be better.

TBH it seemed to be working ok after the ground wire swap, BUT, I moved the keyboard and it went wonky, so I am prepared to believe there is a bad connection.

I have also PM'd Joska, but if it is working for you, I think it should work for me. I'll let you know how I get on.

[vfrvulcan]

I was initially using using 10cm male-male wires and pushing them into the female Atari connector - I think this was the problem. It seemed to work a bit better if I held everything together firmly but would eventually carp-out. Wiring onto a .1" connector strip gives a much better, solid connection.

The firmware I linked to above is the one you should be using as all the others are not for the Teensy 2.0++

Good luck!

[roninfourseven]

So, VFRVulcan, I have replaced my plug with a 1 piece connector strip as per your photo, and have resoldered all of the connections to match yours, and I maybe get a minutes use out of it before it bombs out again.

Flashed with the firmware you linked to.

I've tried with Windows 10 and XP, Vista and get the same result each and every time, about 40-60 seconds of good typing, followed by junk.

I've also tried with a different ST keyboard and the same every time. i aso tested the keyboard on one of my ST's and it's all good, so not that.

Without the knowledge to write my own code, I'm a bit stuck now, so off to see if I can find a Teensy 2 at a reasonable price.

[roninfourseven]

Found a Teensy 2 on RS, but it's back order, so I have done so. In the meantime I will continue to fiddle around with the 2++ I have. I'm wondering if it's a power issue.