Hi there …
I’m new to Particle, and this is my first post on the forum, so just hoping the style and substance of this note comport with local norms.
I’m trying to build some simple tutorials for a course that I teach remotely. I’ve using Jupyter notebooks on Google Colab extensively for teaching data and computationally oriented courses, and am trying a few experiments to see if it could work with Particle, too.
Here’s a proof of concept demonstrating Colab with Tinker: https://colab.research.google.com/drive/1i0wWU-7SnZ19a6OGQN5XnckWlNQDtPR2#scrollTo=ERsWOhNw5NPg
Here’s a proof of concept demonstrating Particle cli on Colab: https://colab.research.google.com/drive/1eybJfx2naCsVBOjTbzEu6GEK6cHu-h5I#scrollTo=ERsWOhNw5NPg
This third attempt is s where the trouble starts: https://colab.research.google.com/drive/1GK5Ogga8ts8vfS9493wmEAExFZ3I3N7u#scrollTo=TcUKDiWOsvt1
There are some issues:
The documentation for the Particle cli library says to use the “add” command to download and install a library. See: https://colab.research.google.com/drive/1GK5Ogga8ts8vfS9493wmEAExFZ3I3N7u#scrollTo=TcUKDiWOsvt1 This seemed to have no effect in the notebook above. But “view” command did download and install a library. Is the documentation correct?
Compiling results in an "Found unsafe content Found: #include “/” error. I could find no documentation on how to override this message. Any advice?
I’m new to Particle, so these are likely newb errors. Any help would be appreciated.
Jeff
ScruffR
October 20, 2020, 12:01pm
2
Welcome to the community
For your first point, particle library add will only add a dependency entry to the project.properties file and the cloud build will then pull that referenced library in but the docs don’t tell otherwise either - no mention of downloading and installing the library AFAICT.particle library copy which will place the library inside your project at its intended place (particle library view will not do that).
For the second question it’s hard to tell without the code as I’m not going to sign up for the colab link
Thank you for explanation regarding “add” vs “copy”. It’s now clear that I’m not setting up the project correctly inside Colab, so will tackle that next and see if this will resolve my problems. Thanks.
ScruffR
October 20, 2020, 12:59pm
4
When running particle library add or particle library copy you should execute that from the location within your project folder where the project.properties file resides.particle project create to properly setup a new project structure.
1 Like
Thanks again. This advice has been spot on. I can create a project, add libraries, copy libraries to the /lib subdirectory, and compile an empty project. The problem now is that compiling fails because it can't find the library subdirectory. Here's the minimal file
#include "Grove_4Digit_Display"
void setup() {
void loop() {
Here's the message
Compiling code for argon
Including:
attempting to compile firmware
mkdir -p target/
make -C ../../../user
It should be:
#include "Grove_4Digit_Display.h"
It’s currently missing the .h part.
2 Likes
Well, that was embarrassing. Thanks, I’ve got a skeleton working in Google Colab.
2 Likes
We’ve all been there and we’ll all be back there.
2 Likes
Thanks. For what it’s worth, I’m pleased with how these notebook are turning out. I realize that notebooks don’t hold a candle to the Particle IDE, but it is one way to structure a document for teaching and exposition. It works surprising well.
https://jckantor.github.io/cbe-virtual-laboratory/
1 Like
system
April 26, 2021, 10:55am
10
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
