Getting a digital signal into the cylinder did not work with just a 433MHz transmitter and receiver, at least not at the speeds necessary for controlling hundreds of addressable LEDs. The next option was to use a more robust wireless chip and a programmable controller. I had some inexpensive NRF24L01 in stock, but I had not used them before. Another goody from my shelves was a Fio board which boasts onboard battery charging, which would be great if the cylinder power turned out to be unreliable.
Both boards were connected according to their pinouts and documentation. The NRF24L01 boards used the SPI communication specification, which is another gap in my experience. According to the short blurbs I read, it was typically used by a controller to monitor and control peripheral devices, and the "P" in SPI suggests as much. A handy Instructable suggested that controller-to-controller communication was possible.
When everything was connected, the Arduino MEGA's serial data showed blips on the radio spectrum, but the Fio spat out nonsense even though the code was identical. Perhaps a sketchy board was not the best place to start with an unfamiliar communication spec and hardware.
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2019-07-06
Arduino MEGA clone and OSEPP Fio
Both boards were connected according to their pinouts and documentation. The NRF24L01 boards used the SPI communication specification, which is another gap in my experience. According to the short blurbs I read, it was typically used by a controller to monitor and control peripheral devices, and the "P" in SPI suggests as much. A handy Instructable suggested that controller-to-controller communication was possible.
When everything was connected, the Arduino MEGA's serial data showed blips on the radio spectrum, but the Fio spat out nonsense even though the code was identical. Perhaps a sketchy board was not the best place to start with an unfamiliar communication spec and hardware.
Even under battery power, only garbage-data came out
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2019-07-06
Comments
Post a Comment