HT16K33 Class: Difference between revisions

Jump to navigation Jump to search
Line 306: Line 306:
But as most of device methodes, this one should be invoked directly only when developping new elements using HT16K33 devices
But as most of device methodes, this one should be invoked directly only when developping new elements using HT16K33 devices


=== setOut(port, row, out, value) ===
=== setOut(port, com, out, value) ===
Allow to set on of off one of the ouput, using port, row and out number as agument
* port : '''A''' or '''B'''. Allow to choose witch range of output will be affected.
* com : Common Register Number [1...8]
* out : Output Number [1...8]
* value : '''0''' or '''1'''
Except for development or debugging and knowing what you are doing, there is no reason to invoke this method directly. It is a system method internal to the operation of the driver.
Except for development or debugging and knowing what you are doing, there is no reason to invoke this method directly. It is a system method internal to the operation of the driver.
<syntaxhighlight lang="python">
<syntaxhighlight lang="python">
Line 316: Line 321:
>>> MODULE_HT16K33 = FGINT1.getModule('HT16K33')
>>> MODULE_HT16K33 = FGINT1.getModule('HT16K33')
>>> LEDPACK2 = MODULE_HT16K33('LEDPACK2', '0x71', 0)
>>> LEDPACK2 = MODULE_HT16K33('LEDPACK2', '0x71', 0)
>>> LEDPACK2.setOut('A', 1, 1, 1) # this will set on the first output of the port A using Common 1
>>> LEDPACK2.setOut('B', 2, 5, 0) # this will set off the fifth output of the port B using Common 2
>>>
>>>
</syntaxhighlight>
</syntaxhighlight>


{{WIP}}
But as most of device methodes, this one should be invoked directly only when developping new elements using HT16K33 devices.
534

edits

Navigation menu