-
Notifications
You must be signed in to change notification settings - Fork 6
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
Raspberry Pico #1
Comments
Ok, found the problem. You are currently waiting fixed 50 milliseconds after writing a command to the module UART. if you remove the |
Does this lib be used on raspberry pi rather than ESP32? |
It was developed for ESP32, but can be adapted for any microcontroller
supported by MicroPython which can do simple UART
Op wo 14 jul. 2021 om 09:53 schreef nicklf3nick ***@***.***>:
… Does this lib be used on raspberry pi rather than ESP32?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3LGQKMOMFNLZXFWOBZYVTTXU66DANCNFSM4ZAZZWBA>
.
--
Bezoek *Effevee's reisblog* op www.effevee.be
|
Thanks for your reply!! But i have a problem that RPi may not support the lib "machine", are there any solutions for it? |
A Raspberry Pi is not a microcontroller and does not support micropython.
The MicroPython code could be ported
to Python, but there would be timing problems as the Raspberry Pi runs an
operating system which has to do lots of things besides running a program.
Op wo 14 jul. 2021 om 11:23 schreef nicklf3nick ***@***.***>:
… It was developed for ESP32, but can be adapted for any microcontroller
supported by MicroPython which can do simple UART
Op wo 14 jul. 2021 om 09:53 schreef nicklf3nick *@*.***>:
Does this lib be used on raspberry pi rather than ESP32?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1 (comment)
<#1 (comment)>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN3LGQKMOMFNLZXFWOBZYVTTXU66DANCNFSM4ZAZZWBA
.
--
Bezoek *Effevee's reisblog* op www.effevee.be
Thanks for your reply!!
But i have a problem that RPi may not support the lib "machine", are there
any solutions for it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3LGQPRIQ3HS3FQXMLQ7ZTTXVJQJANCNFSM4ZAZZWBA>
.
--
Bezoek *Effevee's reisblog* op www.effevee.be
|
A while ago I modified it to work with Raspberry Pi, but I don't have it on GitHub. Basically you have to change how UART works i.e. replace machine.UART with pyserial module which enables Serial for Rasperry Pi. |
Thanks for your reply:) I tried it. Because i am unfamiliar with pyserial module and UART module, so there still some error occurred. |
Hi, first of all thanks for the great library! I successfully used it with esp32. I'm now trying to get it working on Raspberry Pico.
I've hardcoded the UART config in the
start()
function, since micropython Pico port doesn't haveuart.init()
built in. Therefore I initialise itt like this:However the start function is stuck on sending the config bytes:
In the above debug message, I'm printing the uart instance and the values of the three pins: m0,m1 and aux - in this case they are struck on high.
Do you know where the problem could be? Module works ok and emits the signal, if I write a string to it directly like this:
The text was updated successfully, but these errors were encountered: