05-07-2019, 09:17 AM
OK, that's clearer. It wasn't totally obvious from before that that was what was going on. The gotcha here is that that configured trigger stuff is handled generically at the base driver class. So I don't think it can have anything really to do with logic server vs. not logic server, since that code wouldn't know or care what the derived driver class is. The triggers are actually handled even below the base driver class, it's done in the class that stores the field values. So if the field value changes, it should happen. There would seem to need to be some other explanation for it that we need to explore.
Are there multiple computers involved here? If so, are the two drivers on separate machines? That's the most likely answer that comes to me just from what we know so far. Triggers are UDP broadcasts so there are things that can interfere with those. But, OTOH, the logic server runs on the MS and most likely you installed the driver there as well, is that the case? If so, were you watching for triggers locally there on the MS? Or, if there are two machines involved, were you watching the trigger monitor on the same machine as where the driver is installed?
It can't be that the incoming trigger port is blocked or you wouldn't see the other event.
Just as a sanity check, can you create a numeric logic server field? Maybe one that sums the value of two dimmers or something and sends a trigger when non-zero maybe. Then set the dimmers such that the sum should be non-zero. Let's make sure it's not something specific to boolean fields and is consistently just that one driver or not.
Are there multiple computers involved here? If so, are the two drivers on separate machines? That's the most likely answer that comes to me just from what we know so far. Triggers are UDP broadcasts so there are things that can interfere with those. But, OTOH, the logic server runs on the MS and most likely you installed the driver there as well, is that the case? If so, were you watching for triggers locally there on the MS? Or, if there are two machines involved, were you watching the trigger monitor on the same machine as where the driver is installed?
It can't be that the incoming trigger port is blocked or you wouldn't see the other event.
Just as a sanity check, can you create a numeric logic server field? Maybe one that sums the value of two dimmers or something and sends a trigger when non-zero maybe. Then set the dimmers such that the sum should be non-zero. Let's make sure it's not something specific to boolean fields and is consistently just that one driver or not.
Dean Roddey
Explorans limites defectum
Explorans limites defectum