@justRobsi this sounds like a power issue. When installing packages the wifi radio is working to download the files, the CPU is writing the download to RAM, etc. There's a lot going on so the power draw increases significantly and sharply. To get over this hurdle during development, I recommend either: Using an Omega2S Development Kit - it allows for swapping Omega2S modules and has the required power circuit Getting a (through-hole) Omega2 or Omega2+ and a Dock for your development - this will eliminate any power supply issues And then when making your own circuit to power the Omega2S, please refer to the Omega2S Hardware Design Guide and the Omega2S reference schematic

@Zheng-Han You should simple provide some checksum file for each img (bin) file in the repo.

[SOLVED] I found out the servo is discontinued. I think it has flaws in its design. I can't explain why it sort of works (only one direction) from the USB thing and does not from the expansion board, but I got 2 different newer winch servos and they work great in both directions from Onion and my USB thing, so it has to be a faulty servo. I have a feeling it had a 1 to 3 turn limit before breaking a cog if it driven past that, then once the cog is broken the pot doesn't return the right values and its all screwed up. Anyway the expansion board seems pretty bullet proof for noise and EMI EMF, I man handled it pretty good.

Have you tried to do a factory reset thru console command ... plus you might need to downgrade it thru serial ... download an older image and install it using .. sysupgrade -f image.bin

For anyone having the same issue, I believe I solved the issue after some tweaking. The issue seems to be that I wasn't setting pin 3 to be input before trying to read from it. Adding the line os.system("gpioctl dirin 3") solved the crashing issue. Alternatively you could replace gpioctl dirin 3 with fast-gpio set-input 3. I'm a little concerned that the error wasn't handled better. I don't know if that fault is on Python or my Omega2, though. Anyways, happy coding everyone!

Well, After some experimentation: root@Omega-BF4F:/usr/bin/onion-node-red/node_modules/node-red# node --max_old_space_size=768 red.js Seems to do the trick just fine, allthough i find it somewhat weird that node.js is not able to alocate the memory from the box but ow well Regards, Leo

@Lazar-Demin - It is definitely running out of memory, but if I remember correctly I boiled my code down to just a loop checking the state of the gpio, after of course initializing it the way I wanted to use it. Hey @Kit-Bishop, Firstly thanks for the code! Yes the code that I tried after running into issues with my own, was yours. My tests might be out of date because im using a version of code that is still using file writing (/sys/class/gpio/gpioX) to export, read value, and change direction. Where as there is a different gpio class that you have that actually writes directly to the register, like fast-gpio. But i think that class is written in C/C++ and does not have a nodejs addon. Please correct me if I am wrong there. I am new to the Omega and microcontrollers in general, and well I can only tell you what I see and know because I don't know anyone else using this platform.