omg i love this! great job man! also super nice carpet for the mouse hahaha
Let's create the FSSK/FEXT = DONE !!!!
-
dcopellino
- Location: Italia - Napoli
- Main keyboard: IBM 4704 F400 brushed chrome
- Main mouse: Logitech laser wired
- Favorite switch: Buckling spring
- DT Pro Member: 0229
- Contact:
-
Man from Mars
- Location: Italy
- Main keyboard: IBM M122, CM Novatouch, old yellow BTC rubber dome
- Main mouse: whatever or a cheap ergo-ish one
- Favorite switch: Tactiles
Very nice! How (When) can I book a "test drive"?
-
dcopellino
- Location: Italia - Napoli
- Main keyboard: IBM 4704 F400 brushed chrome
- Main mouse: Logitech laser wired
- Favorite switch: Buckling spring
- DT Pro Member: 0229
- Contact:
whenever you want, you're welcome to my home. Sorry, but i can't take it to the billiards
-
daemonspudguy
- Location: United States
- Main keyboard: Unicomp New Model M 103 Key
- Main mouse: Some RedDragon branded gaming mouse from China
- Favorite switch: IBM Buckling Spring
- Contact:
How did you get the PCB files to order one?
-
dcopellino
- Location: Italia - Napoli
- Main keyboard: IBM 4704 F400 brushed chrome
- Main mouse: Logitech laser wired
- Favorite switch: Buckling spring
- DT Pro Member: 0229
- Contact:
Here you are. Consider that you should order as minimum quantity order at least 5pcs from jclpcb. I've got 2 spare PCBs left. Send me a PM If you're interested, I could give them to you.
Edit: (it won't be worth having them sent to you from Italy)
Edit: (it won't be worth having them sent to you from Italy)
-
vineyard88
- Location: Singapore
- Main keyboard: Model M
- Main mouse: Viper Mini
- Favorite switch: Buckling Spring
This is so well done! hope you are enjoying the "FSSK" well.dcopellino wrote: ↑16 Dec 2022, 12:36.......continues from the post above
Fastening and unfastening all layers together or tuning a musical instrumentMaking extra room to house the controller into the bottom case. Look at my birth date....Spoiler:
Keep testing and other extra final steps.Spoiler:
20221215_171542.jpgSpoiler:
all's well that ends well
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Very nice !!!!dcopellino wrote: ↑16 Dec 2022, 12:22Assuming that “Let's create the FSSK/FEXT = DONE !!!!” should never be considered a necro but rather an evergreen common thread, I’d like to share here my pic log presenting my personal FEXT implementation according to i$'s original post to whom I give credit and gratitude, along with all the other thread contributors.Yet another model FEXT implementation,
(aka IBM model MotherFucker*)
Very nice !!!!
Have you installed QMK or VIAL in the xwhatsit controller ?
i$
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Hi,
You may know that I daily use the FSSKs which I originally created. I built three units of them:
1.- FSSK prototype which I daily use at the office
2.- FSSK prototype which is connected to my desk at home for home office
3.- FSSK v1.00
you can find he manual here viewtopic.php?f=7&t=13551&hilit=fssk+manual
I am very happy with the fact that the idea was further elaborated.
I am not fine with the fact that ellipse used FSSK name and all the work that I did to create his own version without asking for permission nor contacting me before. Since years he has been profiting from the works of others without offering the recognition they deserve (in my opinion). In any case, this is a different topic. Lets park it
I believe that people will not be interested in any firmware for the prototype. As I said before, there are just two of these keyboards.
I am sharing the HEX for FSSK v1.00 that was offered in the group buy long time ago. I also include the files which I used to compile the firmware.
I have NOT ported any code. I have just used the work described here (https://www.newfxx-firmware.nconx.com/) to create the template and the matrix required to compile the firmware.
PLEASE ensure that you have a rescue HEX firmware which works to rescue the keyboard in case needed.
I really wanted to include also a rescue HEX. I have not done it as it would just work on the FSSK prototype.
If you want to work with the code you should note that:
1.- a Vial executable will help to monitor the matrix and enter the bootloader mode
2.- Purdea Andrei 's util to check the matrix and levels as well as to enter the bootloader mode
3.- Consider soldering two cables to the reset pins of the xwhatsit controller to access them from outside the keyboard case (rescue).
It should be possible to create easily create a firmware for the FEXT, but as I never built one of these, I have not done it.
Please, let me know any question that you may have and report success or issues.
I am not very active in the forum due to work load, but I will monitor my messages to ensure that I can answer questions.
Many thanks to all who made this post possible. I really enjoy having VIAL in my keyboards !!!!!
i$
P.D.: there is no need to say that this post was typed with the FSSK prototype running VIAL
You may know that I daily use the FSSKs which I originally created. I built three units of them:
1.- FSSK prototype which I daily use at the office
2.- FSSK prototype which is connected to my desk at home for home office
3.- FSSK v1.00
you can find he manual here viewtopic.php?f=7&t=13551&hilit=fssk+manual
I am very happy with the fact that the idea was further elaborated.
I am not fine with the fact that ellipse used FSSK name and all the work that I did to create his own version without asking for permission nor contacting me before. Since years he has been profiting from the works of others without offering the recognition they deserve (in my opinion). In any case, this is a different topic. Lets park it
I believe that people will not be interested in any firmware for the prototype. As I said before, there are just two of these keyboards.
I am sharing the HEX for FSSK v1.00 that was offered in the group buy long time ago. I also include the files which I used to compile the firmware.
I have NOT ported any code. I have just used the work described here (https://www.newfxx-firmware.nconx.com/) to create the template and the matrix required to compile the firmware.
PLEASE ensure that you have a rescue HEX firmware which works to rescue the keyboard in case needed.
I really wanted to include also a rescue HEX. I have not done it as it would just work on the FSSK prototype.
If you want to work with the code you should note that:
1.- a Vial executable will help to monitor the matrix and enter the bootloader mode
2.- Purdea Andrei 's util to check the matrix and levels as well as to enter the bootloader mode
3.- Consider soldering two cables to the reset pins of the xwhatsit controller to access them from outside the keyboard case (rescue).
It should be possible to create easily create a firmware for the FEXT, but as I never built one of these, I have not done it.
Please, let me know any question that you may have and report success or issues.
I am not very active in the forum due to work load, but I will monitor my messages to ensure that I can answer questions.
Many thanks to all who made this post possible. I really enjoy having VIAL in my keyboards !!!!!
i$
P.D.: there is no need to say that this post was typed with the FSSK prototype running VIAL
- Attachments
-
- vial_firmware_for_original_FSSK_V1.00.tar
- (140 KiB) Downloaded 51 times
Last edited by idollar on 06 Jul 2024, 19:12, edited 1 time in total.
-
dcopellino
- Location: Italia - Napoli
- Main keyboard: IBM 4704 F400 brushed chrome
- Main mouse: Logitech laser wired
- Favorite switch: Buckling spring
- DT Pro Member: 0229
- Contact:
- 20231215_171445.jpg (3.13 MiB) Viewed 4510 times
Any advices on how to make this new project vial compatible will be very appreciated, of course.
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Hi dcopellino,
I was reading the posts where you described your adventure with the FEXT before I wrote in the forum today. I feel proud.
Which controller are you using ?
I am using the "historical" xwhatsit which started all of this. Without the work of Tom Wong-Cornall we would not have the opportunity to feel the "F" every day. ([url]hhttps://static.wongcornall.com/ibm-capsense-usb/[/url]).
I am 99% sure that you can run your keyboard in a QMK-VIAL firmware. Xwhatsit is based on the atmega32u2 which has limited memory. The trick is to limit the number of layers to 3, as well as the number of other features like tap-dance. When this is done, it is possible to compile an HEX that just fits:
To do it in the config.h you define the limits:
The procedure that I have used to "create the keyboard" was:
1.- create the vial.json file
I did that manually, matching the matrix of the PCB.
I have not covered the "number extension in the FEXT" but it should be simple to figure out the columns and rows using the "util"
2.- Edit xwhatsit.h as needed also to match the matrix.
3.- Create a layout json to build the firmware:
The FSSK firmware which I posted before shall work (without numpad) in your FEXT.
If you have the firmware that you are running saved, you can test VIAL. You can check also the VIAL application. You will always be able to come back to your original firmware.
I can help you to compile a full FEXT version of the firmware, if you are interested.
VIAL is nice. Creating macros in the fly and the tap-dance feature are so nice !
I assume that you are already running in QMK, isn´t it ?
Cheers
i$
I was reading the posts where you described your adventure with the FEXT before I wrote in the forum today. I feel proud.
Which controller are you using ?
I am using the "historical" xwhatsit which started all of this. Without the work of Tom Wong-Cornall we would not have the opportunity to feel the "F" every day. ([url]hhttps://static.wongcornall.com/ibm-capsense-usb/[/url]).
I am 99% sure that you can run your keyboard in a QMK-VIAL firmware. Xwhatsit is based on the atmega32u2 which has limited memory. The trick is to limit the number of layers to 3, as well as the number of other features like tap-dance. When this is done, it is possible to compile an HEX that just fits:
Spoiler:
To do it in the config.h you define the limits:
Code: Select all
#define VIAL_TAP_DANCE_ENTRIES 4
#define VIAL_COMBO_ENTRIES 41.- create the vial.json file
I did that manually, matching the matrix of the PCB.
I have not covered the "number extension in the FEXT" but it should be simple to figure out the columns and rows using the "util"
Spoiler:
Spoiler:
Spoiler:
If you have the firmware that you are running saved, you can test VIAL. You can check also the VIAL application. You will always be able to come back to your original firmware.
I can help you to compile a full FEXT version of the firmware, if you are interested.
VIAL is nice. Creating macros in the fly and the tap-dance feature are so nice !
I assume that you are already running in QMK, isn´t it ?
Cheers
i$
-
dcopellino
- Location: Italia - Napoli
- Main keyboard: IBM 4704 F400 brushed chrome
- Main mouse: Logitech laser wired
- Favorite switch: Buckling spring
- DT Pro Member: 0229
- Contact:
Hi I$, thanks for your kindly support and encouragement. As you will have understood, having quoted the SMD Universal controller designer team, I'm using that controller sporting an Atmel MEGA32U4. So, since the beginning I oriented my choices for the compiling of the firmware toward one forced direction: QMK, thanks to the ready configurator by Pandrew. Here my json/hex file . For my previous attempt I used QMK Toolbox for uploading the firmware on Caterina ProM1cro bootloader, but I've some confidence with AVR Dude too, when something goes wrong with the QMK Toolbox. I'd be glad if you'd help me compile a QMK-VIAL firmware giving me the opportunity to give it a try. Let me know if you need some more info about the keyboard layout I'm going to use on my 2nd FEXT,
TIA
Cheers
TIA
Cheers
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Hi,
Many thanks to RICO (@geekhack) for creating the Leyden Jar !
I just ordered some 10 Leyden_Jar boards from, JLCPCB.
I am programming extra features in my xwhatsit controllers and I literally reached the limits of the atmega32u2 (size 28460. max 28672)
Ordering was not difficult.
Step 1 - Order now - PARTS NOT AVAILABLE
- First I load the geber file
- I specified that they should solder the components (two changes from the default a) number of PCBs b) mounting the components)
- I loaded the BOM and CPL files in the next page
- I received a WARNING ! They did not have in stock all the components
Step 2 - ORDERING THE PARTS IN ADVANCE. Building my own stock.
I went back to "my username" -> parts manager -> BOM tool and loaded the BOM file
- This allowed me to "pre-order" the parts. Those missing were ordered in some days.
- I had to pay for these parts first
Step 3 - Wait for the parts to arrive
- I received an email for each part.
Step 4 - Order now - ALL PARTS AVAILABLE
- First I load the geber file
- I specified that they should solder the components (two changes from the default a) number of PCBs b) mounting the components)
- I loaded the BOM and CPL files in the next page
- Order and pay the PCB production and mounting them
All in all I paid some 107 euros including taxes and shipping to Europe. Some 10 euros per PCB.
FYI: Ellipse charges $49 + shipping loaded with the firmware, I guess
lets see how they work ... I may have made a mistake in the order
Many thanks to RICO (@geekhack) for creating the Leyden Jar !
I just ordered some 10 Leyden_Jar boards from, JLCPCB.
I am programming extra features in my xwhatsit controllers and I literally reached the limits of the atmega32u2 (size 28460. max 28672)
Spoiler:
Step 1 - Order now - PARTS NOT AVAILABLE
- First I load the geber file
- I specified that they should solder the components (two changes from the default a) number of PCBs b) mounting the components)
- I loaded the BOM and CPL files in the next page
- I received a WARNING ! They did not have in stock all the components
Step 2 - ORDERING THE PARTS IN ADVANCE. Building my own stock.
I went back to "my username" -> parts manager -> BOM tool and loaded the BOM file
- This allowed me to "pre-order" the parts. Those missing were ordered in some days.
- I had to pay for these parts first
Step 3 - Wait for the parts to arrive
- I received an email for each part.
Step 4 - Order now - ALL PARTS AVAILABLE
- First I load the geber file
- I specified that they should solder the components (two changes from the default a) number of PCBs b) mounting the components)
- I loaded the BOM and CPL files in the next page
- Order and pay the PCB production and mounting them
All in all I paid some 107 euros including taxes and shipping to Europe. Some 10 euros per PCB.
FYI: Ellipse charges $49 + shipping loaded with the firmware, I guess
lets see how they work ... I may have made a mistake in the order
Last edited by idollar on 30 Jul 2024, 21:40, edited 1 time in total.
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
The Leyden_Jar boards from JLCPCB have arrived. Customs was not easy this time in Germany but they eventually arrived home.
I am typing this post with a FSSK (the very first v1.0 FSSK) upgraded to Leyden Jar controller !
The installation was simple but for the following:
- I had to compile a VIAL Firmware with the correct layout.
- using the test tool from Rico, I could solve a couple of issues and ...
- figure out the offset required for the threshold in
Code: Select all
#define ACTIVATION_OFFSETS {20,20}Code: Select all
keyboards/leyden_jar/fssk_idollar_v1r0/config.h - also, I had to isolate the keyboard PCB (capacitors) from the metal plate to ensure that there was not contact to ground.
- finally, it seems that the large mounting hole on the left of the board, looking at it with the components on the top, is not connected to the ground. I had to use the right pad to create a good ground keyboards/leyden_jar/fssk_idollar_v1r0/config.hconnection.
Thanks again RICO (@geekhack)
LeydenJar:
- Rico's code: https://github.com/mymakercorner/vial-qmk/
- Rico's PCB: https://github.com/mymakercorner/Leyden ... controller
i$
Last edited by idollar on 30 Jul 2024, 21:39, edited 1 time in total.
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
The next steps with my endevour the Leyden Jar are:
- Install the controllers in all my others Fs
- Figure out how to use I2C to light some indicator LEDs under my main boards to show layer status
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Hi,
I post a spoiler of the posts which I plan in the next days once the work is completed to my satisfaction.
You may know that I have replaced the xwhatsit controller in my FSSKs with the wonderful Leyden-Jar designed by Rico. I just use these keyboards to type.
The RP2040 MCU used in the Leyden-Kar controller is much faster. It also has more storage space which allows to update the firmware as needed. I compiled Rico's firmware to include QMK & VIAL. (reference: https://github.com/mymakercorner/Leyden_Jar)
Rico has exposed the i2c interface in his controller. This allows to solve the only issue that I found in the SSK: these keyboards miss the status LEDs. It is possible to use the i2c interface to add an OLED display, supported by QMK. The question was, how to integrate it ... the answer is 3d printing and Fusion360.
In the attached you can find the first prototype which I completed last weekend.
By mistake I purchased blue OLED displays which I do not like. They need to be white.
Also, I plan to properly finish the 3d part and paint to a colour closer to the original SSK case.
I will post the progress on this project. I just need to find the time to continue.
Until then ... let me know your comments/suggestions.
Cheers
Note: forgive the quality of the pictures, I used the telephone.
Note2: disregard the content of the LED in the picture. It was just a test using a library from a LadisPad which I have.
i$
I post a spoiler of the posts which I plan in the next days once the work is completed to my satisfaction.
You may know that I have replaced the xwhatsit controller in my FSSKs with the wonderful Leyden-Jar designed by Rico. I just use these keyboards to type.
The RP2040 MCU used in the Leyden-Kar controller is much faster. It also has more storage space which allows to update the firmware as needed. I compiled Rico's firmware to include QMK & VIAL. (reference: https://github.com/mymakercorner/Leyden_Jar)
Rico has exposed the i2c interface in his controller. This allows to solve the only issue that I found in the SSK: these keyboards miss the status LEDs. It is possible to use the i2c interface to add an OLED display, supported by QMK. The question was, how to integrate it ... the answer is 3d printing and Fusion360.
In the attached you can find the first prototype which I completed last weekend.
By mistake I purchased blue OLED displays which I do not like. They need to be white.
Also, I plan to properly finish the 3d part and paint to a colour closer to the original SSK case.
I will post the progress on this project. I just need to find the time to continue.
Until then ... let me know your comments/suggestions.
Cheers
Note: forgive the quality of the pictures, I used the telephone.
Note2: disregard the content of the LED in the picture. It was just a test using a library from a LadisPad which I have.
i$
- Attachments
-
- OLED 3.jpeg (170.65 KiB) Viewed 576 times
-
- OLED 4.jpeg (108.88 KiB) Viewed 576 times
-
- OLED 2.jpeg (160.28 KiB) Viewed 576 times
-
- OLED 1.jpeg (197.16 KiB) Viewed 576 times
-
- OLED a.jpeg (169.63 KiB) Viewed 576 times
-
- OLED b.jpeg (196.53 KiB) Viewed 576 times
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
Hi,
Following some proper pictures on how the printout looks in white.
I should finish and paint the parts.
Cheers
i$
Following some proper pictures on how the printout looks in white.
I should finish and paint the parts.
- DSCF0298-small.jpg (1.42 MiB) Viewed 525 times
- DSCF0304-small.jpg (864.93 KiB) Viewed 525 times
- DSCF0303-small.jpg (839.45 KiB) Viewed 525 times
- DSCF0302-small.jpg (475.57 KiB) Viewed 525 times
Cheers
i$
Last edited by idollar on 22 Nov 2024, 10:15, edited 2 times in total.
-
idollar
- i$
- Location: Germany (Frankfurt area)
- Main keyboard: IBM F or M
- Favorite switch: BS
- DT Pro Member: -
In the case that anyone wants to upgrade to the Leyden-Jar their real fssk, and perhaps add the oled screen, send me a PM.
We will find a way to send you the 3D files, instructions etc ...
We will find a way to send you the 3D files, instructions etc ...