BLUNO Feature Request
visualxl 2014-07-18 16:34:06 3345 Views4 Replies Hi,
Its me again. How long has it been? haha
Anyway, just a quick update. I have been playing around with BLE Mini from Red Bear Lab for quite sometime. So, here are the features that I would like to suggest to be implemented on the BLUNO:
1. for CENTRAL, implement a device discovery feature where it only scan for BLE devices. It should also show useful information for each BLE devices like for example, "Device1: MAC_ADDRESS: UUID: RSSI: DISTANCE".
2. In regards to para 4, implement an AT command that allows you to specify the maximum devices that can be discovered.
3. In regards to para 1 and 4, implement an AT command that allows you to specify whether to use a whitelist or not during device discovery.
4. In regards to para 3, implement an AT command that allows you to specify the addresses that needs to be whitelisted. So, for example, if I want to whitelist 3 MAC addresses, its gonna be like "AT+WHITELIST=MAC1:MAC2". Or maybe, "AT+WHITELIST=MAC1", "AT+WHITELIST=MAC2".
Well.. That is all for today.
Its me again. How long has it been? haha
Anyway, just a quick update. I have been playing around with BLE Mini from Red Bear Lab for quite sometime. So, here are the features that I would like to suggest to be implemented on the BLUNO:
1. for CENTRAL, implement a device discovery feature where it only scan for BLE devices. It should also show useful information for each BLE devices like for example, "Device1: MAC_ADDRESS: UUID: RSSI: DISTANCE".
2. In regards to para 4, implement an AT command that allows you to specify the maximum devices that can be discovered.
3. In regards to para 1 and 4, implement an AT command that allows you to specify whether to use a whitelist or not during device discovery.
4. In regards to para 3, implement an AT command that allows you to specify the addresses that needs to be whitelisted. So, for example, if I want to whitelist 3 MAC addresses, its gonna be like "AT+WHITELIST=MAC1:MAC2". Or maybe, "AT+WHITELIST=MAC1", "AT+WHITELIST=MAC2".
Well.. That is all for today.
2014-08-25 19:02:08 Yeah, it will be a very good function.
But it is still in development phase. Let us be patient. Grey.CC
But it is still in development phase. Let us be patient.
Grey.CC 2014-08-23 07:51:26 Hello 
i created an account just to say that it'd be AWESOME if you could implement the device discovery (not necessarily CONNECT, just list the visible MAC addresses), especially IBEACON discovery. it'd open up a whole new range of possibilities/applications
thanks in advance for considering this uiteca
i created an account just to say that it'd be AWESOME if you could implement the device discovery (not necessarily CONNECT, just list the visible MAC addresses), especially IBEACON discovery. it'd open up a whole new range of possibilities/applicationsthanks in advance for considering this
uiteca 2014-07-18 19:26:14 Ah you mean device discovery mode?
I didn't think of that yet and not sure whether it has some big implication or not.
But I think, if the whitelist function can be implemented for both CENTRAL and/or PERIPHERAL, the blacklist/hide function is redundant. visualxl
I didn't think of that yet and not sure whether it has some big implication or not.
But I think, if the whitelist function can be implemented for both CENTRAL and/or PERIPHERAL, the blacklist/hide function is redundant.
visualxl 2014-07-18 18:36:50 Hello Visualxl,
Wow, it is very glad to see you again.
Good advice! I will let the developer know your suggestion. Maybe he will add some new functions in the new firmware.
What is about blacklist? or hide function?
Grey.CC
Wow, it is very glad to see you again.
Good advice! I will let the developer know your suggestion. Maybe he will add some new functions in the new firmware.
What is about blacklist? or hide function?
Grey.CC 