Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Different behavior than standard Platform IO 'pico' when running simple Modbus RTU Server example using ArduinoModbus #2378

Closed
pomplesiegel opened this issue Aug 28, 2024 · 0 comments

Comments

@pomplesiegel
Copy link

Hello! I realize this is crossing streams slightly, but I'm wondering if what's going on here may be on a lower embedded level.

I am building a device using an Adafruit Feather RP2040 + a RS485 interface for Modbus RTU communication. Everything was working well when using the standard Raspberry Pi Pico platform on Platform IO. However, I really prefer the arduino-pico platform so I changed over. Everything was working great, but for some strange reason only 1 modbus server/slave running arduino-pico can be reached on a RS485 bus without waiting multiple seconds - a totally new and very strange issue.

I'm wondering if some strange timing / pin behavior is happening here under the hood?

This is the issue I created for the ArduinoModbus library, including a very short 20-ish-line generic MVP example of the issue.

Anyone have any ideas on what could be going on here? I've been beating my head against a wall trying experiments to uncover what could be the underlying issue.

Thank you!
Michael

Repository owner locked and limited conversation to collaborators Aug 28, 2024
@earlephilhower earlephilhower converted this issue into discussion #2379 Aug 28, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant