UART + non-connectable advertisement

RE: UART + non-connectable advertisement

Edvin — Fri, 16 Nov 2018 09:12:15 GMT

Hello,

Sorry for the late reply. I have been out of office this week.

First, I recommend that you do the app_timer_init() outside your main-loop, because in this case you will run app_timer_init() all the time, as long as you are connected, so it will stop and start all the time, and you will create timers just as often, and your app_timer_create() will return NRF_ERROR_INVALID_STATE from the second time it is called.

So move everything that you have inside if(connected == 1){} to before the for(;;)

What you actually don't do is to start the timer, using app_timer_start. This is also something you should do outside your main-loop. If not, you will just start it over and over.

I suspect that the if(connected) part is something you want in your timeout handler. You should initialize your timer in your main() application, before the for (;;) loop, and you can start your timer in the BLE_GAP_EVT_CONNECTED event in ble_evt_handler().

I recommend that you look at the ble_app_hrs example, as this sets up different timers. You can see in the main() function, that it calls timers_init(), application_timers_start().

The m_heart_rate_timer_id is quite similar to what you are trying to achieve. As you can see, the timer_id is defined near the top of main.c, APP_TIMER_DEF(m_heart_rate_timer_id);

If I were to tell you how to do it, it would be a copy paste of the main file from the ble_app_hrs example.

Best regards,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Sun, 11 Nov 2018 16:07:00 GMT

devzone.nordicsemi.com/.../2703.ble_5F00_app_5F00_uart.zip

RE: UART + non-connectable advertisement

hmcashan13 — Sun, 11 Nov 2018 16:03:19 GMT

I found what you are referring to and I am able to pass in data properly. What I am having trouble with is being able to call uart_event_handle constantly because the use case is having the bluetooth device emit UART signals in a regular interval with the temp and weight information. I am able to trigger the uart_event_handle by creating a variable of type app_uart_evt_t and passing it into that function. I do this in the main loop, but there is not enough of a delay between each call to this function. My thoughts were to either sleep the thread for a certain period of time which I have had zero success, and I am also trying to create an app_timer to repeatedly call this function in a certain interval but not successfully able to do so. Was wondering if you could help me create this timer or if you could think of a better way. Here is my main loop so far:

for (;;)
    {   
        if(connected == 1) {
              
              
             // create timer
              ret_code_t err_code;
              err_code = app_timer_init();
              APP_ERROR_CHECK(err_code);
              
              // variables to pass into app_timer_create
              app_timer_id_t * timer_id = APP_TIMER_DEF(10);
              app_timer_mode_t * timer_mode = APP_TIMER_MODE_REPEATED;
              app_timer_timeout_handler_t * timer_timeout_handler;
              
              // variable to pass into uart_event_handle
              app_uart_evt_t * p_event;
              // triggers data to be sent over UART
              uart_event_handle(p_event);

              // 
              err_code = app_timer_create(timer_id,timer_mode, timer_timeout_handler);
              APP_ERROR_CHECK(err_code);
        }
        
        idle_state_handle();
    }

But I'm getting a compiler error with the timer_id as I have no idea what to pass in. I also don't think I'm setting the timer_mode variable properly, and I don't know how I can set the timer_timeout_handler to call the part_event_handle function. I've also attached my source code.

RE: UART + non-connectable advertisement

Edvin — Fri, 09 Nov 2018 07:53:45 GMT

look for ble_nus_data_send();

It is used in the uart_event_handle() in main.c in that example.

You can use this function to send your data to the phone.

BR,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Fri, 09 Nov 2018 04:10:04 GMT

So I figured out how to read the sensors using the Saadc example. Now the task that I'm faced with is to relay this data through UART ble_peripheral to my iPhone/Android device. I am using the UART tutorial on ble_peripheral but I'm having a difficult time trying to find out where I pass these values to be sent over UART.

RE: UART + non-connectable advertisement

