C-Bus connection error

Hello

My customer called me that he can not connect his WISER.

I checked connection of it.
I was able to connect WISER via iPhone.
But I found red small icon of top right.
I reconnected WISER via PC then I found C-Bus icon shows red strike through in the Wiser UI.

This is procedure of clear this trouble.
I clicked System Utilities icon and opend a Setup page of WISER.
I clicked Save Settings button.
WISER was re-started.
Trouble has gone.
I did not change any configuration.

I think WISER stopped communication to CNI.

This is third time of same trouble.

Same type of trouble have been posted in the past.
Is this problem resolved?

Regards,

 

Which version of firmware is the Wiser running?

 

Hi kjayakumar,

Thank you very much for your reply.

This is a information of WISER Status.

Firmware Version Kona_1.29.0
Project Size 440272 / 524272 : 83 percent full
Project Information SHIRAISH
CNI Information 192.168.1.201:10001
User Interface Version CBC - 3.7.0,UI - 4.74
Time Source NTP Master at 04/02/2013 07:08:51
Miscellaneous HG-LAN Enabled, Schedules Enabled

The project was created by PICED 4.11.2.
And it has Power Meters and three Web Camera widgets.

Regards,

 

Ok, Wiser firmware looks up to date. When the problem occurs, what is the status reported by the CNI from a web browser? Does it show connection state? For example, my CNI reports:
C-Bus status: Client connected from 192.168.100.100
since > 24 hours ago
Network voltage: 29.0V, measured > 24 hours ago

(192.168.100.100 is the Wiser).

The C-Bus icon with a red strike through it indicates that the Wiser does not have connectivity to C-Bus. In such a scenario, Wiser will retry connecting to the CNI every 30s.

 

Hi kjayakumar

I arranged C-Bus Diagnostic utility at customer's C-Bus.
I can access customer's LAN from my office via PPTP connection.

This is condition of WISER connection error.
WISER was started at January 28.
My customer informed me at February 1 10:00 that he can not connect WISER from his iPad from January 31 12:00.
I tried to connect customer's WISER from my office via PPTP connection.
(WISER is one of device of LAN)
I was able to connect WISER but I found C-Bus icon with a red strike.
I checked condition of WISER.
WISER is 192.168.1.200.
CNI is 192.168.168.1.201.
These units sent back ping reply at error condition.
Netrowk voltage is over 30V. CNI of WISER is 31.4V
I tried to connect WISER again after 5 minutes but still C-Bus icon with a red strike in there.

I checked logging data in Diagnostic utility.
WISER sent Time Clocks command in every hour also error condition.
2013/1/31 14:35:59 Rx=SourceUnit122 Time Clocksate:Thursday 31/1/2013 Clocks:Time:14:35:33 Daylight Savings Offset:0hour(s)

I found Security and MRA command.
But I did not arrange Security and MRA widget.

2013/1/31 0:54:30 Rx:=SourceUnit122 Security Security:StatusReport2 Request
2013/1/31 0:54:30 Rx:=SourceUnit122 Security Security:StatusReport1 Request
2013/1/31 0:54:30 Rx:=SourceUnit122 Plug and Play Audio MRA:GlobalStatusRequest

2013/1/31 13:42:03 Rx:=SourceUnit122 Security Security:StatusReport2 Request
2013/1/31 13:42:03 Rx:=SourceUnit122 Security Security:StatusReport1 Request
2013/1/31 13:42:03 Rx:=SourceUnit122 Plug and Play Audio MRA:GlobalStatusRequest

2013/1/31 22:54:46 Rx:=SourceUnit122 Security Security:StatusReport2 Request
2013/1/31 22:54:47 Rx:=SourceUnit122 Security Security:StatusReport1 Request

2013/2/1 9:29:37 Rx:=SourceUnit122 Security Security:StatusReport2 Request
2013/2/1 9:29:37 Rx:=SourceUnit122 Security Security:StatusReport1 Request
2013/2/1 9:29:37 Rx:=SourceUnit122 Plug and Play Audio MRA: GlobalStatusRequest

I checked logging data(Feb1-Feb5) today but I don't find Security and MRA command.

I hope that this information will be useful to improve the WISER firmware.

Regards,

 

As for me - Wiser is very laggy piece of crap, haven't seen something more problematic than that.
I first time used it in one project about 2 years ago and changed it twice in half a year since - first time because of faulty behavior (software bug), second time - network bridge just stopped to respond.
Even after the third device installed I noticed that when it was running for a week or more iApp began to connect very very slowly to it (sometimes showed something like "interface is not accessable") - and only the reboot helped. As wifi or "router" it's absoloutly useless.
Now I install Cbus network interface with standard wifi AP and a small AMX controller - this piece of hardware that clipsal should have taken as a pattern by when constructed wiser.
P.S. to solve the problem of connection to wiser I put wiser's power supply into cheap timer-relay that plugs directly to AC socket. It automaticly deenergizes wiser every day at 5AM for 3 minutes.
Since then no more troubles and angry calls.

 

Hi Yoshi,

Thanks for the data. I'm not sure what "ping reply at error condition" means. The messages you posted about security and time are normal. These are generated whenever the Wiser gets reconnected to C-Bus. If you're seeing these messages regularly, then that means that the C-Bus connection is getting disconnected and reconnected repeatedly. That could mean several things. I have seen this before when a customer had a duplicate CNI with the same IP address as the Wiser's CNI. The other possibility is that there might be an issue with the busbar connecting the Wiser to the CNI where the connector is marginal.

 

Hi greefon and kjayakumar,

