HT16K33 Configuration: Difference between revisions
Jump to navigation
Jump to search
m (Side bar update - Now side bar is a self page) |
m (fix sidebar template link) |
||
| Line 1: | Line 1: | ||
{{ | {{I2C Devices Classes sidebar}} | ||
As each device, each HT16K33 you have in your hardware interface must be declared here.<br /> | As each device, each HT16K33 you have in your hardware interface must be declared here.<br /> | ||
In our radio panel the section defining the HT16K33 chip is as follows :<br /> | In our radio panel the section defining the HT16K33 chip is as follows :<br /> | ||
Latest revision as of 11:06, 19 August 2019
| I2C Devices Classes |
|---|
|
MCP23017 |
|
HT16K33 |
|
Navigation |
As each device, each HT16K33 you have in your hardware interface must be declared here.
In our radio panel the section defining the HT16K33 chip is as follows :
[IOPACK1]
devicetype=HT16KK33
devicename=LEDPACK1
deviceaddr=0x70
devicedummy=0
- devicetype :
This is the class that will be used to create the element in the interface.
In the case of Holtek HT16K33 chips, the module class is HT16K33.
- devicename :
This is the name under which it will be created at the interface. This name must be unique.
This name must be used in the getDevice(devicename) function, for example. This parameter is case sensitive
- deviceaddr :
This is the device address on the I2C bus. The address must be supplied in hexadecimal format.
- devicedummy :
This parameter is actually unused. But have been implemented for futur release. You must leave this parameter to 0