Timeline for How to interpret Serial data received by Bluetooth module
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 27, 2020 at 10:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jul 30, 2020 at 9:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jun 30, 2020 at 8:07 | answer | added | Mwasela | timeline score: 1 | |
Jun 29, 2020 at 23:32 | answer | added | DragonflyRobotics | timeline score: 0 | |
Jun 21, 2020 at 19:35 | comment | added | Juraj♦ | replace %u with %c | |
Jun 21, 2020 at 19:34 | comment | added | Majenko |
98 and b are the same thing. Just different ways of representing the data.
|
|
Jun 21, 2020 at 19:33 | comment | added | I Like | nvm ascii table | |
Jun 21, 2020 at 19:31 | comment | added | I Like | seems to work now. But still wondering how to convert data to characters. Example: 'b' is received as '98'. Where do i look up the corresponding char for the data? | |
Jun 21, 2020 at 19:18 | comment | added | I Like | you are correct from looking at datasheet. thank you! | |
Jun 21, 2020 at 19:17 | review | First posts | |||
Jun 22, 2020 at 21:55 | |||||
Jun 21, 2020 at 19:16 | comment | added | Majenko | Sounds like you have a baud rate mismatch. | |
Jun 21, 2020 at 19:16 | history | asked | I Like | CC BY-SA 4.0 |