Edvin — Wed, 03 Oct 2018 07:54:59 GMT

The reason for why there isn't any tutorial for setting up sensors is because different sensors have different protocols. Some use UART, some use I2C, some use SPI, some are analogue (Like your weight sensor), some are something else (Like your Temp sensor. Not standardized).

The weight sensor uses changes the resistance depending on the weight, so you have to give it some voltage, and measure the voltage drop over the sensor. See the Saadc example on how to do this.

The temp sensor uses a custom protocol. It is called 1-wire-bus. See the datasheet section 1-wire bus system. I don't know what protocol it is, but it looks like a modified SPI or UART, using only one wire (in and output). You will have to experiment a bit with this one, or maybe you can find some tutorials (not from Nordic) on how to use this.

Best regards,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Wed, 03 Oct 2018 02:19:29 GMT

I don't know what you mean by protocol. I've been going through the data sheets for both the temperature sensor and weight sensor, but neither says anything about protocols. There also aren't any online tutorial for Segger in setting up sensors. I'm attaching links to both the data sheets for the sensors I'm using.

Temp Sensor: http://cdn.sparkfun.com/datasheets/Sensors/Temp/DS18B20.pdf

Weight Sensor: https://cdn-learn.adafruit.com/assets/assets/000/010/126/original/fsrguide.pdf

RE: UART + non-connectable advertisement

Edvin — Tue, 25 Sep 2018 07:12:29 GMT

Have you found any datasheets for your sensor? You need to know what protocol they use in order to read the data from the sensors.

RE: UART + non-connectable advertisement

hmcashan13 — Tue, 25 Sep 2018 02:35:50 GMT

