Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Official 5.3 Beta Discussion Thread
#31
It's something to look at. I don't know if they improved anything or just added an IP interface. The UPB interface, it looked to me from what I've seen looking at the driver, isn't great. If they also improved that in the process, it might be worth taking on a new driver and taking advantage of those improvements.

Anyhoo, in the meantime, for some reason today the lock is responding to my messages. I just locked and unlocked the lock via the driver. I'm not sure what changed, which is sort of not optimal. But at least it's working now. I also made a big improvement in how the XML info files pass in handler specific info to get rid of what would have ultimately become a lot of busy work.

Oh, so I just restarted the driver and now it's not reponding again. The driver had been up a while after the new replication pass but I could still talk to the lock. Clearly the lock hadn't just stayed awake all that time, just because it had been woken up by the master during replication. So there may be something going on with the management of the encryption key or something and I'm not getting it loaded back up correctly when the driver loads next time.
Dean Roddey
Software Geek Extraordinaire
Reply
#32
Well, actually it just worked that one time, perfectly, then hadn't worked again all this time. And now it just worked again, after a replication. I've let it sit there for some time, longer than it would have stayed awake just due to the replication pass I think, and it is responding perfectly. I restarted the driver, and now it won't respond.

That's seriously weird.
Dean Roddey
Software Geek Extraordinaire
Reply
#33
Well, I've spent days and I cannot figure out the above issue. I can only talk to the lock securely after a replication has been done. Once the driver stops and restarts, it can't talk to it. I can do the replication process again after the driver starts back up and it starts working again. But I can't automatically do a replication when the driver starts, because it requires the master controller to start that process.

It makes no sense to me at all why this is the case. I guess the master is sending the Z-Stick something during replication that it loses when the driver stops, though that makes no sense to me. It wouldn't even know if the driver is there or not. The only difference is that the driver will sometimes send it commands when its running. The driver isn't directly connected to the Z-Stick, it's just talking to it via a virtual serial port. And the only thing really related to secure comms is the network key, which I have stored away load up again when the driver starts.

If the driver was not running for a while then I could see maybe the master deciding it's not responding and putting it on some sort of dead node list, but even I stop and restart the driver as quickly as possible, way too quickly for such a thing to happen, I can't talk to the lock securely again.

If it didn't respond at all, I'd think maybe it was just something to do with the whole beaming thing, which is something I wasted a LOT of time on earlier thinking that was the case. But it wakes up and responds just fine to non-secure messages. And it even responds to the request for a security nonce that is needed to send it back a secure message. So it's responding, it just ignores secure messages as though my network key is wrong, but it's exactly what I was given during the replication phase.

I dunno, this just keeps happening and I'm sucking up time and more time on this thing. It's depressing and infuriating at the same time, which is always a nice combination. I'm not sure if it's wise to continue down this path any further or not.
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official 5.3 Release Thread Dean Roddey 0 96 10-17-2017, 07:13 PM
Last Post: Dean Roddey
  Official 5.2 Beta Discussion Thread Dean Roddey 244 15,899 10-14-2017, 07:57 PM
Last Post: Dean Roddey
  Official 5.2 Beta Release Thread Dean Roddey 13 2,193 10-09-2017, 06:49 PM
Last Post: Dean Roddey
  Official 5.1 Beta Discussion Thread Dean Roddey 453 49,316 05-16-2017, 03:45 PM
Last Post: Dean Roddey
  Official 5.1 Beta Release Thread Dean Roddey 28 5,708 05-12-2017, 05:44 PM
Last Post: Dean Roddey
  Official 5.0 Beta Discussions Dean Roddey 2,019 133,553 11-09-2016, 04:34 PM
Last Post: Dean Roddey
  Official 5.0 Beta Release Thread Dean Roddey 15 6,933 11-01-2016, 10:32 AM
Last Post: Dean Roddey
  How to obtain Beta versions? willsauter 3 1,300 07-15-2016, 04:57 PM
Last Post: willsauter
  Official 4.7 Beta Release Thread Dean Roddey 21 7,094 04-23-2015, 04:20 PM
Last Post: Dean Roddey
  Official 4.7 Beta discussion thread Dean Roddey 295 32,409 04-23-2015, 04:19 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)