Undefined - Fujitsu Esprimo E3510 - 3

Took another look at the old Fujitsu again last saturday. Got a VGA cable for the monitor, turned it on, and... nothing. Well, almost nothing. The computer beeped twice after about half a minute. No video output, nothing. I removed the keyboard, cd drive, hard drive, until only the monitor, CPU, and RAM were left. Nothing, two beeps. I removed the RAM sticks, booted with only one stick (tried both sticks, both slots). It wouldn't POST.

Apparently, these beeps are a code, meant to tell you what is wrong. Kind of. The beep code that I got means "parity circuit failure", which seems to have something to do with either the RAM or the motherboard. Since one of the RAM sticks originally came with the case and the other one was brand new, I don't think either of them are the problem. The motherboard may be faulty. Not really looking forward to having to buy new things.

7 december 2021

Update: the android app still doesn't work. Every time I implement something new, I have to learn a whole new set of classes. What the hell are classes, objects and instances anyway? Wish I could do this in C or something.

At least I'm making progress on my industrial automation project. Part of it concerns a machine vision application. Was given a license for Halcon with its somewhat user-unfriendly interface, tried to do it in OpenCV instead, got in a heated discussion with Visual Studio when I tried to install the libraries, went back to Halcon, remembered that the project had a bunch of requirements I never even looked at, heard that a classmate had figured out how to meet one of the requirements perfectly in Halcon.
The requirement? We have to use the OPC-UA protocol for transferring data. A PLCNext (like a PLC, but worse) acts as an OPC-UA server, so any external system should be a client. Luckily, Halcon has operators (functions or methods) to connect to an OPC-UA server. It worked in the end, but only if I turned off user authentication (removed all passwords and safety measures) on the PLC. So much for cybersecurity.