Skip to content
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

Seldom Nonresponses #24

Open
j-broome opened this issue Jan 20, 2023 · 2 comments
Open

Seldom Nonresponses #24

j-broome opened this issue Jan 20, 2023 · 2 comments

Comments

@j-broome
Copy link

Running the example rtu slave with no flow control. Just using USB to UART0 for now. When I use FinSH to run the slave demo, everything seems to work, but Modbus Poll has shown occasionally the slave does not respond. I tried adjusting the priority from 10 to 5 so it wasn't fighting with the main task, but still seeing the slave not respond sometimes.

Since the terminal is running on uart0, when I run the slave from uart0, does it hand the port off or is that where my issues are coming from?

image

@j-broome
Copy link
Author

I have the demo running on UART port 1 (GP4/pin 6 and GP5/ pin 7). I have Modbus Poll polling 10 holding registers 0 through 9 every second.
I run the slave demo through FinSH as suggested:
image
Modbus Poll Setup:
image
image
Register 3 is incrementing as per the sample code:
image
But here is the problem (7 out of 132 messages have experienced a transmit timeout) that I was able to screenshot showing the communication log:
image

Any suggestions? This is the example with no modifications other than correcting the Pico systick in RT per: https://github.com/RT-Thread/rt-thread/pull/6242/commits/

@j-broome
Copy link
Author

The only thing I did notice I had incorrect was the parity, but still seeing the same result after recompiling and trying again. Changed it to Even Parity per the demo setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant