Rated 3 out of 5 stars

by ve2mrx on Jan. 16, 2014 · permalink

The code in the documentation was wrong and it has been replaced. Apparently that code fixed the problem... I can't wait to see the fix coded in the extension! It will work then... For those who used the workaround, it will have to be reversed...