How to display Variables from a script on to an OLED using simulink

14 次查看（过去 30 天）

Jack 2023-10-21

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2036501-how-to-display-variables-from-a-script-on-to-an-oled-using-simulink

评论： Jack 2023-10-25

hello

I am having an issue displaying variables on my OLED Display (ssD 13150) im a bit new to matlab and think i need to use simulink but am not sure and vcant find to much info on using oled displys in matlab , does anyone have any resources or tips they can give me

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

采纳的回答

Walter Roberson 2023-10-21

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2036501-how-to-display-variables-from-a-script-on-to-an-oled-using-simulink#answer_1337961

Use simulink arduino I2C blocks; https://www.mathworks.com/matlabcentral/answers/318267-how-to-communicate-with-the-arduino-i2c-in-simulink

https://www.mathworks.com/matlabcentral/answers/512483-how-to-control-ssd1306-128x32-oled-display-in-matlab#answer_1149845 gives an example of the I2C that would be needed to turn on a SSD1306

https://www.mathworks.com/help/supportpkg/arduino/ref/adxl343-read-acceleration-tap-count-oled-io-device-builder.html shows an example of creating custom I/O blocks that use I2C to talk to an OLED that is compatible with SH1106 . I am not sure if you will need to go that far

14 个评论
显示 12更早的评论隐藏 12更早的评论

Walter Roberson 2023-10-22

The slave address for that device is either '0x3C' or '0x3D'; you would typically use 0x3c for the "left" display if you are using two of them.

You can writeRegister() a stream of bytes. The bytes must be in pairs.

If the first (0x80) bit of the first of the pair is 0 then the next bit should be 1 and rest of the bits in the byte should be 0, and the second byte must be a data byte, and that must be the end of the sequence -- so 0x40 then the last byte. (Except as I read the manual, 0x00 then the last byte should work as well, but there is a potential contradiction in the documentation and 0x40 would be safer.)

If the first (0x80) bit of the first of the pair is 1 then the next (0x40) bit determines whether the following byte is a command byte (bit is 0) or a data byte (bit is 1), and the remaining 6 bits of the first byte must be 0. There must be additional bytes in the sequence.

There is an implication that every sequence of bytes must end in 0x00 followed by a data byte -- and therefore there are no "pure command" sequences.

You can send a pure sequence of data bytes by interleaving 0xc0 <data> until a final 0x40 <last data> . Each of those data bytes would be stored in the next location in memory.

The command table starts at page 37 of https://cursedhardware.github.io/epd-driver-ic/SSD1315.pdf

It looks like "display on and clear" is 0xA5 and "display on without clearing" is 0xA4 ... except 0xAF also appears to be to set the display on.