StateFarm-STEM / hablogger

High Altitude Balloon Data Logging Project
Other
16 stars 9 forks source link

Pico Naming Consistency #128

Open jvanantwerp1 opened 9 months ago

jvanantwerp1 commented 9 months ago

Pin references change from hardware pin numbers to Pico GP pin numbers without consistency or warning. This was very confusing to the teams. My suggestion would be to use the Pico Pin References (VCC, GND, GP11, etc) because that matches to the provided diagram.

Mention could also be made of the hardware pin number.

tdeknecht commented 9 months ago

Do you have an example of this?

I do see the table references both the physical pin and GPIO pin. Both are important because the physical pin is faster to reference when wiring, but the GPIO pin is crucial for the coding portion which is used to interface with the device plugged in to the physical pin.

We can make this clearer, but first need to learn where in the lesson(s) the confusion exists.

pankonen commented 8 months ago

i think this is found on the Pico vs Pico W's as they use some of the pins for the wireless capability. It maybe worth while to look across versions of the Pico as I think there have been some cosmetic changes. (for example some have the reset button or debug port and others don't or header differences but pins SHUOLD be the same)

tdeknecht commented 8 months ago

@pankonen Do we know how many Pico vs. Pico W's we have? One way around this is to go with the Pico only and standardize on it. It might also be cheaper from a hardware standpoint.

pankonen commented 8 months ago

I don't know but would like to account for each as we have ordered this years already and I don't think I can add to the order. Normal Community purchased some of their own components to have smaller groups.

tdeknecht commented 8 months ago

We'll need @jvanantwerp1 to weigh in and give more context to the original issue. However, @pankonen , there is an existing issue related to the Pico and Pico W disparity: https://github.com/StateFarm-STEM/hablogger/issues/124

I still suspect this issue is in reference to physical pin locations and GP pin assignments. To help with this, I've added clarity in Lesson 2 for the difference between these two: https://github.com/StateFarm-STEM/hablogger/tree/main/python/raspberrypico/lesson-2#adjusting-our-code-to-blink-one-external-led

I will close this issue pending @jvanantwerp1 's response.