The power of the P1 and P2 is that you can use a pin for anything. .....
Why buy a device with a dedicated bus interface.
Mike
@iseries Could you please elaborate a bit more ?
I'd say Ken has already given an answer to your question in his opening post or at least that's how I see it. He just wants the forum members to add or remove a module and state the reason behind such a move.
There are users who need these drivers badly to speed things up in development and certainly there are some, like myself, who simply lack the abilities or time to write their own drivers for a commonly available component, at least at the moment.
Or maybe you are referring to some other post, mine possibly ? If that's the case, I'll explain.
Yes, this is correct and thanks for all the posts. Many such systems and form factors exist: shields, hats, Feathers, Qwik, Clicks -- all from different suppliers. We're just looking at the MikroE products because they seem to provide the closest prototype "match" to what we're looking for with the P2's introduction. They have a wide support base for other commercially-available microcontrollers of all types, and we need to swim in a larger sea with other fish to make the P2 more viable as a product line. Further, they have over 1,200 boards in their series.
Hardware is one part of speeding adoption/prototypes, but the drivers are ultimately the most important thing we need to provide. Since Parallax started, and since we introduced the P1, many companies have jumped into the "breakout board" business that it's an absolute race to the bottom. We're just picking the fastest horse (MikroE), knowing it has a long career and a really well-lead team.
As a side note, ST and Microchip adopted the MikroE "socket" for a purpose. And these are giants. I can't imagine why Parallax would look elsewhere. This, in my view, is a move in a right direction and I, and probably many more members of this forum, hope to benefit from it too.
Thanks, Parallax.
If the list is not finalized yet please consider these cheap click boards with the ATECC508/608 or any other of the kind ME makes.
I can see great potential in these. Security is "the topic" this days and it's importance will not fade away with time. Quite the opposite, in my view.
The big fishes have libraries for these chips, so why shouldn't Parallax have one ?
These modules are maybe a niche products for many and dirt cheap but if it's a right horse...
It's a great move. Many of us have great ideas for the Prop but then we have to worry about how to interface to the outside world. We need proven workable solutions and the Mikroe guys provide schematics so that, once proven, the same circuitry can be grafted on to one board.
I suppose there'd be a fair amount of enthusiasm if we provided objects and libraries for these Clicks. You'd be able to combine a few sensors and a VGA/HDMI display for some impressive stuff, pretty quickly.
You've got of bunch of URL which give a 404 error.
It appears to be any URL with a capital "C" used in "Click" will produce the error. When I change the one I tested to a lower case "c" the URL works.
Here's the RTC with the correct link. https://www.mikroe.com/rtc-10-click
We're leaning hard on @JonnyMac and there's only one of him.
I'll do my best with the Spin side of things -- we'll definitely need some help on the C, BASIC, and Forth side. My intention is to create a generic coms object for the modules; specific code for modules would be built on top of this.
Ken,
Yes I have a lot of Parallax stuff, but I dunno if I'd call it a museum :P
JonnyMac,
I already have I2C and SPI stuff up and running on FlexC (ported simpletools.h stuff), so it'll probably be fairly similar. Assuming most of these modules will use serial, I2C, or SPI.
Mikroe Click standard clearly has a huge following; imagine a Click module with a P1 + headers and putting it out there?
I second Mickster on this one. Brilliant. We'd loose some precious pins as Click's have only 16 of them and some are already assigned like power or buses but nonetheless.
Great idea and opens up a lot of possibilities. I could certainly use one of such P1 Clicks myself.
@Mickster IOs, I meant IOs. P1 has 32 usable while a Click board has only 16 pins so leaving out the power pins we end up with 14 free on the Click to break out a maximum of 14 out of 32 IOs. This was what I tried to say. Unless, of course, we use a double click board and break out the rest of the P1 IOs to them.
Just ran across this module that has 1 Mbit SRAM with automatic backup to EEPROM upon power failure. No battery needed, works off of the onboard capacitor. The SRAM is restored from EEPROM upon power up. Great for data loggers.
Comments
Yes, this is correct and thanks for all the posts. Many such systems and form factors exist: shields, hats, Feathers, Qwik, Clicks -- all from different suppliers. We're just looking at the MikroE products because they seem to provide the closest prototype "match" to what we're looking for with the P2's introduction. They have a wide support base for other commercially-available microcontrollers of all types, and we need to swim in a larger sea with other fish to make the P2 more viable as a product line. Further, they have over 1,200 boards in their series.
Hardware is one part of speeding adoption/prototypes, but the drivers are ultimately the most important thing we need to provide. Since Parallax started, and since we introduced the P1, many companies have jumped into the "breakout board" business that it's an absolute race to the bottom. We're just picking the fastest horse (MikroE), knowing it has a long career and a really well-lead team.
Ken Gracey
Thanks, Parallax.
If the list is not finalized yet please consider these cheap click boards with the ATECC508/608 or any other of the kind ME makes.
I can see great potential in these. Security is "the topic" this days and it's importance will not fade away with time. Quite the opposite, in my view.
The big fishes have libraries for these chips, so why shouldn't Parallax have one ?
These modules are maybe a niche products for many and dirt cheap but if it's a right horse...
Just give it a second thought, please.
Maciek
It's a great move. Many of us have great ideas for the Prop but then we have to worry about how to interface to the outside world. We need proven workable solutions and the Mikroe guys provide schematics so that, once proven, the same circuitry can be grafted on to one board.
Several choices but this seems to be the most feature-packed at this price around $25 (and we will sell these at the listed prices).
Ken Gracey
I believe it really doesn't matter all that much since they all provide NMEA-formatted output and are somewhat commodity-interchangeable.
Any preferences please say so.
Thanks,
Ken Gracey
4-20 mA R Click https://www.mikroe.com/4-20ma-r-click
4-20 mA T Click https://www.mikroe.com/4-20ma-t-click
AIR QUALITY Click https://www.mikroe.com/air-quality-click
Brushless 3 Click https://www.mikroe.com/brushless-3-click
eINK Click - bundle https://www.mikroe.com/e-paper-bundle-2
Environment Click https://www.mikroe.com/environment-click
LightRanger 4 Click https://www.mikroe.com/lightranger-4-click
LSM6DSL Click https://www.mikroe.com/lsm6dsl-click
OLED C Click https://www.mikroe.com/oled-c-click
Ozone 2 Click https://www.mikroe.com/ozone-2-click
PROTO Click https://www.mikroe.com/proto-click
Proximity 3 Click https://www.mikroe.com/proximity-3-click
Relay2 Click https://www.mikroe.com/relay-2-click
RS485 Click 3.3V https://www.mikroe.com/rs485-33v-click
mikroBUS Shuttle Bundle https://www.mikroe.com/mikrobus-shuttle-bundle
Stepper 2 Click https://www.mikroe.com/stepper-2-click
WiFi BLE Click https://www.mikroe.com/wifi-ble-click
RTC 10 Click https://www.mikroe.com/rtc-10-click
Nano LoRa Click https://www.mikroe.com/nano-lora-click
Compass/Accel/Gyro https://www.mikroe.com/mpu-9dof-click
Nano GPS Click https://www.mikroe.com/nano-gps-2-click
CAN SPI Click https://www.mikroe.com/can-spi-33v-click
I suppose there'd be a fair amount of enthusiasm if we provided objects and libraries for these Clicks. You'd be able to combine a few sensors and a VGA/HDMI display for some impressive stuff, pretty quickly.
Ken Gracey
It appears to be any URL with a capital "C" used in "Click" will produce the error. When I change the one I tested to a lower case "c" the URL works.
Here's the RTC with the correct link.
https://www.mikroe.com/rtc-10-click
Will repair those links now.
Ken Gracey
Parallax Museum of San Diego, Curated by investor Roy Eltham
It would be great to have some driver help. We're leaning hard on @JonnyMac and there's only one of him.
Ken
Yes I have a lot of Parallax stuff, but I dunno if I'd call it a museum :P
JonnyMac,
I already have I2C and SPI stuff up and running on FlexC (ported simpletools.h stuff), so it'll probably be fairly similar. Assuming most of these modules will use serial, I2C, or SPI.
The shuttle bundle is interesting I did now know you could do that
Keen to have a go at the lightranger.
You can download code examples (Pascal, Basic, C) here and use them for templates to get started.
https://libstock.mikroe.com/projects/view/3845/6dof-imu-14-click
I second Mickster on this one. Brilliant. We'd loose some precious pins as Click's have only 16 of them and some are already assigned like power or buses but nonetheless.
Great idea and opens up a lot of possibilities. I could certainly use one of such P1 Clicks myself.
Just ran across this module that has 1 Mbit SRAM with automatic backup to EEPROM upon power failure. No battery needed, works off of the onboard capacitor. The SRAM is restored from EEPROM upon power up. Great for data loggers.
https://www.mouser.com/ProductDetail/Mikroe/MIKROE-4129?qs=vmHwEFxEFR%2BAljS1d5JL7w==
nice
Anybody using the Clicks in projects?
I also like there is a PDIP available :
https://www.digikey.com/en/products/detail/microchip-technology/47C16-I-P/6236456