(01-31-2016, 05:43 PM)khgoh Wrote: (01-31-2016, 03:59 PM)CanadianIceTech Wrote: (01-31-2016, 11:42 AM)stephen fleming Wrote: (01-30-2016, 11:00 PM)CanadianIceTech Wrote: For the temperature and humidity sensors, what's the accuracy with them? I have a big need for accurate temp and humidity sensors that can transmit data back to a host computer (preferably over wifi), but the temp sensor needs to be a probe that can accurately read ice temperature to 0.1F I think I found the board you are looking for:
http://wiki.pine64.org/index.php/POT#WiF...PMWF01A.29
And there is a temperature and humidity sensor plugin:
http://wiki.pine64.org/index.php/POT#I2C...PMSDP01.29
However there is no temperature probe or any one that I know of that has a I2C interface. Adafruit sells a temperature probe that is designed to be directly interfaced to a computer that I think has the accuracy you need:
https://www.adafruit.com/products/381
I do not know if it can be interfaced to the WiFi remote board. I think that is probably what I'm looking for. If I can use a $15 pine64 board in a case that has a large battery (to lengthen times between charging), plus the sensors it'd be far cheaper than what is commercially available. Ideally I'd like to have a wifi receiver on the outside of my office to collect the data from the sensors, then send to a laptop. This will be for monitoring, and also for remote alerts of warm temps caused by a power plant failure so I can try and save the ice while the issue is resolved with the ice plant. (http://www.eyeontheice.com/index.html)
I'm assuming this would be a good humidity sensor? https://www.adafruit.com/products/1293 More detail info and sensor/IC spec for board can be found at,
http://wiki.pine64.org/index.php/POT
For the I2C 4 wire connector, the pin are GND,SDA,SCL and 5V. For the five pin are GND, INTR, SDA, SCL and 5V. For some of the I2C device, they are build in with interrupt. With this interrupt, the CPU will have faster reaction time when certain condition is trigger. This also implied that if the CPU is waiting for the trigger condition, the CPU do not need to scan I2C device thus provide a more efficient use of I2C bus. 6 connectors ( 2pcs five pin and 4pcs of four pin I2C connector) is connect to TWI1-SCL/SDA channel in the pi-2 bus and another 6pcs of the connector is connected to TWI-SCL/SCA channel in the Pi-2 Bus.
All of the INTR pin for the total of 4pcs of connector is connected to separate GPIO of the bus indicating on the PCB.
Both of the I2C channel is going through a I2C Bus Repeater ( PCA9517) before connecting out to the connector. This will allow the I2C bus to run either in 5V I2C bus or 3.3V I2C bus.
The idea is that you can make use of the PineA64 as sensor Hub and all the sensor is connected to the PineA64 board. For longer distance that which you do not want to pull a long cable, you can make use of the Wifi Remote I2C ( http://wiki.pine64.org/index.php/POT#WiF...PMWF01A.29 ) to use a remote I2C repeater. The I2C connector on the board has the same I2C pin layout configuration. Furthermore, Wifi Remote I2C has a on board relay that allow for 240Vac on/off. the Currently we are still developing the firmware for the Wifi Remote I2C. Once it is ready, we will publish the source for the firmware.
On Humidity and Temperature Sensor, it is base on Silicon Lab Si7021. The sensor IC is mounted on the reverse side of the board. In term of accuracy, it is consider quite good, please refer to spec the for the detail. The only downside for this IC is that it do not have any address selector and only allow 1 sensor per I2C channel. But if more sensors need to be install, you can make use of the Wifi Remote I2C to allow more Humidity and Temperature Sensor to be installed.
As for the Ambient Light Sensor it is base on TSL2561T from AMS. The reason for the 5 pin I2C connector is that this sensor allow the CPU to configure a trigger point base on the received light intensity. Once it reaches the level, it will provide a trigger to the CPU.
../KH Goh
Thank you very much for the response. I'm really going to be looking more into this over the coming months and hopefully I can get something going by the next curling season in September.
A bunch of this is still new to me, but I am very interested in exploring this more and learning how to build things like these. The commercially available version of this starts at $5k with very few sensors, so if I can build something like this for about $100 total per sensor (pine64, addon-modules, battery, temp/humidity sensors, etc) that would be preferred.
01-31-2016, 07:00 PM
(This post was last modified: 01-31-2016, 07:03 PM by MichaelMeissner.)
(01-31-2016, 05:43 PM)khgoh Wrote: For the I2C 4 wire connector, the pin are GND,SDA,SCL and 5V. For the five pin are GND, INTR, SDA, SCL and 5V. For some of the I2C device, they are build in with interrupt. With this interrupt, the CPU will have faster reaction time when certain condition is trigger. This also implied that if the CPU is waiting for the trigger condition, the CPU do not need to scan I2C device thus provide a more efficient use of I2C bus. 6 connectors ( 2pcs five pin and 4pcs of four pin I2C connector) is connect to TWI1-SCL/SDA channel in the pi-2 bus and another 6pcs of the connector is connected to TWI-SCL/SCA channel in the Pi-2 Bus.
All of the INTR pin for the total of 4pcs of connector is connected to separate GPIO of the bus indicating on the PCB. From a connector design point of view, I sort of wish you didn't have both 5 pin and 4 pin i2c items. For example, if you wanted to have both the ambient light sensor and a generic 4 pin i2c device share the same wire connection to the pine64, you would need to craft a 4 pin to 5 pin cable (and plug in the ambient light sensor first) to hook up the second device. Or you have to run a second i2c connection for the second item back to the board.
In addition, if you had moved the interrupt pin to one of the ends, you might be able to use a 4 pin connection (without the locking tabs) directly.
I would hope you plan to sell 5 pin and 4 pin connector cables in the pine64 store once you open for retail business, as well as the raw connectors.
If you had standardized on just having 5 pin cables, it would have made the interconnection simpler. But there is no standardization in this area.
Of the i2c devices I've looked at, the pinouts are all over the place, that I just give up and use separate wires.
(01-31-2016, 07:00 PM)MichaelMeissner Wrote: (01-31-2016, 05:43 PM)khgoh Wrote: For the I2C 4 wire connector, the pin are GND,SDA,SCL and 5V. For the five pin are GND, INTR, SDA, SCL and 5V. For some of the I2C device, they are build in with interrupt. With this interrupt, the CPU will have faster reaction time when certain condition is trigger. This also implied that if the CPU is waiting for the trigger condition, the CPU do not need to scan I2C device thus provide a more efficient use of I2C bus. 6 connectors ( 2pcs five pin and 4pcs of four pin I2C connector) is connect to TWI1-SCL/SDA channel in the pi-2 bus and another 6pcs of the connector is connected to TWI-SCL/SCA channel in the Pi-2 Bus.
All of the INTR pin for the total of 4pcs of connector is connected to separate GPIO of the bus indicating on the PCB. From a connector design point of view, I sort of wish you didn't have both 5 pin and 4 pin i2c items. For example, if you wanted to have both the ambient light sensor and a generic 4 pin i2c device share the same wire connection to the pine64, you would need to craft a 4 pin to 5 pin cable (and plug in the ambient light sensor first) to hook up the second device. Or you have to run a second i2c connection for the second item back to the board.
In addition, if you had moved the interrupt pin to one of the ends, you might be able to use a 4 pin connection (without the locking tabs) directly.
I would hope you plan to sell 5 pin and 4 pin connector cables in the pine64 store once you open for retail business, as well as the raw connectors.
If you had standardized on just having 5 pin cables, it would have made the interconnection simpler. But there is no standardization in this area.
Of the i2c devices I've looked at, the pinouts are all over the place, that I just give up and use separate wires. Yes, we will be selling the wire with 4way to 4way connector , 5way to 5way connector and 4way to 5way connector.
(01-31-2016, 08:24 AM)MichaelMeissner Wrote: The board is mis-named (IMHO). From the title, it sounds like a board that can directly hook up 12 potentiometers (variable resisters like analog dials), but instead it is a shared i2c bus board. Yes, you can hook up 12 i2c devices, each of which provides a potentiometer and has a small microprocessor to do the i2c connection, but you can also hook up displays, switches, etc.
Thank you, MichaelMeissner - that was a great post and I learned a lot from it, much appreciated.
In return, this might be useful: I discovered that another meaning of the 'POT' in the naming of this accessory, in addition to "potentiometer", is "Peripheral On Top". ( Source) I don't know if that's a widely-recognised usage or if it is just used by PINE, but that may be what they're intending. (The whole 12C I2C is confusing enough for new players!)
I'm more familiar with POT == potentiometers, but I could understand it being Peripheral on Top, though I would argue that the board is still mis-named, because the peripheral's aren't on top, just the plugs for the peripherals.
The veroboard is more for peripheral on top usage, since you can wire the components directly to the prototype board. But that is a minor thing. However, unlike embedded microcontrollers like Arduino or Teensy, you probably won't be able to plug analog sensors directly into the pine64.
In addition, running an OS is problematical for things that need hard real time control (like neopixel/ws2812 leds). So, you would plug in the embedded MCU's to one of the standard buses (i2c, spi, serial, i2s, etc.), and send them commands to do their limited actions.
02-19-2016, 10:13 AM
(This post was last modified: 08-09-2021, 12:30 PM by Liuka Finke.)
There is a disconnect in their i2c designs. The normal i2c connection has 4 pins (ground, power, scl, sda) and most of the plugs have 4 pins.
But the ambient light sensor wants to pass a 5th pin (called nInt, which presumably is a pin that goes high when the state changes so that you can attach an interrupt so that you know when their is new data).
They put the nInt pin between ground and sda pins, which means you can't intermix 4 pin and 5 pin i2c connections.
http://www.7pcb.com
02-19-2016, 11:54 AM
(This post was last modified: 02-19-2016, 11:56 AM by MichaelMeissner.)
(02-19-2016, 10:13 AM)Liuka Finke Wrote: There is a disconnect in their i2c designs. The normal i2c connection has 4 pins (ground, power, scl, sda) and most of the plugs have 4 pins.
But the ambient light sensor wants to pass a 5th pin (called nInt, which presumably is a pin that goes high when the state changes so that you can attach an interrupt so that you know when their is new data).
They put the nInt pin between ground and sda pins, which means you can't intermix 4 pin and 5 pin i2c connections.
That was the point I made on January 31st in this thread.
Since I wrote that post, the bakerkit is up, they do sell 4 pin i2c cables, 5 pin i2c cables, and a 5 pin to 4 pin conversion cable. So you can intermix the 5 pin i2c devices with the 4 pin i2c devices as long you connect the 5 pin i2c devices to the POT board, and then use the 5 pin to 5 pin conversion cable to attach the 4 pin i2c devices.
Or, you can use the POT multi i2c bus board which has 4 connections for the 5 pin i2c devices (each of the connectors targets a different pin for interrupt), and 6 connectors for the 4 pin i2c devices.
Note, even if the pins lined up, you would not be able to plug a 4 pin cable into a 5 pin slot, since the plugs are shaped to only allow a fixed size plug to be used.
I have post up a diagram on the interconnection of the I2C cable http://wiki.pine64.org/index.php/POT#Int...ction_Wire
Please check it out.
I have ordered the PINE A64+ 2GB board with a Wifi 802.11BGN/ Bluetooth 4.0 Module and a power supply for it.
Now I would like to add a Humidity Temperature Sensor for PINE64 but I can't find out how to connect it.
Can some one advice me as to what I will need to connect it.
I think I may have to buy this first PINE64 12C Multiport POT , then a cable to connect it.
Is this the correct way to do this or is there a shorter way around it.
Thanks to everyone in advance for your help.
(02-22-2016, 10:53 PM)COMPUTIAC Wrote: I have ordered the PINE A64+ 2GB board with a Wifi 802.11BGN/ Bluetooth 4.0 Module and a power supply for it.
Now I would like to add a Humidity Temperature Sensor for PINE64 but I can't find out how to connect it.
Can some one advice me as to what I will need to connect it.
I think I may have to buy this first PINE64 12C Multiport POT , then a cable to connect it.
Is this the correct way to do this or is there a shorter way around it.
Thanks to everyone in advance for your help.
The best way to connect the I2C sensor is using the Pine64 I2C Multiport POT.
For Humidity Temperature Sensor, you need to use 4Way I2C cable to connect the Sensor to the I2C Multiport POT.
Please check out our wiki page below for more info.
http://wiki.pine64.org/index.php/POT
|
