the older ones via xml i think. The newest have them build in to the module if i’m right. read it on this forum.
hope this helps
stis
Hi,
Velbus 7 software had some xml files that contained the memorymaps of certain module.
These where only the memorymaps.
It would be nice if you could create you own devices in the next velbus software.
This could be done through a library with (xml)files for every module.
To create a custom device you could choose out of certain standard components like pushbuttons, dimmerchannels, relaychannels, sliders, …
In that way i can create several new modules an intergate them in the velbus software.
I’m not a dot net wiz, so a simple XML module file would be great.
Regards,
Jeroen.
Hi,
Any news on the my feature request ?
Regards,
Jeroen.
That will probably never happen, it is simply too complex
Hi,
I could read values and show them on a display and send commands to the velbus.
Last thing i did was looking at the memory maps but i did not finish this project due to not enough time/other projects.
I guess i will start over this winter.
Regards,
jeroen.
cool,
can you post your docu somewhere on how you did it?
would really be halpfull as i was thinking of writing an IR sender that hooks onto velbus …
I would be interested as well! 8)
Hi guys,
Sorry for the late reply.
If you are interrested in the mbasic code, just send me an email (not sure if it’s visible in my profile).
You need a PIC 18F2480 (or similar), an MCP2551, an LCD (4x20), some pushbuttons and some resistors.
Regards,
Jeroen.
no email in the profile 
Hi,
Just send an email to jeroen.hollemans(at)telenet.be
Regards,
Jeroen.
Time to do some prototyping 
I’m going to try to put someting together with a full color display, preferably OLED like the new Niko modules.
Compared to the display of the VMB4PD the latter looks ancient…
For example:
http://www.nikohomecontrol.be/assets/images/product/knop-16.jpg
The VMBLCDWB looks promising but I think 199€ is a little steep…
Looks nice but oled displays are not that cheap.
There are some nice oled displays on the market that have a serial interface and an input for 5 buttons (joystick + push) from 4d systems.
Some of these models even have a touch sensor over the display.
It would be nice if the whole timer and date activated functions would be programmable like a simple heating thermostat (programming on the wall device in a graphical way/visual timeline.)
You could make schedules and apply these to certain actions or action groups.
So for the whishlist. (I’m sure i can come up with some other things)
Regards,
Jeroen.
Hai,
Did anyone of you get the CAN interface chip MCP2515 working? I am having troubles getting reliable data. I just posted in another thread (sorry, overlooked this one).
My data is shifted 1 bit (not byte) when longer data is send. For short messages, all is fine. I cannot find the correct MCP2515 settings to eliminated the shift.
Greetings Matthijs
Hi Matthijs,
This is an old topic and i stopped developing devices for velbus.
I can say that i used a PIC microcontroller with CAN interface + CAN Tranceiver MCP2551.
I had it working and I was able to read and write to the VELBUS so it is possible to create devices of your own.
One of my projects was a volume controller/digital potentiometer that was recognised by velbus as a dimmer.
Not sure if the PIC software was written in Basic or in C. Will have to look if i can find the old files.
Regards,
Jeroen.
Help would be appreaciated.
I have narrowed it down to a missing bit when more than 5 bits are send. So it has to do with bitstuffing but only in relation to the bytes “data length” and “1st data byte”.
Maybe I should buy a decent CAN to USB device and check again.
Greetings Matthijs
Hi matthijs,
Did you take a look at the protocol pages of VMB8PB fir instance ?
There you can find all the bits and what they stand for.
page 2
in one of my routines i did find a bitshift:
'----------------- Sub Procedures ---------------
sub procedure Velbus_To_Can_Address()
HighPrio_ID = Module_Address
<<HighPrio_ID
Firmware_ID = Module_Address
<<Firmware_ID
Firmware_ID = Firmware_ID + 0x0200
ThirthParty_ID = Module_Address
<<ThirthParty_ID
ThirthParty_ID = ThirthParty_ID + 0x0400
LowPrio_ID = Module_Address
<<LowPrio_ID
LowPrio_ID = LowPrio_ID + 0x0600
Also think of the fact that this was valid for the velbus version of 2013.
Regards,
Jeroen.
Thanks for helping.
I spent quite some time yesterday on the MCP2515. One of the conclusions is that I cannot retrieve the CRC bits from it, so there is no way to check the data and do any shifting if NOK.
Will fire up my STM32 and learn how to CAN with that one. See if I loose the sam bits or not and if I can get the CRC out of it.
Will keep you posted.
Greetings Matthijs
Yes!
STM32 + CAN is working. Now working on decoding the messages and creating a correct response.
Does anyone know if there is a “third party” device ID to use? Or should I just fake an existing module?
Decoding in action:
Greetings Matthijs
2 Likes
You can fake existing modules, it all depends on what values and functions you want to be able to send and receive from other devices.
A dimmer could also be used for a PWM dimmer for leds or for volume or tone control.
You could make your device to listen to multiple channels and combine on/off commands with values such as dimmer values.
Have fun experimenting with it.
Jeroen.