(from Trac issue #85 by kpratt)
Observed Behavior: '/dipswitch/value' returns 220 for two different settings of
the dipswitch.
Expected Behavior: Should return 192 in one state and 220 in second state.
Steps to recreate:
--Set bits 7 and 8 high on dipswitch
--Read value using /dipswitch/value in mchelper
--Returns 220 as value (128 + 64 should be 192)
--Set bits 3,4,5 high
--Read value using /dipswitch/value in mchelper
--Returns 220 as value (This is correct: 128 + 64 + 16 + 8 + 4 = 220)
Note: The dipswitch contacts on the back of the board read correctly with a
multi-meter: ie bits
set on read 0.0V (connected), and bits set off read 3.258V (not connected),
indicating this may be
a firmware issue, rather than a hardware problem.
Repeatability: 100%
System Details: /system/version Heavy 1.5.1 MCHelper Version 2.2.0 (Windows XP)
I'm not using the dipswitch in any of my projects, so it's not a big issue for
me, but if there is
anything I can do to help debug or track this down for other people, just let
me know.
Cheers-- --Kevin
Neglected to specify that the first tests were all on the USB connection.
Checking again, the
dipswitch values read correctly when accessing the board with an ethernet
connection, but
display the original error when using USB. This behavior is seen on both XP and
OS X 10.5.
Original issue reported on code.google.com by lst...@gmail.com on 1 Jul 2009 at 5:11
Original issue reported on code.google.com by
lst...@gmail.com
on 1 Jul 2009 at 5:11