Welcome to the world of OpenRemote with Velbus :-)
Please excuse the short answer, I'm supposed to be heading to a party, I'll reply again.
To get you going..
I don't think the online test function will ever be able to simulate your own Velbus network, so an Okay is the best you can hope for.
The only way to really see if your design works is to sync it with your local controller, so let's address that first :-)
(This might need the assistance of someone wiser than me on this subject)
As your using PB_Server, the default Velbus settings in OR should be fine
So you just need to get your controller up and running.
What messages do you get when you run the "openremote.bat run" command line?
Good luck,
Stuart
I also noticed that the port is being referenced is 8445.
Curiously, that is the same port that HomeCenter uses.
Is it a case that the default port of OpenRemote has been changed?
Good luck,
Stuart
By the looks of your screen dump your controller is running happily on port 8688.
You should be able to get the sync page by using
Sounds like you're making progress..
The "unable to connect" issue is something to do with the Controller connecting to the online beehive, it's nothing to worry about and won't affect your experience.
Search this group or the old forum for solutions.
Now, one observation about your Velbus connection is this...
Firstly, do you have a good (solid) reason for changing the default port of OpenRemote away from 8688?
And secondly, why do you choose ports that are in use by other software?
Port 8090 (and 8091) are the default ports for PB_Server, so I'll assume that OpenRemote must have started before PB_Server for it to take hold of port 8090?
Unless, you've also changed the default port of PB_Server too?
In which case, have you edited the Velbus connection details within the online designer?
(Then resync the controller to adopt the changes)
Please let us know how you get on.
Cheers,
Stuart
MDAR Ltd
Please take a look in..
../logs
You'll find plenty of folders and files in there with all kinds of information.
The ../logs/velbus/velbus.log file will show you if your getting a connection to PB_Server and if modules are initialised correctly.
On that subject, have you got the latest Velbus.jar file (V 1.2.2) ?
This added VMBDMI-R support.
There is another version on its way which will give support for the new VMBMETEO.
Thank you for your reaction. I will answer the questions
I have no reason to change to another port other than I wanted to try some possible solutions before bothering you in the forum. I thought it would help it use the Homecenter port, but it clear that it isn't.
I have no clue about 8090 and 8091 and how that happen.
I only had changed the discovery config in OR designer, port in server file on the pc , as explained in http://www.openremote.org/display/docs/Change+Controller+Default+Port
But I have changed everything back 8688 as you described.
I have used 1.2.2 jar file
The log file from now is added
So, I m not very helpful I think. If I can give any other information, just say what I can do
Richard
Op vrijdag 20 januari 2017 19:45:12 UTC+1 schreef Stuart Hanlon:
Thanks for the answers.
So everything should be back in order.
Now, according to your log file, it looks like your simply missing a connection to PB_Server.
This line is the key
"WARN 2017-01-20 16:38:21,843 (Velbus): Connection timed out: connect"
I'd double check that your settings are correct in the online designer.
/Modeller/Configuration/Velbus
Port should be whatever PB_Server is listening on, which is shown on the bottom status bar of PB_Server.
Please let me know the results so that I can help you get to the next stage.
Good luck.
Stuart
I'm very happy that you're up and running.
If you're looking to see how far you can go, you had better prepare for a very long journey :-)
The combination of OpenRemote and Velbus will give you far more options than you could wish for.
When you get any ideas that you're not sure how to realise, just create a thread on here or the Velbus forum :-)
Bon voyage :-)
Stuart
MDAR Ltd
I've just realised where I've seen your name before.....
https://openremote.github.io/archive-dotorg/forums/openremote%20and%20velbus.html
Thank you for staying with us :-)
Cheers,
Stuart
INFO 2017-01-31 18:04:32,515 (Velbus): Device is not reachable so not adding sensor - This means that the addressed module has not responded. INFO 2017-01-31 18:06:12,250 (Velbus): Device is not reachable so not adding sensor INFO 2017-01-31 18:13:31,171 (Velbus): Device is not reachable so not adding sensor INFO 2017-01-31 18:22:59,281 (Velbus): Device is not reachable so not adding sensor INFO 2017-01-31 18:26:16,812 (Velbus): java.io.IOException: TCP socket read error - I'm not certain, but I think this means that there was an issue between the OpenRemote controller and the Velbus TCP server (PB_Server in your case) INFO 2017-01-31 18:27:04,578 (Velbus): Scheduled bus connection task - This is a normal attempt to locate a particular module INFO 2017-01-31 18:27:11,093 (Velbus): Connection initialised - The above module was contacted INFO 2017-01-31 18:27:11,093 (Velbus): Stopping connection timer - The time-out timer for the above activity has been cancelled (becuase the task was a success) INFO 2017-01-31 18:29:14,421 (Velbus): Scheduled bus connection task INFO 2017-01-31 18:29:20,687 (Velbus): Connection initialised INFO 2017-01-31 18:29:20,734 (Velbus): Stopping connection timer INFO 2017-01-31 18:32:03,390 (Velbus): Scheduled bus connection task INFO 2017-01-31 18:32:09,656 (Velbus): Connection initialised INFO 2017-01-31 18:32:09,656 (Velbus): Stopping connection timer INFO 2017-02-01 18:21:41,539 (Velbus): Scheduled bus connection task INFO 2017-02-01 18:21:48,617 (Velbus): Connection initialised INFO 2017-02-01 18:21:48,617 (Velbus): Stopping connection timer ERROR 2017-02-01 18:24:21,305 (Velbus): Device '22' failed to initialise - There was a problem contacting or initialising your Velbus module with the bass address 22 - What is this module? Is it a non-compatible module? INFO 2017-02-01 19:32:27,883 (Velbus): Scheduled bus connection task INFO 2017-02-01 19:32:34,351 (Velbus): Connection initialised INFO 2017-02-01 19:32:34,351 (Velbus): Stopping connection timer ERROR 2017-02-01 19:35:46,008 (Velbus): Device '22' failed to initialise - There is a clever re-attempt process built into the Velbus protocol so that if a TCP connection fails to a Velbus network, a re-connection attempt is made a number of time is quick succession, then drops to reattempting once an hour.
So to conclude, your Velbus log looks good, other than you have an issue with your module at address 22.
Can you confirm that you are using the Decimal address for this module and what type of module this is.
(Please keep in mind that only the 2nd generation of Velbus modules are compatible with OpenRemote, please review the table in the How-To document - GitHub - Velbus Wiki)
The only other part of your question I can offer a little help with is about alternative platforms to run OpenRemote on.
My personal preference is the BeagleBone Black, which I sell pre-installed with OpenRemote Pro 2.5.0 and Velbus TCP server, all in a Din Rail (or wall mount) case for roughly 150 Euro including VAT and P&P within the UK.
There is more information about this on this thread - Google Group - Din Rail controller
I am playing with the ODroid platform too, as that is an 1Ghz 8 core SBC device, however I'm not finding it that much faster than the 1Ghz single core BeagleBone.
I hope this give you some useful guidance.
Regards,
Stuart
--
You received this message because you are subscribed to the Google Groups "OpenRemote" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openremotecommu...@googlegroups.com.
Visit this group at https://groups.google.com/group/openremotecommunity.
To view this discussion on the web visit https://groups.google.com/d/msgid/openremotecommunity/f153561e-4c73-44e4-b394-37966b03db23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to openremotecommunity+unsub...@googlegroups.com.