-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
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
Timeout Issue #51
Comments
Sure, can you post your read and write functions?
So if you can't honor the requested timings, you can just return the exact number of byte requested and you should never encounter any timeout error |
Thanks for quick Answer Please review the read and write code below along with the logs. This code executes a read operation without incorporating any time delay handling between read and write operations. Upon request, we print the return value, which consistently shows -3.This indicate a read/write timeout error? How can we resolve this timeout issue? The read operation should function properly without resorting to alternatives. Could you please assist me in resolving this issue? Logs: ql_rs485_demo:ql_rs485_read 206 entered ql_rs485_read read_bytes: 25 ql_rs485_demo:ql_rs485_demo_thread 371 Error1 in reading1: -3 Code:- #include "ql_api_osi.h" ql_task_t rs485_task = NULL; int ql_rs485_write(ql_uart_port_number_e port, unsigned char *data, unsigned int data_len)
} int ql_rs485_read(ql_uart_port_number_e port, unsigned char *data, unsigned int data_len)
} int32_t read_serial(uint8_t* buf, uint16_t count, int32_t byte_timeout_ms, void* arg)
} int32_t write_serial(const uint8_t* buf, uint16_t count, int32_t byte_timeout_ms, void* arg)
} static void ql_rs485_demo_thread(void *param)
exit: |
I integrated NanoModbus library with the quectel EC200u controller for RTU communication as a master. However, I'm encountering timeout errors despite successful communication. In the SDK, there isn't a timer function available to handle read and write operations. Could you please assist me in resolving this issue?
The text was updated successfully, but these errors were encountered: