We have moved at community.getvera.com

Author Topic: NX-584e Connection to NX-8 using WF2SL  (Read 14980 times)

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #15 on: October 09, 2013, 05:01:04 pm »
Unfortunately I can't access the Configure tab, it just stays at "Getting configuration..."

You can go to the Advanced tab for the device and edit the Debug variable to the value 1.  If there is no Debug variable, you can add it (copy and paste to ensure you don't mistype them):
Code: [Select]
New service: urn:futzle-com:serviceId:CaddxNX584Security1
New variable: Debug
New value: 1
Then Save.

I am leaning towards the likelihood that Vera's not able to communicate with the WF2SL, leaving the plugin dead in the water.  While I'm convinced by your testing that you have set up the WF2SL properly, I'm not convinced that the Vera is properly configured to talk to it.  But let's rule out a problem with the plugin first by capturing the Luup log during a reload.

Offline BoffinGus

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #16 on: October 10, 2013, 06:17:28 am »
Thanks again futzle,

I've enabled the logging and the most obvious entry is:

10/10/13 21:09:55.949   luup_log:8: Global handlers not set up yet <0x5817>
10/10/13 21:09:55.951   luup_log:8: Global handlers not set up yet <0x5817>

I'll add that I have re-installed the system again and this time the plugin is device 8, not 11 that was in the previous posts.

Cheers
Gus..

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #17 on: October 10, 2013, 06:29:09 am »

10/10/13 21:09:55.949   luup_log:8: Global handlers not set up yet <0x5817>

That's not necessarily an error. I really need the whole log starting from a Luup reload.

Offline BoffinGus

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #18 on: October 10, 2013, 08:13:37 am »
Hi futzle,

Here is the log showing just Critical & Luup entries:

root@MiOS_18714:/tmp/log/cmh# tail -f LuaUPnP.log | grep '^01\|^5'
01      10/10/13 23:09:24.940   got CAN <0x1406>
01      10/10/13 23:09:25.971   got CAN <0x1406>
50      10/10/13 23:09:32.184   luup_log:0: L_sPhoneUI running version: 1.5.622 <0x803>
50      10/10/13 23:09:32.188   luup_log:0: L_WapUI running... <0x803>
50      10/10/13 23:09:34.111   luup_log:6: starting device: 6 <0x803>
50      10/10/13 23:09:34.113   luup_log:6: got devices <0x803>
50      10/10/13 23:09:34.122   luup_log:6: module0 port 0 type ETHERNET device: 6 <0x803>
50      10/10/13 23:09:34.125   luup_log:6: module1 port 1 type SERIAL device: 6 <0x803>
50      10/10/13 23:09:34.126   luup_log:6: parse device: 7 module: 1 unit: 1 type: SERIAL <0x803>
50      10/10/13 23:09:34.129   luup_log:6: num modules 1 <0x803>
50      10/10/13 23:09:34.130   luup_log:6: ValidModules: 1 <0x803>
50      10/10/13 23:09:34.412   luup_log:8: Initializing Caddx NX-584 __LEAK__ this:245760 start:245760 to 0x8d7000 <0x803>
50      10/10/13 23:09:34.413   luup_log:8: Opening serial port <0x803>
50      10/10/13 23:09:34.414   luup_log:8: Sending message and waiting for response: 0x21 Interface Configuration Request <0x803>
50      10/10/13 23:09:34.416   luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x803>
50      10/10/13 23:09:42.420   luup_log:8: Input is nil <0x803>
50      10/10/13 23:09:42.421   luup_log:8: Timed out waiting for response, retrying <0x803>
50      10/10/13 23:09:42.422   luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x803>
50      10/10/13 23:09:50.430   luup_log:8: Input is nil <0x803>
50      10/10/13 23:09:50.431   luup_log:8: Timed out waiting for response, retrying <0x803>
50      10/10/13 23:09:50.432   luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x803>
50      10/10/13 23:09:58.458   luup_log:8: Input is nil <0x803>
50      10/10/13 23:09:58.459   luup_log:8: Timed out waiting for response, retrying <0x803>
01      10/10/13 23:09:58.471   LuaInterface::CallFunction_Startup-2 device 8 function caddxInitialize failed Caddx NX584 Security System[8] with return false <0x803>

Cheers
Gus..

Offline BoffinGus

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #19 on: October 10, 2013, 10:44:19 am »
Hi futzle,

Here is another log, this time I eneterd the IP & port of GC IP2SL for connection instead of using serial port drop box option.

01      10/11/13 1:32:34.525    Mongoose XXX-mg_stop1 0x83e6d8 1 1 <0x400>
50      10/11/13 1:32:34.681    luup_log:8: Ignoring byte 0b <0x4c14>
50      10/11/13 1:32:34.682    luup_log:8: Global handlers not set up yet <0x4c14>
01      10/11/13 1:32:36.540    Mongoose XXX-mg_stop2 0x83e6d8 2 1 <0x400>
01      10/11/13 1:32:36.541    Mongoose XXX-mg_stop3 0x83e6d8 2 1 <0x400>
01      10/11/13 1:32:36.542    Mongoose XXX-mg_stop4 0x83e6d8 8782696 1 <0x400>
50      10/11/13 1:32:47.121    luup_log:6: starting device: 6 <0x402>
50      10/11/13 1:32:47.124    luup_log:6: got devices <0x402>
50      10/11/13 1:32:47.133    luup_log:6: module0 port 0 type ETHERNET device: 6 <0x402>
50      10/11/13 1:32:47.135    luup_log:6: module1 port 1 type SERIAL device: 6 <0x402>
50      10/11/13 1:32:47.137    luup_log:6: parse device: 7 module: 1 unit: 1 type: SERIAL <0x402>
50      10/11/13 1:32:47.139    luup_log:6: num modules 1 <0x402>
50      10/11/13 1:32:47.141    luup_log:6: ValidModules: 1 <0x402>
50      10/11/13 1:32:47.502    luup_log:8: Initializing Caddx NX-584 __LEAK__ this:245760 start:24576to 0x897000 <0x402>
50      10/11/13 1:32:47.503    luup_log:8: Opening socket to 192.168.0.51 port 4999 <0x402>
50      10/11/13 1:32:47.621    luup_log:8: Sending message and waiting for response: 0x21 Interface Cfiguration Request <0x402>
50      10/11/13 1:32:47.623    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:47.821    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:47.823    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:47.824    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:47.825    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:47.827    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:47.981    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:47.983    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:47.983    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:47.985    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:47.986    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:48.191    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:48.193    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:48.193    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:48.195    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:48.197    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:48.351    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:48.353    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:48.353    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:48.355    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:48.356    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:48.661    luup_log:8: Received inconvenient message 0x08 __LEAK__ this:28672 sta:274432 to 0x89e000 <0x402>
50      10/11/13 1:32:48.663    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:48.663    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:48.665    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:48.667    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:51.001    luup_log:8: Received inconvenient message 0x08 __LEAK__ this:94208 sta:368640 to 0x8b5000 <0x402>
50      10/11/13 1:32:51.002    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:51.003    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:51.004    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:51.006    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:53.631    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:53.632    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:53.633    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:53.634    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:53.636    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:56.131    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:56.133    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:56.133    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:56.135    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:56.137    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:32:58.621    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:32:58.623    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:32:58.624    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:32:58.625    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:32:58.627    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:33:01.121    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:33:01.123    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:33:01.123    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:33:01.125    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:33:01.127    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:33:03.611    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:33:03.613    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:33:03.613    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:33:03.615    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:33:03.617    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:33:06.161    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:33:06.163    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>
50      10/11/13 1:33:06.163    luup_log:8: Sending message: 0x1D Positive Acknowledge <0x402>
50      10/11/13 1:33:06.165    luup_log:8: Message: Outgoing: 0x7e 0x01 0x1d 0x1e 0x1f <0x402>
50      10/11/13 1:33:06.167    luup_log:8: Message: Outgoing: 0x7e 0x01 0x21 0x22 0x23 <0x402>
50      10/11/13 1:33:08.480    luup_log:8: Received inconvenient message 0x08 <0x402>
50      10/11/13 1:33:08.482    luup_log:8: Message: Unsolicited message body: 0x00 0x00 0x00 0x00 0x00x00 0x00 0x00 0x02 0x01 0x00 <0x402>

Seems to get traffic? but not correct.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #20 on: October 10, 2013, 05:19:18 pm »
Hi BoffinGus,

That second log is looking better.  The first one contains only timeouts.

My best guess from the log is that bytes are travelling from the NX-584 to the Vera without a problem, but no bytes are travelling from Vera to the NX-584.  I base this on the fact that the plugin is getting the same message (0x08, which can be generated spontaneously, and probably was minutes before you started the capture) over and over again.  The NX-584 re-sends messages until they are acknowledged by Vera.  Vera is (according to the log) sending acknowledgments, but the NX-584 is apparently never receiving them, so it continues to send that one message, over and over...

So.  In all your testing of the serial connection I don't think you've verified the data path travelling to the NX-584 over the serial line.  There are a couple of points of failure that you can look at:
  • Mess with the four jumpers on the NX-584 board, the ones that control the transmit/receive pins on the interface.  As a rule you either leave all four as they came, or toggle all four of them to their opposite state.  If you changed only some of them then you'd get the behaviour you see.
  • See if the IP2SL has any kind of serial flow control or half-duplex turned on. It might be holding back bytes on the mistaken assumption that it isn't allowed to send them yet.  You're largely on your own here but look for options to do with "duplex" or "flow control" and jiggle them around.
  • Or it could be a bad connection or bad cable.

As far as the plugin is concerned, it's behaving correctly under the circumstances.  There's no point uninstalling/reinstalling it again.  When the underlying physical problem with the connection is resolved, the plugin will suddenly start working.

Offline BoffinGus

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #21 on: October 23, 2013, 03:28:20 am »
Update...

I have been able to confirm that the serial connection is good with a 232 breakout which shows that communication from each end is working. I have also used a Prolific USB to serial directly getting same results.

I can see transmits from the Vera are getting to the Nx as DS3 is lighting up.... though I have had to flip J7&9 compared to J8&10 as no traffic from Vera happens.

Does anything on the NX4 side need to be set for correct data from the 584? Communicator format?

Further update....

After leaving for an appointment, I've returned home to find all is working!!! ;D ;D

So far so good, I'm seeing Zones, etc...

« Last Edit: October 23, 2013, 08:45:44 am by BoffinGus »

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
NX-584e Connection to NX-8 using WF2SL
« Reply #22 on: October 23, 2013, 04:07:22 am »
Does anything on the NX4 side need to be set for correct data from the 584? Communicator format?

Only what is described on the plugin's documentation page (http://code.mios.com/trac/mios_caddxnx584).

Edit: by that, I mean that there is a list of ten or so message types that you have to enable on the interface. The names are the same as you will see in the Nx-584 installation manual (which you can find online if you didn't receive along with the hardware). I've no idea what those settings become on a factory reset so you'll have to just set them according to the list on the web page.

But something unprecedented is going in here. Changing only half the jumpers while leaving the others unchanged has never been the right setting for anyone else. I'm suspicious. Additionally, the way that your previous log keeps repeating the 0x08 message still indicates that Vera's acknowledgement packets aren't getting through The connection between the NX-4 and the NX-584 is bidirectional so if you are getting messages one way they are going the other way too.

I'm out of ideas, I'm afraid.
« Last Edit: October 23, 2013, 05:56:53 am by futzle »

Offline BoffinGus

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #23 on: October 23, 2013, 10:01:43 am »
Hi futzle,

Well the change of the J7&9 seems to have done the trick. :)

I agree that this should not be the case as I am flipping the Rx & Tx but not the CTS & RTS. That being said the Nx584e manual does note that the RTS & CTS are not currently supported.  ??? I have also tried both options on the iTach GUI for either 'Hardware' & 'None' Flow control too, both seem to work.

Thanks for the prompt replies.
Cheers
Gus..

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #24 on: October 23, 2013, 05:00:40 pm »
That being said the Nx584e manual does note that the RTS & CTS are not currently supported.  ??? I have also tried both options on the iTach GUI for either 'Hardware' & 'None' Flow control too, both seem to work.

It's hard to know if the documentation is still correct, but even if it is and the NX-584 doesn't "support" RTS/CTS, moving that jumper around will cause a high or low voltage to be asserted onto the appropriate wire in the cable.  It may even convince the other end to withhold sending data.  Serial is a pain in this respect; if you don't have both ends configured exactly the same then you can end up getting only half (or none) of the conversation.

The next thing to be on the lookout for is to check that all the message types that you need are enabled in the NX-584 programming interface.  Not setting these (for instance, having Zone Status Message off) will lead to weird experiences such as not getting proper zone status when you walk around the house.

Offline jthurs

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: NX-584e Connection to NX-8 using WF2SL
« Reply #25 on: December 28, 2013, 03:55:41 am »
Hello, would anyone be able to connect the NX-584 and on the WF2SL, and have them properly configured?  I would pay someone to ship me this setup.

Then all I would have to do is connect the NX-584 to my NX-8E correct and the installation would be simple?