Arduino SPI RAM II


Hello there!

KiLLA’s got some new stuff to share ;-)

I have plans to use most of these ICs @ 12MHz SPI so i made proper shield instead of breadboard because some guy found it too noisy to work properly that way(link at bottom).
The shield is drilled a bit off axis as i did make it fast with 550W handheld drill :-P

First tests with built in libraries reach sort of low speeds, probably due to latency growing with bus speed, getting ~20kB/s with byte transfer for both writing and reading @ 12MHz and ~50kB/s for 4MHz SPI :roll:

23LCV512-I/P 64kx8bit SRAM 20MHz SPI – TESTED WORKING up to 12MHz
IP12B256I-TU 32kx8bit SRAM 20MHz SPI
IP12B512C-TU 64kx8bit SRAM 20MHz SPI

# do some more tests..speed!!!
# find fastest library or make own, this guy juiced off ~120kB/s

usefull info:

the noisy guy:

microchip 23xx spi pinout:

Serial NVSRAM Circuit Diagram

Simplest SRAM library i found:

SRAM library:

This library example compiles, but throws errors on serial monitor running on Arduino:

Ion Chamber


I’m interested in unusual things, so.. I MUST HAVE THIS!!! 8-)

Found tons of articles, noob videos and so on, so i picked one i like for testing..
Minor side note on sensitivity: IF THIS DETECTS SOMETHING(>10cm), RUN FOR YOUR LIFE!

Source of schematics:


Current state: waiting for better sources of radiation

Further plans:
# make new completely surface mounted flat PCB
# insulate components side and use thermal conductive glue to fix metal sheet on top

why??? because the 4117 JFET has some nice pictures in datasheet describing behavior @ -55°C :-D
and how do we get to -55°C??? LN2??? :-D

# place it on 48W peltier with 125w heatpipe cooler
# make some cool testing
# make some more pieces of THT version boosted with Arduino counter + SSD1306 OLED + cool gauges

Arduino & stepper 28byj-48


..there are tons of articles about this stepper..
..this is simplest solution i found.. there are few mistakes in the code, but i like it..

i did lol on whole thread how the guys grew up the code and made it far more complex
with weird function names for motor movement as well :-D
they forgot that Arduinos have only 2KB SRAM(most of units sold) for whole project
so we cannot spent huge part of it to make work single part :-D

the idea of the original code is far better than the complex mess from the coolguys..
its not generally wrong to use digitalWrite and its not necessary to use direct port manipulation like tha guys recommended because of the sequential type of the movement..

main problem of the original code is that there is attempt to be correct and make steps somewhat aligned to time with 4x digitalWrite in a row so it delays the desired change of state by variable but repeating amount of time :-D
correct is that there is just one change per the substep and make timing between these same way as datasheet says..
to be fine we must also introduce possibility to add sort of delay between the steps with all coils off as the original code makes stepper pretty hot after a while of high speed..

we should also care of full step and wave drive techniques so we can reach higher speeds than with halfsteps in the original code.. meh..

also i did get from 190 bytes of precious SRAM usage(serialPrint and so on) of the original code(not to mention the coolguys memory bombz lol) to 9 bytes (!) least for working code and 11 bytes in my „light“ version with no precise timing, just the steps and sort of „speed“ (aka delay) :-D
with timing mem usage is somewhat higher because of storing time variables as float type..
this can be partially lowered as we can fiddle with memory storing.. :-D


here is version 0.9.0 beta for testing.. eats 11Bytes of SRAM :-D
+ half steps both directions
+++ wave drive!!!
+ ability to set speed
+ full torque for testing

* be cautious with the testing full torque halfstep function, theres need to use stepper_sleep() func after >ending< sequence of these or even single step to turn coils off -> less heat.. its not used in demo code in loop() section. you have to add call to that func to test.. also its good to call stepper_sleep() before to ensure that all OUTs are LOW..

10.4.2017 - 18.43
10.47 kB

LAN over non-twisted cable experiment part.1


I was quite sure that this wont work, but we have been forced to try.. Not that much.. :-P
Normally the LAN is got over FTP and UTP cables, aka the twisted ones.. Yeah, the twisted wires.. Or even twisted pairs of twisted wires.. Cat6e has 6 twists per inch..
But using old 12 x 1.5mm² AC mains cable with no twists which is 20 to 30 meters long, is under ground and dated to late 70′s or 80′s must fail..or..?


why this could work?
1st: i used only 10Mb/s mode
2nd: we were totally lucky

update 2/2017: i will be finishing this project soon!

New corporate system app

Last month i have been asked to code program to my work..
It took huge amounts of time.. but.. it was fun to hack Windoze :-D

what does it do:

  • after starting Win7 and login to username the desktop is not showed & our IS is started and held fullscreen
  • checks for our IS running, if its shutdown by user our app asks for pass or restarts it
  • hotkey to invoke our login / logout to system with timeout of 10min to login again
  • while user is logged in an unmovable & switchable window shows rest of time until next login window appears
  • checks for instances of web browsers (IE, Opera, Chrome, Mozilla) and asks for pass to our login or quits them
  • checks for instances of autoruns etc. and kills them so absolutely no way computer can be penetrated from local user
  • switching keyboard language via hotkey or automated because our IS needs EN keyset
  • is able to disable itself while certain user is logged in Win7 and enable again at logout
  • verbose logging to both local and remote files over network
  • ability to control TeamViewer QuickSupport executable and send its login over network  (dropped due to uncommon / unknown licensing until it gets clear)
  • overlay debugging window via hotkey

recent version source code has size of ~30kB

GLXgears on various OS

..Windows may look quite good in chart, but gears were choppy and had huge tearing.. Linux based systems performed smooth with no vsync.. Nouveau driver has kinda slow 3D yet..