Maybe it would be worth putting a real simple step by step guide to adding it to your Core up on the Wiki. That would remove any barriers to even a casual tester giving it a try. We faced much the same problem when we first started to test z-wave by the way... but the 'fix' here was to just go buy some hardware and test it ourselves. After that we had no end of people testing it LOL!! If I could do that here in the UK I would...

I'll try to add a bit more to the page.. regarding testing, troubleshooting, etc.

I'm not the best at wiki entries, and I'm not sure what you mean by 'promoting' it...

Would it be possible to help me with that?

Well what I meant by 'promoting' your driver and the tutorial was just drawing peoples attention to it in a more obvious way. Start a new thread and post an announcement and url to the tutorial so that people take another look at testing the driver. Its always going to be harder for people to test new capabilities when they have to invest in the hardware before they can do so... but with the tutuorial i think more people will be willing to do that now ;-)

I'm sure there's more... It's hard to remember what I did...This was my first attempt at Ruby programming, and at over 2000 lines of code, I think I did pretty good.I'm taking a different approach to the PLCBUS interface.. a bit more coding at the beginning, but in the long run, I think it will help tremendously.. (much more OO design)

and to think that ENGLISH was my worst subject in school...Dan

Logged

The only intuitive interface is the nipple. After that it's all learned.My other computer is your windows box. I'm out of my mind. Back in 5 minutes.Q: What's Red and smells like blue paint?