You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The issue appears I want to receive the signal strength (rssi) of a received message via radio connection before reading the message. In the older calliope implementation that is not a problem and the value for the rssi is received, If I want to read the message after, the information is not lost and the messages appear in received order. In Calliope V3, this is not the case. If I try to read the signal strength of received message before reading the message, the result is always 0, meaning it can't read the signal strength before reading the message first.
To Reproduce
Steps to reproduce the behavior:
Go to Open Roberta Lab
Create a program to send messages as shown in picture 1
Create a program to display the signal strength value in a loop as shown in picture 2
Implement this on both older calliope versions and calliope V3
Notice the difference in behavior
*Remember: You always need two devices to implement this
Expected behavior
The result should be similar in all versions, the signal strength should be 0 until a message is read
Screenshots
Picture 1:
Picture 2:
Device information
Type [Desktop]
OS: [Ubuntu 22.04.4 LTS]
Browser [Chrome Version 126.0.6478.126]
The text was updated successfully, but these errors were encountered:
Describe the bug
The issue appears I want to receive the signal strength (rssi) of a received message via radio connection before reading the message. In the older calliope implementation that is not a problem and the value for the rssi is received, If I want to read the message after, the information is not lost and the messages appear in received order. In Calliope V3, this is not the case. If I try to read the signal strength of received message before reading the message, the result is always 0, meaning it can't read the signal strength before reading the message first.
To Reproduce
Steps to reproduce the behavior:
*Remember: You always need two devices to implement this
Expected behavior
Screenshots
Picture 1:
Picture 2:
Device information
The text was updated successfully, but these errors were encountered: