-
Notifications
You must be signed in to change notification settings - Fork 9
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
"Monster Blood" CLSLab: Liquid Motor does not respond to Pi #255
Comments
Could you include a picture of the setup? Also, please copy the main.py file (or include the link to the one you're using). There have been some weird things with certificates lately (will likely have a fix in the coming month) #253, so I recommend regenerating your certificate. Are you using a custom broker? Also, can you verify whether or not you can use https://huggingface.co/spaces/AccelerationConsortium/light-mixing with a light-mixing demo that you have on hand? |
Some other random bits present in https://ac-microcourses.readthedocs.io/en/latest/courses/hello-world/1.1-running-the-demo.html It sounds like you've already tried multiple networks (e.g., phone hotspot). |
|
I regenerated the certificate, but the issue still persists. I have also tried the light demo, and the sensor error still pops up, I guess it is the sensor problem rather than motors? it seems like the main.py can't find the as7341_sensor module as well. |
What is the output from both the notebook and from the microcontroller when you're running it? Have you tried connecting to a mobile hotspot in extended compatibility mode?
Can you clarify the other questions? |
The Pi seems to be getting commands as the lights blink when we start the
Instantiation
on Google Colab, and the PI seems to be working and waiting for experiment requests. Still, the motors are not doing anything, which resulted in the sensor running timeout. We tried different boards, and the problem still exists.It was later found that the issue is not on the board as all boards or networks face the same issue - it should be a software one.
The text was updated successfully, but these errors were encountered: