
This blog has reached its end of life. I will instead post updates on VSCP matters in the VSCP discussion area from now on. See you there.

This blog has reached its end of life. I will instead post updates on VSCP matters in the VSCP discussion area from now on. See you there.
Just turned 70 early this month. How did that happen? I dont know. But I am still kicking. Oh well, slightly… But think more and more about the future. I will not be around for ever, but will VSCP? Don’t know how to solve that. Trying to figure that out, if it is worth the effort or not to find a solution. Thoughts on this are welcome.
Still working all day with VSCP. Still a lot to do. Or “still a lot I would like to do” is more correct. Claude and Copilot have lately come to my help. Great friends, work hard if I just ask them. No need even to ask politely. Speed a lot of things up, and I think Claude writes better code than most of us do nowadays.
Well, AI usage cost a lot of money. Fight with that every day now. Spend way to much on it. I guess that the limiting factor for most open source projects when you accept this to be a valuable tool just as a wrench is in other areas.
Want to share some things that have happend latley
Well, thats it for today. Have fun!
The latest release of the vscp-firmware repository has a breaking change that will reflect a lot of software/firmware depending on it. In this release the “common” folder has changed name to “src” to be consistent with the rest of the repositories.
Also the version format is now year.month.patch. This will also be used everywhere except for vscp-helper-lib and other libs where a change in the major-version means a breaking change, a change in the minor-version additions and bug fixes and version-patch is updated for every update.

VSCP. So many repositories. So many releases. Now in the VSCP wiki I will keep a list of all releases here

After a few fantastic days at the keyboard (you know how it is when everything just flows), I’m sitting here grinning. Satisfied, really.
The new daemon/server (vscp-tcpip-daemon) for the VSCP Link protocol, which will live alongside vscp-mqtt-daemon, runs on Linux, Windows and macOS just like its cousin. It’s essentially the old VSCP daemon/server in a more stripped-down form. If and when time allows, all the functions of the old one will return in the form of drivers. Much of it is already there, but some of that code is pretty shaky and needs a review.
If this were a team, this would be the kind of moment where you’d head into town to celebrate. Grinning together is always better than celebrating alone on your hill. But here I am, on my own. I did get a few cookies with my coffee, though. And if you like cookies, as I do, that’s not so bad either.
A note: your message contained the whole text twice, so I translated it once. Also, “kubb” is left as is, since I’m not certain which sense you mean (it’s also the name of the Swedish lawn game). If you meant a sweet or treat, “a few pieces” would work.

When you start the game of being a programmer it is common to point fingers on others when something goes wrong. When you been in the game for some time you end up in the other end always thinking the problem is on your side.
So I have looked into this problem of mine for almost a week now. Harden code and tested, tested, tested. The problems is intermittent so it takes a very long time to debug.
So
kernel: ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback – urb stopped: -32
is spotted in the logs. The problem sits in the USB <-> serial adapter.
Well well… Found it eventually. NOT my fault. Possibly somewhat responsible for having bought cheap USB<->serial adapters from China, though. This is when you wish you worked at a bigger company so you could point the finger at someone else…. 🙂 But when it’s just you, you obviously can’t do that. You’re stuck standing there. Gotta fix it yourself.
Swapping the adapter is of course the obvious solution. But it would be even nicer if you could detect this in the driver and account for it. I’ll probably start down that road.
We’ll see how it goes.
Still searching for the problem with the serial data from the measurement system
No server admin would be happy about something like this. But here, I’m the one who decides, and I like it. Or, if truth be told, maybe I don’t like it that much either, but if I eventually get some kind of clue from this, I might even end up loving it.
For anyone curious, it’s (among other things) the value below that flies by

The art of making the simple complicated, basically. That’s kind of my job, in a way. You have to imagine that counter is sitting in an industrial environment on the other side of the globe. If you want to try to understand why everything has to be so damn complicated, you just have to stick your head in a bucket and go “hmmmm… and wonder about it all“
Well, 26 years today, counting from when the project was uploaded to Sourceforge as ‘EDA-Simple Service Gateway.‘ Doesn’t mean anything, of course. One more year in the service of the sand art [i.e., in the spirit of Buddhist sand mandalas — impermanent by nature]. Pretty happy with that!
Had the exact same thought earlier today. Where does the fun (and the driving force within) go?