Wireless Pixel Brid...
 
Notifications
Clear all

Wireless Pixel Bridge

38 Posts
8 Users
0 Reactions
11.8 K Views
timon
Posts: 2149
Topic starter
(@timon)
Noble Member
Joined: 16 years ago

Called Lairdtech and talked to tech support. We decided that I've got to put together a writeup as to what's needed and they will pass it up the food chain. Before I do that I'm posting some questions to Nordic and will take their answers and add them to my email to Lairdtech plus CC my contact in Colorado so get his take on the issue.

I've gone over the nRF51's radio modulation specifications and it looks to be the same for both Nordic's proprietary protocol and Bluetooth. Since modulation is one of the main components in an EMI profile with data rate being the second I don't see any reason why using the proprietary protocol would make any difference as long as your at or below 1Mbps. I could see an issue if running at 2Mbps since they did not test at that data rate. They did test at +4 dBm with a 2.1dBi gain external antenna so that's taken care of. The one big difference is that bluetooth transmits using frequency-hopping spread spectrum and the proprietary protocol does not. Since that's not required in the ISM band I don't know if that will effect the certification. It could but I would normally expect it too if you tested using fixed channel then switched to frequency-hopping spread spectrum not the other way around.

BTW, I was looking at the ISM band allocation compared with the WiFi and Bluetooth channels I noticed that the range between 2478 to 2482 are not used by either one making these a somewhat more "Clean" set of channels. I suspect that those would be the best primary channels for the master to use. Since there are only 5 channels new slaves should scan them when they don't know what channel to use. That way the master could send a beacon packets so new slaves could find the operational frequencies. Since these packets are small they should not interfere with normal operations. Just something to think about.


Reply
timon
Posts: 2149
Topic starter
(@timon)
Noble Member
Joined: 16 years ago

Here is the version using a LairdTech BL600 module. This module is nothing more then the nRF51822 chip with all of the crystals, filter caps and U.FL connector that's shielded and solders directly to the board, no pin header. Not bad for $13.30 Qty 1 at Mouser. You can get one with a chip antenna however the module placement has many more restrictions so the RF section will work correctly. It's much easier using the U.FL connector and an external antenna so keep everything clean. Current plans are to overwrite LairdTechs code and use my own which is easy to do using the JTAG connector.

Changes other than the module are an updated power supply that can handle at least 6A at either 5 or 12V. See first post for updated specifications.


Reply
Posts: 853
(@roterhead)
Prominent Member
Joined: 15 years ago

Excellent find on these! Takes the FCC issues out of the equation....


Reply
timon
Posts: 2149
Topic starter
(@timon)
Noble Member
Joined: 16 years ago

Maybe, as thee may be an issue since they were tested with Bluetooth and we're running Nordic proprietary format but I don't see any technical issues doing that since the power levels and frequencies are the same. Only the protocol changes.


Reply
timon
Posts: 2149
Topic starter
(@timon)
Noble Member
Joined: 16 years ago

I got some initial information back from Nordic. They see no issues that would de-qualify the BL600 FCC certification if I used their proprietary protocol however I still need to discuss this with the manufacture. We're not home free yet but we're getting closer.

One point did come up however. I cannot support the 250Kbps data rate. I must run at least 1Mbps to stay withing the original certification under Part 15.247. To run run at 250Kbps would require certification under Part 15.249. This is because under .247 the 6dB bandwidth has to be at least 500Kbps. Sorry, not my rules. The nRF24L01 can still be talked to however they will have to run at 1 or 2 Mbps. Personally I don't see that as a major issue.


Reply
komby
Posts: 871
(@komby)
Prominent Member
Joined: 14 years ago
timon wrote:

One point did come up however. I cannot support the 250Kbps data rate. I must run at least 1Mbps to stay withing the original certification under Part 15.247. To run run at 250Kbps would require certification under Part 15.249. This is because under .247 the 6dB bandwidth has to be at least 500Kbps. Sorry, not my rules. The nRF24L01 can still be talked to however they will have to run at 1 or 2 Mbps. Personally I don't see that as a major issue.

Its not a major issue, but it will impact the range for sure. I don't know about the module u are proposing but I do know that when using the nRF24L01 going up to 1Mbps will cut reception range significantly, Cuts it down for me from 1000ft (line of sight) to 200 - 300 feet line of sight.


Reply
timon
Posts: 2149
Topic starter
(@timon)
Noble Member
Joined: 16 years ago

Since the source will be released under Creative Commons there is nothing to stop someone from making a program change. I don't expect any protocol difference with different speeds. For the official releases however 250 will be left out.

I'm planing to look at frequency hopping for the nRF51 protocol. It would definitely cut down on interference without effecting speed.


Reply
Posts: 853
(@roterhead)
Prominent Member
Joined: 15 years ago
timon wrote:

I'm planing to look at frequency hopping for the nRF51 protocol. It would definitely cut down on interference without effecting speed.

+1 on the concept of frequency hopping.


Reply
Page 4 / 4
Share: