We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, thank you for your code. It was very useful for some experiments with Conrad TX-01 temperature sensor although i had to make some changes)
I found that the receive code can sometimes not change the output data.
The bug is that the variable rx_curByte is incrementend correctly in the AddManBit function but only initialized on the program start.
It must be reseted when a complete receive is completed.
the following code resolves the problem (in the ISR):
... if ((rx_sample == 1) && (rx_curByte >= rx_maxBytes)) { rx_mode = RX_MODE_MSG;
//get ready for next receive ! rx_curByte = 0; rx_manBits=0; } else
...
The text was updated successfully, but these errors were encountered:
Hello! Which lines did you changed?
Sorry, something went wrong.
Hello, in my last experiments I changed this function(initialize lines):
MANRX_BeginReceiveBytes(uint8_t maxBytes, uint8_t *data) { rx_curByte = 0;//initialize rx_numMB=0;//initialize rx_manBits=0;
rx_maxBytes = maxBytes; rx_data = data; rx_mode = RX_MODE_PRE; }
No branches or pull requests
Hello, thank you for your code. It was very useful for some experiments with Conrad TX-01 temperature sensor although i had to make some changes)
I found that the receive code can sometimes not change the output data.
The bug is that the variable rx_curByte is incrementend correctly in the AddManBit function but only initialized on the program start.
It must be reseted when a complete receive is completed.
the following code resolves the problem (in the ISR):
...
if ((rx_sample == 1) &&
(rx_curByte >= rx_maxBytes))
{
rx_mode = RX_MODE_MSG;
...
The text was updated successfully, but these errors were encountered: