Dave Heap - 2014-04-25

I have had one other report of a similar problem that later went away. Possibly a bug in a particular firmware release, but I have no way of reverting firmware versions on a decoder to test this.

Please recheck with JMRI V3.7.4 just in case.