| Posted: Tuesday Mar 11th, 2014 04:46 pm |
|
1st Post |
popov
Member
| Joined: | Tuesday Mar 11th, 2014 |
| Location: | |
| Posts: | 5 |
| Status: |
Offline
|
back to top
|
Hello
i have pretty ince velbus setup with an VMB7IN module witch is used to interface presence detectors.
While evrything is working fine velbus is lacking of inteligence when it comes to do complex scenarios.
This why i want to use compfort logic engine to get messages form velbus and act as "Brain" to create scenarios.
My question is :
- will VMB7IN work with comfort (as its not listed in the doc
Regards
|
| Posted: Tuesday Mar 11th, 2014 05:21 pm |
|
2nd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
We do not support this at the moment
I believe it is a new product
Can you use the other Velbus input modules for the same function?
|
| Posted: Tuesday Mar 11th, 2014 05:32 pm |
|
3rd Post |
| Posted: Tuesday Mar 11th, 2014 05:55 pm |
|
4th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
certainly we will look at it but I know there are many many new modules in process in R&D, new versions of Cbus, KNX and PHC included so it may be some time
|
| Posted: Wednesday Mar 12th, 2014 01:13 pm |
|
5th Post |
wexfordman
UCM Pi Users
| Joined: | Monday Jan 1st, 2007 |
| Location: | Cork, Ireland |
| Posts: | 546 |
| Status: |
Offline
|
back to top
|
Might sound like I am simplifying things but is this not almost the same as the vmbp6in and would it mean very little changes required to add this module?
Comfort works very well with velbus, the logic engine almost sounds ideally suited for what the op wants.
|
| Posted: Wednesday Mar 12th, 2014 04:11 pm |
|
6th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Do you know what other new modules there are which are not supported?
|
| Posted: Wednesday Mar 12th, 2014 05:14 pm |
|
7th Post |
| Posted: Friday Mar 14th, 2014 06:59 pm |
|
8th Post |
popov
Member
| Joined: | Tuesday Mar 11th, 2014 |
| Location: | |
| Posts: | 5 |
| Status: |
Offline
|
back to top
|
Any hope to have a timeline for these ?
It would be great so i can already order the parts and wait for the new FW...
|
| Posted: Saturday Mar 15th, 2014 07:13 am |
|
9th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
back to top
|
The github code does not help much as it is a plug in for a certain software, which is not compatible to our embedded firmware
For systems like C-bus and KNX, all modules conform to a protocol so they can add or remove or change modules without affecting the interface to Comfort
For velbus every module has a slightly different protocol, so it is a problem if they remove or add modules. The UCM/Velbus firmware must be constantly updated which makes it difficult
So we cannot give you any timeline but we will try to look at the changes in protocol
|
| Posted: Monday Mar 17th, 2014 07:36 pm |
|
10th Post |
popov
Member
| Joined: | Tuesday Mar 11th, 2014 |
| Location: | |
| Posts: | 5 |
| Status: |
Offline
|
back to top
|
Hello
github do help as its a working example of new protocol implementation and it just give you the new codes and return values for new modules. So you dont have to read the documentation that is sometimes unaccurate .
The protocol does not realy change they do add new modules codes but this is not big changes the logic is the same.
regards
|
|
