I bought this off Ebay, thinking it would be a strange F-122 with funny legends, but as Myoth pointed out, it's actually a very rare keyboard for the 4980 terminal - part number 4178208. Pictures: https://postimg.cc/gallery/xc931rkw/
The keyboard has only one stabiliser, and that's under the spacebar. It has plenty of weird keys, including a split right shift and relegendable keycaps on the numpad. The keyboard is very clean and appears to have seen little use. Strangely, some of the keycaps with thick, bold legends are mixed with keycaps with thinner, misaligned legends from another keyboard. There's also two B keys.
Sadly, the keyboard does not work with my Set 3 F122/M122 Orihalcon converter. How would I find out what protocol this keyboard speaks and how would I convert it? I really want to keep the cable.
Whoa, I read about this is a manual as I have the 4978 terminal for the Series/1. Very cool. You could try an figure out how the protocol works or desolder the existing controller and replace with a Model F Xwhatsit. If you do that at least preserve the irreplaceable controller.
Whoa, I read about this is a manual as I have the 4978 terminal for the Series/1. Very cool. You could try an figure out how the protocol works or desolder the existing controller and replace with a Model F Xwhatsit.
If all else fails, I'll just get an Xwhatsit. I find it bizarre how it speaks a different protocol. I just want to keep the original cable. It's really clean and looks amazing.
Whoa, I read about this is a manual as I have the 4978 terminal for the Series/1. Very cool. You could try an figure out how the protocol works or desolder the existing controller and replace with a Model F Xwhatsit. If you do that at least preserve the irreplaceable controller.
And yes, I'll absolutely keep the original controller.
Hmm.. that's a bit too advanced for me at the minute. I'll explore my other options before I dive into that.
Re: Converting IBM 4980 Model F Battleship
Posted: 11 Jul 2019, 15:30
by Muirium
Indeed. I wish someone like Orihalcon did ready made Common Sense controllers. They’re too much for me to understand. And I’ve built my own Soarer and TMK converters; from soldering to firmware flashing. All that Cypress stuff, though, baffles me like an SDK for a games console.
Indeed. I wish someone like Orihalcon did ready made Common Sense controllers. They’re too much for me to understand. And I’ve built my own Soarer and TMK converters; from soldering to firmware flashing. All that Cypress stuff, though, baffles me like an SDK for a games console.
What is the advantage of Common Sense over Xwhatsit?
Does this keyboard actually speak a different protocol? Or is it because of the extra keys? If I cannot use my converter, I will probably just get an XWhatsit - if it's as simple as soldering it to the PCB and binding things with the Utility program...
Indeed. I wish someone like Orihalcon did ready made Common Sense controllers. They’re too much for me to understand. And I’ve built my own Soarer and TMK converters; from soldering to firmware flashing. All that Cypress stuff, though, baffles me like an SDK for a games console.
What is the advantage of Common Sense over Xwhatsit?
Does this keyboard actually speak a different protocol? Or is it because of the extra keys? If I cannot use my converter, I will probably just get an XWhatsit - if it's as simple as soldering it to the PCB and binding things with the Utility program...
The wiki says that this keyboard was used with the Series 1 Minicomputer. Perhaps it has some differences in this way? There have been F122s found with dip switches and extra plugs that go into the controller. Normally the plug goes into the bottom row of pins, but yours has a plastic attachment in the middle if you notice the blue thing.
It would have gone here as in this image.
Spoiler:
f122 dip swtich.jpg (186.01 KiB) Viewed 9825 times
So I wonder if the controller is setup differently. Maybe at the factory they changed the dip setting if that is possible?
Regardless it is probably aside from that 100% the same as other F122s and easily convertable with xwhatsit or commonsense
Indeed. I wish someone like Orihalcon did ready made Common Sense controllers. They’re too much for me to understand. And I’ve built my own Soarer and TMK converters; from soldering to firmware flashing. All that Cypress stuff, though, baffles me like an SDK for a games console.
Its just additional solder points and nothing more.
I am happy to build you one if you ship me a controller.
But you'll still have to solder the PCB traces though...
Re: Converting IBM 4980 Model F Battleship
Posted: 11 Jul 2019, 16:32
by Muirium
It’s the software side that I find the most daunting part. I like to remap my boards quite a bit, experimenting with layout ideas. Having it hard baked would be a downer.
What is the advantage of Common Sense over Xwhatsit?
Does this keyboard actually speak a different protocol? Or is it because of the extra keys? If I cannot use my converter, I will probably just get an XWhatsit - if it's as simple as soldering it to the PCB and binding things with the Utility program...
Xwhatsit will get the job done. It’s what I’d do. But, as I understand, Common Sense is much more programmable, actively supported and quite a bit cheaper too.
Actively maintained is vital as years go on and OSes change. At some point, Xwhatsit’s GUI won’t run any more on the Mac for instance. Fortunately, you only need it for initial setup and re-mapping, so my Kishsaver is all set. (I’ve already played around with cunning layers there aplenty.)
But Common Sense’s biggest immediate advantage is the key specific thresholds. Xwhatsit uses a single trigger value for every key on the board, which can get a bit hairy to say the least. Common Sense is aptly named that way. But more of a bugger to install (where's the edge connector?) and certainly more of a challenge in getting setup, software-wise. It’s fans say it’s “easy” then start speaking in flawless Abyssal. It’s the damnedest thing…
That this keyboard speaks "3270/BSC data stream." but I am not sure
"The IOCP and the data stream support make the 4978 or 4980 look like a 3277 to the operator and to the
programs that communicate with the terminal. " Not sure if this is done keyboard side or terminal side...
So this keyboard may very well be sending acompletely different protocol to the computer
I think the easiest way to get this keyboard to work if it doesn't immediately work with a soarer converter is to just use xwhatsit or common sense.
Re: Converting IBM 4980 Model F Battleship
Posted: 11 Jul 2019, 17:58
by Wazrach
Looks like it's XWhatsit then. Just so I know what to do when I get it, is it as simple as soldering it to the PCB and installing the Capsense GUI?
Re: Converting IBM 4980 Model F Battleship
Posted: 11 Jul 2019, 18:18
by Wazrach
Also, if anyone wants to update the wiki with the pictures, you have my permission. I tried to do it myself, but it was a pain in the arse.
with your orihalcon converter that no codes are being sent out by the keyboard?
You basically would plug it into the converter and run that program. You may need to reboot with the keyboard plugged in.
Thanks for linking that. Nope, no scancodes.
Ah alright then. I am not entirely sure. I may be totally wrong on this, maybe conversion is done terminal side and it is just sending normal codes, it is a normal keyboard and we are overlooking something...
with your orihalcon converter that no codes are being sent out by the keyboard?
You basically would plug it into the converter and run that program. You may need to reboot with the keyboard plugged in.
Thanks for linking that. Nope, no scancodes.
Ah alright then. I am not entirely sure. I may be totally wrong on this, maybe conversion is done terminal side and it is just sending normal codes, it is a normal keyboard and we are overlooking something...
I was just about to strip it down and clean everything, ready for a foam replacement. If there's a chance it will work with my converter, I'll wait. I won't be able to test it afterwards, and I don't want to waste money on an XWhatsit if I don't need one
It would be bloody strange if it did speak a different protocol.. I mean, it uses the same plug as other F122s... Surely the plug would be different if it was another protocol?
Ah alright then. I am not entirely sure. I may be totally wrong on this, maybe conversion is done terminal side and it is just sending normal codes, it is a normal keyboard and we are overlooking something...
I was just about to strip it down and clean everything, ready for a foam replacement. If there's a chance it will work with my converter, I'll wait. I won't be able to test it afterwards, and I don't want to waste money on an XWhatsit if I don't need one
It would be bloody strange if it did speak a different protocol.. I mean, it uses the same plug as other F122s... Surely the plug would be different if it was another protocol?
Hi you are probably best to wait. I can get carried away with researching things like this... when a model f doesnt work it is usually something simple you have over looked
I won't be able to test it afterwards, and I don't want to waste money on an XWhatsit if I don't need one