- Posts: 71
- Karma: 1
- Thank you received: 4
Support for Raspberry Pi 2.
9 years 2 months ago - 9 years 2 months ago #320
by skywatch
Replied by skywatch on topic Support for Raspberry Pi 2.
I have one now, will try and test it today!
Well setup and install went OK, no problems. But running it doesn't go well. I have the EasyIoT.exe start, but it never seems to 'see' the nrf24l01+ and stays there.
I have checked the blacklist and its empty(!) - So that's good. I enabled SPI in raspi-config too. I have connected it as per a 'normal' pi but also noticed that on the Model B+ there's a second set of pins with mosi, miso and sck, so I tried them too. Still no luck.
lsmod shows the spi module loaded and ls /dev/ shows both spi0.0 and spi1.0 so it's not that.
Maybe they changed the gpio header? I have tried 2 nrf24 modules just to be sure it's not a bad module and have assumed the gpio pins are the same as the model B+ (which, with no info on the raspberry pi web site seems reasonable to me!).
This is with kernel 3.18.5-v7+ & 3.18.6 tried too...
Unfortunately that was when the sound system started having a bad day and I got bogged down into fault finding that for an hour or two (bad Chinese power supply in the end!)....
Any ideas..???...
Skywatch.
Well setup and install went OK, no problems. But running it doesn't go well. I have the EasyIoT.exe start, but it never seems to 'see' the nrf24l01+ and stays there.
I have checked the blacklist and its empty(!) - So that's good. I enabled SPI in raspi-config too. I have connected it as per a 'normal' pi but also noticed that on the Model B+ there's a second set of pins with mosi, miso and sck, so I tried them too. Still no luck.
lsmod shows the spi module loaded and ls /dev/ shows both spi0.0 and spi1.0 so it's not that.
Maybe they changed the gpio header? I have tried 2 nrf24 modules just to be sure it's not a bad module and have assumed the gpio pins are the same as the model B+ (which, with no info on the raspberry pi web site seems reasonable to me!).
This is with kernel 3.18.5-v7+ & 3.18.6 tried too...
Unfortunately that was when the sound system started having a bad day and I got bogged down into fault finding that for an hour or two (bad Chinese power supply in the end!)....
Any ideas..???...
Skywatch.
Please Log in or Create an account to join the conversation.
9 years 2 months ago #350
by EasyIoT
Thank you for report. Sorry for late response. I didn't see this post. The correct SPI is 0.
It looks like that BCM2836 is not directly compatible with old BCM2835.
Can you test one more thing? Can you test Raspberry Pi GPIO driver? It also uses BCM. Just go under drivers and enable one pin as DO - (not first two because they are sometimes used). Select Raspberry Pi B+ as board. Then switch in WEB UI this DO and measure voltage to check if it works.
Replied by EasyIoT on topic Support for Raspberry Pi 2.
skywatch wrote: I have one now, will try and test it today!
Well setup and install went OK, no problems. But running it doesn't go well. I have the EasyIoT.exe start, but it never seems to 'see' the nrf24l01+ and stays there.
I have checked the blacklist and its empty(!) - So that's good. I enabled SPI in raspi-config too. I have connected it as per a 'normal' pi but also noticed that on the Model B+ there's a second set of pins with mosi, miso and sck, so I tried them too. Still no luck.
lsmod shows the spi module loaded and ls /dev/ shows both spi0.0 and spi1.0 so it's not that.
Maybe they changed the gpio header? I have tried 2 nrf24 modules just to be sure it's not a bad module and have assumed the gpio pins are the same as the model B+ (which, with no info on the raspberry pi web site seems reasonable to me!).
This is with kernel 3.18.5-v7+ & 3.18.6 tried too...
Unfortunately that was when the sound system started having a bad day and I got bogged down into fault finding that for an hour or two (bad Chinese power supply in the end!)....
Any ideas..???...
Skywatch.
Thank you for report. Sorry for late response. I didn't see this post. The correct SPI is 0.
It looks like that BCM2836 is not directly compatible with old BCM2835.
Can you test one more thing? Can you test Raspberry Pi GPIO driver? It also uses BCM. Just go under drivers and enable one pin as DO - (not first two because they are sometimes used). Select Raspberry Pi B+ as board. Then switch in WEB UI this DO and measure voltage to check if it works.
Please Log in or Create an account to join the conversation.
9 years 2 months ago - 9 years 2 months ago #352
by skywatch
Replied by skywatch on topic Support for Raspberry Pi 2.
No worries!
I have the server running now.
Lots of updates and upgrades and now it works but I don't know if EIoT needs the nrf24 to load before it works or not.
Tomorrow I will make a sensor and test the RF side of things.
I have some of the newer 'mini' nrf24l01+ modules to play with as well now, much smaller (but it's going to be very challenging to solder the thin wires to the holes on the PCB).
EDIT: I have tested the pi's SPI and it's working, so I am not sure why the info from the nrf registers are not being displayed at the start of EIoT.
EDIT2: When I go into config and select the MySensors driver it is disabled. I enable it but don't get a dialogue box open. When I exit and re-check it's disabled again.
This would appear to be an issue.
EDIT3: The GPIO test failed. I set pin7 (as in the example) to 1 and 0, but pin 7 remained at 3.3V all the time. I have seen mention of a new 'base' for the GPIO header, so that's something for you to look into.
I used the raspberry pi B+ configuration in config for this test. Will test again with pi B later......
Skywatch.
I have the server running now.
Lots of updates and upgrades and now it works but I don't know if EIoT needs the nrf24 to load before it works or not.
Tomorrow I will make a sensor and test the RF side of things.
I have some of the newer 'mini' nrf24l01+ modules to play with as well now, much smaller (but it's going to be very challenging to solder the thin wires to the holes on the PCB).
EDIT: I have tested the pi's SPI and it's working, so I am not sure why the info from the nrf registers are not being displayed at the start of EIoT.
EDIT2: When I go into config and select the MySensors driver it is disabled. I enable it but don't get a dialogue box open. When I exit and re-check it's disabled again.
This would appear to be an issue.
EDIT3: The GPIO test failed. I set pin7 (as in the example) to 1 and 0, but pin 7 remained at 3.3V all the time. I have seen mention of a new 'base' for the GPIO header, so that's something for you to look into.
I used the raspberry pi B+ configuration in config for this test. Will test again with pi B later......
Skywatch.
Please Log in or Create an account to join the conversation.
Time to create page: 0.221 seconds