Thank you very much for your comment.

I installed six WISERs in my customers.
WISER is very good system but it is little unstable more than other C-Bus devices.
Regarding "Unable connect to wiser" message, I guess it is depending on zombie Session between WISER and CNI.
As user PC can access WISER in this condition. Because user can get "Unable connect to wiser" message.
But WISER can not access CNI. Because CNI does not have available session in that case.

I think, if user feels slow to open WISER window, user click reload button in browser or restart WISER app in iPhone.
And WISER does not have Logout button. Only close a window or app at end of using WISER.
These operations are making zombie sessions. Sessions are closed by timer in WISER.

Kjayakumar,
As Ping Reply,
I tried to check connectivity in Ethernet to use ping command in Command Prompt in PC.
Ping 192.168.1.200 (WISER)
Ping 192.168.1.201 (CNI)
I was able to get reply message for these commands.
This means that the Ethernet connection is good in " C-Bus icon with a red strike " condition.

I made the test system, such as attached drawing.
I tried to disconnect/connect between HUB and CNI.
I was able to find Security and MRA message as your comment.

I think my customer did not add device in midnight. And all of his devices were configured in DHCP.
Also I do not think there is a place to connect with the loose connection to WISER.
Because WISER is connecting directory to Internet Router.

I will continue to monitor.

Regards,

 

Hi Yoshi,

Thanks for the detailed reply. I'm trying to understand why you say the Wiser can not access the CNI and why the CNI does not have an available session. The fact that you can still ping the CNI from the Wiser when the problem occurs is good. That eliminates any network problems. The red strike through C-Bus indicates that the Wiser believes it has no C-Bus connection. This is why I was suggesting checking using the CNI's web page (in your case, this will be http://192.168.1.201/ to see what the CNI is reporting as its status). It should look like below:
C-Bus status: Client connected from 192.168.100.100
since > 24 hours ago
Network voltage: 29.0V, measured > 24 hours ago

Is there any other device/application on your network that may connect to the CNI? If you have a toolkit session open, please be aware that during the time it is connected, Wiser will not be able to connect to the CNI. The CNI can only have one connection at a time. Wiser uses TCP keepalives to ensure its TCP connection with the CNI is still active and it also checks periodically if it has a valid C-Bus connection with the CNI, if it does not, then it will attempt to reconnect to the CNI.

 

Hi kjayakumar,

This is late reply for your suggestion.

At first, I checked connection of session level between WISER and CNI.
WISER and CNI made only single session for all of accessing WISER.
When i connect two PCs to Wiser and make connections, I was able to control C-Bus groups from both two PCs, but session was only one.


I was informed similar trouble in WISER by another customer.

I checked condition of WISER remotely.

WISER and CNI sent back PING reply in LAN environment.
My PC was able to connect CNI via Web browser at connection from .
My PC was not able to connect WISER via Web browser. I was not able to get authentication window at connection from Web browser.

I tried to reinstall Project data from PICED for restart WISER.
All of WISER functions came back after that.

This trouble does not relate C-Bus network voltage.
Because CNI was not restarted for clearing trouble.

And also this trouble does not relate any other device/and application.
Because my PC was able to communicate WISER and CNI in Network Layer level.
As process of Ping and Ping Reply were covered in Network Layer.
If IP address duplication occurred, my PC cannot get Ping Reply from WISER and CNI.

I think, some of process in WISER was frozen.
But process for 8336 and 8337 were working.

I believe WISER has some software bugs regarding process management.

Thank you very much.

 

Thanks for your reply. I'm not sure what you mean by "session was only one". If you mean that there is only one connection between the Wiser and its CNI, then yes, that is correct and expected. There will only ever be a single connection between the Wiser and its CNI. If by "session", you mean Adobe Flash UI, iPhone UI, iPad, then these sessions are managed on the Wiser itself. The Wiser handles the multiple sessions (up to 6) and then talks on its own to the CNI.

"My PC was not able to connect WISER via Web browser. I was not able to get authentication window at connection from Web browser."

This is a key and useful observation. If the http authentication (browser asking for username/password) window does not come up, then that indicates that the web server has stopped responding to requests. Is this the LAN side web server (meaning port 80) or the WAN/remote side web server (port 8080)?

 

Hi kjayakumar,

As reported error, connection error occurred in both WAN and LAN side.

I connected network analyzer at one of port of HUB in previous picture.
I was able to get only a port number to communicate between WISER and CNI.
I unplugged 12V DC only WISER unit.
The CNI was working on an ongoing basis.
I plugged 12V DC to WISER and start Web browser in PC.
I was able to get Authentication Window in PC.
I added user/password and pressed "OK".
But I got a "COMMUNICATION ERROR" after that.

I checked network analyzer in this condition.
WISER tried to communicate CNI in another port number.
But CNI was still using old port number to communicate WISER.
After a few minutes, CNI discarded old port number and it accepted new port number to commutate WISER.
As "COMMUNICATION ERROR" was cleared after that.
This is normal communication between WISER and CNI.

But if "COMMUNICATION ERROR" will not be cleared,
uncommunication condition is continuing between WISER and CNI.
If this trouble will be cleared only restart WISER, trouble is depending on WISER side.

I installed about ten WISERs.
I feel WISER has three type troubles.

1. Slow response
It is slow to path authentication phase and loading current condition.
The control window has come finally.

2. " COMMUNICATION ERROR "
Authentication phase is passed but control window does not come.

3. No Authentication Window
Authentication Window does not come.

I think all of troubles will be gone after restart WISER.

Thank you very much.