Is anyone else seeing this recently?
Currently using Velbuslink 11.9.6 and I have been seeing this a while, certainly the last few versions.
I had thought it might be the “save” before quitting that was doing it but I can confirm it happens even if I save my configuration before I exit.
I should add, apart from the crash at exit everything else works fine… a .vlp save happening on exit works OK, nothing obvious gets corrupted.
Same experience, seems to occur especially after broken connection to canBus (e.g. after PC sleep).
Yes, this is a known bug with the later versions.
More importantly, is anyone suffering as a result of it?
From what I’m told, it’ll be addressed in the next major (very major) update.
Not a big deal for me …
Not a big deal for me either. It doesn’t seem to break anything.
Same here, keeps crashing. No big deal, but if I were a new user crashing software gives -10 to the confidence in the system. I hope it will be fixed soon. Or we will see the open source VelbusLink and I’ll fix it 
Open Velbuslink (… managed by Velleman) would be nice
Or we will see the open source VelbusLink
I cannot let that comment go without adding a +1 here. That would be great.
But I can understand that Velleman might be very wary of that. It is probably a (too) big step?
I am aware that host/edit software probably needs serious consideration for Mac and Linux support also. The embedded software developer world is still very Windows biased because of legacy issues but there are signs that is changing… more and more are going Linux and Mac and multi-host and open tools.
Hi all,
Just to add some context from our side: we are indeed aware of this issue. Unfortunately, it’s one of those bugs that is quite tricky to track down.
The good news is that this behavior has no impact on your VelbusLink project files or configuration. The issue is purely cosmetic and only occurs when exiting the application. There is no functional risk and no data loss involved.
We understand that it can be frustrating to encounter issues like this, especially in a tool that has been around for a long time. Rest assured, it is on our radar, but our priority remains stability and compatibility for existing installations.
We also appreciate the interest and discussion around a more open VelbusLink solution. As a small sneak preview: this year — and certainly moving into next year — we plan to start working towards a new, cross-platform VelbusLink, running directly in the browser. The goal is to support local hosting, Signum-based hosting, and cloud-based access.
Needless to say, this is not a short-term effort. It involves rethinking and modernising close to 20 years of existing code, while ensuring full backward compatibility. That requires careful planning and time. Of course, while working on this new platform, we will continue to maintain and make incremental improvements to the current VelbusLink where needed.
A more open or extensible approach is definitely something we are considering as part of that future, as it can only strengthen the Velbus ecosystem. More details will follow once things become more concrete — so no weekly update requests just yet .
Thanks for the constructive feedback and the discussion.
Regards
Thank you very much for the info! It sound very interesting….but….a browser version means stuff on some external servers? Or everything-local solution? Anyway, if you need alpha/beta testers - keep me on the list please.
P.S. I don’t know what source management software you use, but debugging a consistent error (the exit crash) with granular commits on git is fairly straightforward…. on solid systems like linux
Even as we move towards a browser-based solution, we will always keep a local installation option available. This allows users to connect directly via USB, which is important because many Velbus installations do not yet have a fully configured network at the time of installation.
We’ll keep you posted on this forum once an alpha build is available for early testers, although this won’t be happening anytime soon.
Interesting… Yesterday I ran VelbusLink 11.9.7 to add some (long press to us pre-set dim) to some lights. This all worked fine but VelbusLink crashed on exit.
Today I noticed that task manager shows that a process (but not the application) “Velbus Configuration Software (32 bit)” is still running, using 1.34MB memory, and using a steady 6% of CPU (which sounds like 1 core, as my PC has 16).
So I killed the process in task manager and it has now gone… but I wonder what it was doing?
I am not particularly worried, just thought it was odd and maybe worth mentioning.
Can you add that to a help ticket please?
Oops. Sorry for delay.
Done now. #30411