I am using an fsr weight sensor (https://www.mouser.com/ProductDetail/SparkFun/SEN-09376?qs=WyAARYrbSnZm3k2OB4XwnA%3D%3D&gclid=Cj0KCQjwlqLdBRCKARIsAPxTGaVJJHUxsem5voGhSz6SU448bj-TSC2OffI2mAEgGkMw_j5pOLybGMsaAjlQEALw_wcB)

and I am using a DS18B20 (https://www.mouser.com/ProductDetail/SparkFun/SEN-11050?qs=WyAARYrbSnY0sq2HamgEvg%3D%3D&gclid=Cj0KCQjwlqLdBRCKARIsAPxTGaVBUMh3fjcHdQMuEvzNDSGc6LQwRu6e9y8JH7MUIWVe5jWGCddBblcaAtpOEALw_wcB)

RE: UART + non-connectable advertisement

Edvin — Mon, 24 Sep 2018 07:43:42 GMT

What protocol do your sensors use? SPI? UART? TWI/I2C?

BR,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Wed, 19 Sep 2018 21:47:55 GMT

The problem is that I don't know how to read the data from the sensors, and even if I were able to get this data, I don't know how I could send this data over UART. I know the sensors are setup properly and the device is capable of doing this because I have successfully done this through the Arduino IDE.

RE: UART + non-connectable advertisement

Edvin — Tue, 18 Sep 2018 06:25:14 GMT

And the problem is... ?

Are you getting values from your sensor, which are transferred? You don't want that? You want to process the sensor data before sending it? I am only guessing here. It would be easier if you describe the issue.

RE: UART + non-connectable advertisement

hmcashan13 — Mon, 17 Sep 2018 14:55:50 GMT

I’ve read through the tutorial and performed it fine, but my problem is doing the transfer of data over rx from within the code. This is because I will have a weight and temp sensor connected to my nRF52 device and will be sending the data it is receiving to send over UART to the iPhone.

RE: UART + non-connectable advertisement

hmcashan13 — Mon, 17 Sep 2018 14:54:22 GMT

RE: UART + non-connectable advertisement

Edvin — Mon, 17 Sep 2018 06:27:36 GMT

Look at the test guide for the ble_app_uart example:

http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fble_sdk_app_nus_eval.html&anchor=project_uart_nus_eval_test

You can use a terminal, like Termite to send strings to the nRF. Then use nRF Toolbox or nRF Connect for mobile to receive the data. You need to enable notifications if you use nRF Connect for mobile to see the data. See the guide on how to do that.

BR,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Fri, 14 Sep 2018 14:55:18 GMT

Both. I know my sensor works as I have it setup via Arduino but I don’t know where I can access this data on the uart example. Once I get this data, how do I then send it through rx. I’ve been trying to send test strings such as “hello world” just to test this thing out but can’t seem to find where this data should be placed for it to be transferred over rx.

RE: UART + non-connectable advertisement

Edvin — Fri, 14 Sep 2018 13:21:41 GMT

Ok. So you need to be able to pick up the beacon advertising packs from another device than the mobile phone when you are connected, then?

Regarding sending weight readings:

Could you describe what the problem is? Do you have difficulties getting the readings from the sensor, or do you have problems sending them over the link?

RE: UART + non-connectable advertisement

hmcashan13 — Fri, 14 Sep 2018 12:16:19 GMT

Edvin,

By being able to monitor and not range the beacon I’m referring to the ability of the device to only having the ability to monitor whether the beacon is in the particular region (monitor) as opposed to being able to also determine its exact distance. I’m also having trouble determining how to send data such as the weight readings that are being fed through the A1 port of the nRF device over uart (rx).

-Hudson

RE: UART + non-connectable advertisement

Edvin — Fri, 14 Sep 2018 07:15:01 GMT

I don't quite understand what you mean with "monitor the beacon but not range it with the current situation".

It is possible to scan at the same time that you are connected, but nRF Connect for mobile does not do this at this point in time. What do you want your application to do?

You advertise with the BLE uart service, and when you connect to it, you start advertising as a beacon. Is this new advertising because you want to measure the distance to the beacon?

Best regards,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Thu, 13 Sep 2018 12:11:07 GMT

Edvin,

The only issue with doing what you said is that I don’t have two phones, and the requirement for my project is for this to be done on one phone. Correct me if I’m wrong but I’ll be able to monitor the beacon but not range it with the current situation (using one phone) which is all I need to have happen.

-Hudson

RE: UART + non-connectable advertisement

Edvin — Thu, 13 Sep 2018 12:06:47 GMT

Well. When you program a device with the application used in nRF Connect, it will overwrite everything that is already on there, so you need an extra DK or Dongle in order to use nRF Connect for Desktop.

However, you shouldn't need that. If you have two cellphones, this should be possible.

Program your DK with the application that you wrote, then open nRF Connect on both phones. Connect to the device with one phone, and after that start scanning with the other phone. You should see the beacon advertisements.

Best regards,

Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Thu, 13 Sep 2018 12:01:04 GMT

Edvin,

No it’s the same device I’ve been using.

-Hudson

RE: UART + non-connectable advertisement

Edvin — Thu, 13 Sep 2018 06:40:44 GMT

Hello Hudson,

Just to clarify a couple of things. The device that you are trying to use with nRF Connect is not the same as the one you try to program your uart + beacon application to, right?

And the device that you are using with nRF Connect, is that a nRF DK or nRF Dongle?

-Edvin

RE: UART + non-connectable advertisement

hmcashan13 — Thu, 13 Sep 2018 02:14:50 GMT

Edvin,

I'm having trouble working with the nRF Connect application on my Mac. I have the bluetooth device connected to my Mac via J-Link and the error I am receiving is:

Error while setting up device 000801001102: No serial port available for device with serial number 000801001102

-Hudson

RE: UART + non-connectable advertisement

Edvin — Wed, 12 Sep 2018 12:52:23 GMT

Hello Hudson,

No. That is not what I meant. What I am trying to say is that the application that you sent is advertising as a beacon while it is in a connection.

Best regards,

Edvin