Elk Version Support Issue

[Ron Haley]

Driver is MEng.System.CQC.Drivers.ElkM1.DriverImpl. Version 2.0

I'm running with Elk V1

[Dean Roddey]

Oh, that's the issue. I was looking at the V2 driver. You don't have the driver pack I sent you for that hacked up V1 driver? I'd hate to have to do that again for such an out of date driver.

[Ron Haley]

Oh, that's the issue. I was looking at the V2 driver. You don't have the driver pack I sent you for that hacked up V1 driver? I'd hate to have to do that again for such an out of date driver.

I'd already looked, and looked again.  Nothing.  Can u check your sent files perhaps.

[Ron Haley]

Oh, that's the issue. I was looking at the V2 driver. You don't have the driver pack I sent you for that hacked up V1 driver? I'd hate to have to do that again for such an out of date driver.

I'd already looked, and looked again.  Nothing.  Can u check your sent files perhaps.

Let me restart everything, reinstall drivers etc.  Make sure it's not a problem here.  Hard to believe you made change in one driver and not the other,.

[Ron Haley]

OK, still no go. If I reconfigure the V1 driver, upon reloading, it gets an update correctly. So the Elk has the correct information stored.

Tried to access the counters in the Elk using the V2 driver, but it seems to support a maximum of 16 counters. I'm using 36 currently. And adding a new field in the Client for every counter, Output, zone etc. was the reason I never moved to the V2 driver. Huge time sink and prone to errors.

[Ron Haley]

Good news. Found the driver updates from last year. Emailed them to you so that you can put them in the official version

[Ron Haley]

Installed and working correctly. I sent them to you last night. Let me know if you don't have them.

[Dean Roddey]

I don't think it's worth updating the V1 driver. If you have the driver pack just use that. The V2 driver was correctly updated to handle the 5.x counter support (where they are reported async and don't have to be polled.)

[Ron Haley]

The problem with the V2 driver is that its a massive upgrade work wise for no benefit (to me). The V1 driver client did a lot of work. Not so for the V2 client. It looks like V2 was developed to work with the autogen stuff. Certainly didn't take into account customers migration for V1, IMHO
Now I could upgrade the Elk, but it works. Let sleeping dogs lie.

[kblagron]

Similar to you, the upgrade for me was going to require a lot more time than I had.  I ended up finally upgrading in pieces.  I use the ethernet interface, so I was able to have both drivers running at the same time.  I have done this for a good while, I now have all of my interfaces updated, just need to work on some of the triggers and hopefully I will be up to date on the latest everywhere.