A Novel Process

I invented a novel process improvement at work and the initial test results are promising, and warrant further investigation. This could end up being a big win for the company.

What makes a novel process improvement? Well I’m also working on a machine, and, although I won’t release any details, let’s say that it reduces the amount of rework required for a part of a manufacturing process. That makes the machine a process improvement, but it is not a novel process improvement, because we could pay other engineers to supply a machine that does the same thing. My machine may contain parts that are novel, but it’s not a novel process improvement.

In the case of my novel process improvement, there is no one else that can be paid to get you the same thing. Only Licap has it.

Busy, busy, busy…

I’m working mainly on a few exciting work projects these days. Mainly designing a new machine, also working with machine vendors on a new pilot line, and supporting maintenance and upgrades of existing machines, not to mention some forays into IT support.

Parts fab is at the forefront of my concerns at the moment: Do I print?, have printed?, have milled?, machine myself with or without CNC scribing? Or just all of the above? All of the above sounds right.

Cheap Aliexpress Nanos.

I got some arduino nano replicas on aliexpress a couple of months ago for an incredibly low price. Not surprisingly, there was a reason for the discount. The pin assignments as they’d be programmed in the IDE did not match the pins as they were silkscreened on the board. The analog pins were silkscreened in reverse order to their actual hardwired positions.

Thus, among the plethora of reasons that a device might end up super cheap on ali-x are manufacturing defects. This problem happenned to just be with the silkscreen, but the silkscreen is a very important time saver for circuit assembly.

Nevertheless, the board I used still helped me blast together a device to run an experiment and log data. The physical chemistry involved has been more problematic than anything else for that experiment, but a change in approach will eliminate all such problems.

My weekend exercise.

For the past several weekends I’ve been hiking up this canyon. It’s a little over 3.5 miles with 2.5 miles of gentle slope and one grueling high slope mile. It’s had some pleasing health benefits, and the view’s not so bad.

Computer Day

I spent the day researching and evaluating open source database solutions, and decided to upgrade from debian 9 to 10 again.

The biggest ooen source database communities are mysql and postgresql. I started out with mysql, and I chose the guaranteed free and open source mariadb variant. Mysql has a few good looking php generator tools to generate interfaces to gather and show the data to the users and has an admin tool called mysql workbench. I verified from the mariadb documentation that mariadb databases can be administered with mysql workbench and proceeded to install a mariadb server and mysql workbench. I set up a test database and got mysql workbench to connect to it, but there were many warnings. I went to set up a table in the database with mysql workbench and it kept throwing syntax errors in the autogenerated sql code. I couldn’t get it to stop without going in and editing the autogenerated code. That’s not what I’m looking for in a good database tool, and after I imagined having to do the same editing with every auto generated php interface file, I decided to give postgre a try. I suspect the issue has to do with mariadb and mysql compatibility, but I’d want to use mariadb rather than straight mysql.

Postgre is free and open source, and there is a free and opensource admin program called pgadmin. There are also php generator tools on the market to build interfaces, just as with mysql. So I purged all traces of mysql from my system and set up postgresql and pgadmin4. There was a problem with setting up the postgresql server, though an understandable one. Postgre doesn’t allow a user named “user.” I, of course, happened to be running a system in which the only non-root user is named “user.” And it happens that pgadmin has to be run in a browser, and for security reasons, firefox doesn’t permit being run as root. So I set up a new user with an actual name, migrated everything over, and finally deleted “user.” After setting up the new user, I get postgresql working and pgadmin4 working as well. I set up a test database, and used the admin tool to create test tables and there were no syntax problems. Easy. At least, it would have been if not for my ironic choice of user names.

Having replaced my user profile, and having noticed during software research that debian buster had been released as stable, I decided to go ahead and run the dist-upgrade. I’d actually had buster installed earlier in the year but I had reverted to stretch in an ultimately futile attempt to get monodevelop installed (a problem eventually solved with a windows virtual machine). It was a smooth upgrade with minimal complications. I mostly just had to go through the apt sources.list and sources.list.d and replace stretch with buster and 9 with 10, the one complication was having to replace a 9.0 with just a 10 rather than a 10.0.