Ah ok j’ai compris 
Du coup je m’installe un mini pc très basic style Atom à coté de ma baie, je la connecte en reseau, j’installe ce petit programme, et du coup j’accède depuis le vrai programme velbus en reseau depuis n’importe quel pc
Génial, voilà une idée qu’elle est bonne !
Exact !
let’s continue in english (for all users of Velbus system).
[size=150]Here is version 3.01 ![/size]
Filtering is enhanced and some bugs were removed : see golfy.olympe.in/PB_Velbus-Server_3_manual.pdf for release notes and manual
Download link : golfy.olympe.in/PB_Velbus-server.exe
And now, here is the official site for PB_Velbus-server and VelbusCmd projects :
golfy.olympe.in/Teo-Tea
[size=150]Here is version 3.02 ![/size]
Bug fixed : show all kind of bad frames (before, displaying only bad checksum frames)
This version is ideal for debugging your own application.
Download : golfy.free.fr/Velbus/PB_Velbus-Server/PB_Velbus-server.exe (v3.0.2)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.1)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes)
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
As always, your feedback are welcome
[size=150]Here is version 3.03 ![/size]
Added : bandwidth graph (RX is Velbus received frame, TX is Ethernet received frame… all from server view of course)
This version is ideal for debugging your own application.
Download : golfy.free.fr/Velbus/PB_Velbus-Server/PB_Velbus-server.exe (v3.0.3)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.3)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes)
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
As always, your feedback are welcome : are you using it ? have you any problem ? is it stable or unstable ?..
[size=150]version 3.04 : minor enhancement ![/size]
Added : Coloring velbus frame depend of priority frame (light green is High or special, normal green is Normal)
Added : Source address has been added to “source” field
Added : Serial port number and Ethernet port are displayed in statusbar (better for troubleshooting)
This version is stable release.
http://golfy.olympe.in/PB_Velbus-server_3.04.png
Download : golfy.free.fr/Velbus/PB_Velbus-Server/PB_Velbus-server.exe (v3.0.4)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.4)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes)
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
**As I’ve no feedback, I don’t know if it’s useful for you ** : should I continue to publish it here (Velbus forum) ? Are you waiting for other function ? don’t hesitate to post here…
Hi Golfy,
I want to give this version a try, but I’m not able to run it: I’m seeing a popup “Not able to find velbus hardware”.
Should I fill in a com port nr somewhere?
I can’t download the user manual: server is unavailable.
thanks!
[quote=“GertSt”]Hi Golfy,
I want to give this version a try, but I’m not able to run it: I’m seeing a popup “Not able to find velbus hardware”.
Should I fill in a com port nr somewhere?
I can’t download the user manual: server is unavailable.
thanks![/quote]
Just create a text file named PB_Velbus-server.ini
1st line is COMx
2nd line is network port
At my home, it’s
COM6
8080
That’s all.
[size=150]version 3.05 : great enhancement ![/size]
**Added **: decrypting function. It permit to show some kind of messages (Memory transfert, Temp Request, etc.) from Velbus Bus or Ethernet apps (which communicate to Velbus). Warning: some description aren’t accurate (because some frames are contextual). It would be use for development’s user but could be a way to study the Velbus protocol
**Added **: ini file initialization (GertSt: you don’t have to create manually the ini file). At first launch, PB_Velbus-server search for ini file, else, it asks for right parameters (and checks them).
This version is stable release.
http://golfy.olympe.in/PB_Velbus-server_3.05.png
Download : golfy.free.fr/Velbus/PB_Velbus-Server/PB_Velbus-server.exe (v3.0.5)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.5)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes)
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
Small Enhancement, always same place
**Have a good 2013 year with lot of funny Velbus projects **
golfy.olympe.in/Teo-Tea/2013/01/ … treatment/
http://golfy.olympe.in/Teo-Tea/wp-content/uploads/2013/01/PB_Velbus-server_3.06.png
Download : golfy.free.fr/Velbus/PB_Velbus-S … server.exe (v3.0.6)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.6)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes (not updated since long time))
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
Bonjour et bonne année.
Je pense à un truc Golfy qui serait tout simplement énorme;
Je ne sais pas si tu connais les NAS synology.
Une version de ton serveur instalable sur un nas synology serait parfaite
Avoir un petit serveur Nas, qui sert à tout (en particulier médiathèque), mais qui en plus pourrait s’occuper de vellbus, pour le partager en réseau…
Et en poussant le luxe, on pourrait même imaginer plus tard une interface simplifiée sur le nas, permettant de contrôler basiment les interupteurs et de voir par exemple la température.
Si je programmais, je me lancerais sans hésiter, mais j’y connais rien 
les NAS Synology semble utiliser du PHP…
synology.fr/support/faq_show … 4&lang=fre
pour ma part, mon application est compilé pour Windows (et potentiellement pour Linux, si j’arrive à faire marcher Purebasic sur mon Linux virtualisé).
Ils proposent PHP pour les usages “web”, mais c’est du linux derrière.
Donc si vous arrivez à faire marcher votre appli sous linux, pas impossible qu’elle soit utilisable sur un nas.
Faut savoir que les syno sont accessibles en root, en SSH.
Donc ca doit être installable et executable à ce niveau peut être.
Voir ici : synology.fr/support/3rd_part … p?lang=fre
is this program working with homecenter?
I don’t know how HomeCenter is working. Consider this program as converting Velbus Logical protocol into Ethernet Logical protocol (with IP addresses) : frame still in RAW format but encapsulated in Ethernet frame !
3.07 is a Major bugfix !
interface still the same as 3.06 but in some case, frames from Velbus bus to Ethernet network were not transmitted
version 3.07 correct this plus a minor enhancement for name display in log detail (no more strange characters)
http://golfy.olympe.in/Teo-Tea/wp-content/uploads/2013/01/PB_Velbus-server_3.06.png
Download : golfy.free.fr/Velbus/PB_Velbus-S … server.exe (v3.0.7)
Download : golfy.olympe.in/PB_Velbus-server.exe (v3.0.7)
Manual : golfy.olympe.in/PB_Velbus-Server_3_manual.pdf (manual and release notes (greatly updated))
official site for PB_Velbus-server and VelbusCmd projects : golfy.olympe.in/Teo-Tea
Thanks for sharing!
By the way, I need help from** Linux** users
could you please try this ?
golfy.free.fr/Velbus/PB_Velbus-S … server.exe
or
golfy.free.fr/Velbus/PB_Velbus-S … server.zip
It’s the 3.08 version compiled under LinuxMint 13 (64 bits).
Feedback, screenshots and other information are welcome *
i tested it on
Linux desktop 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
this and here it seems to work
one tip thought, a linux program is not called .exe
but i can not use it connected to my velbus system, as my server does not have a gui installed at home, and my velbus is connected to this system, that also the reason why i still use jeroends c server, as this one just runs in the background, no gui needed.
I can not test this at the moment since I have no 64 bit version of linux running at this time. Also as Cereal said, a graphical environment is needed to run this. As the most stable linux servers don’t run in an graphical mode, this is not very interresting (by the way, it’s never interresting to have a server running in a graphical mode since this takes a lot of processing power away only to see some visuals + could make the system more instable).
Also an other notice, some of the (embedded) boards I’m working on even don’t have a video out, or aren’t meant to use with a display (for ex. the olimex olinuxino imx233 or the a13 micro).
If you want to have your server app running stable, you’ll have to split it up in 2 parts. The “real” server part, which takes care of the connections an distribution of the velbus packets and is a console app that runs in the background. The visualisation part, which would be optional and has only no more to do as connecting to the server part and to do some visuals. This as reason that when the visual part crashes the whole system doesn’t goes down and it will be usable to users that don’t use a display.
Why is it so interresting to use embedded boards with no display: simply because they are so low power consuming, very stable and there are boards that will fit in a din rail enclosure (look for ex at tuxrail from busware.de). For domogik I’d recommend using a rasperry pi at this time since the other boards don’t have enough memory (waiting for other boards to try out, but the last few months I didn’t had the time at all).
So, I hope this is a bit more clear why your app isn’t that interresting on linux at this time, yet it looks very promessing on windows.
ps: another advantage when splitting up your app, you could have the server part running at a linux station (for ex.) and have the front app (the monitoring part) still running in windows (I’m not doing everything in linux btw ;-))
yeah if you could split the application to a backend (tcp to serial) and the gui (connecting over tcp to teh backend) i would be verry interested in the gui, but same for jeroen, my velbus connection is linked to a headless setup