Dear Dialog
We have your DA14531 modules, we would like to ask how can we use DSPS with doing no coding changes. We were under the impression we wont need to change any thng to make it work "Codeless"
We have tried all of the firmware versions with all the help from the forums.
We can get the module to work on the Pro Dev Kit. But as sson as we move away from the Dialog applications to start using a custom app that an embbed device will be using as a Serial Port. "The Serial Port Service (SPS) emulates a serial cable communication." This is a quote from your DSPS Page and it is all we require.
When using the codless firmware we cant get a connection to 3rd party custom apps. Did you as Dialog lock all your products to only use Dialog Software?
I have been trying to contact your techinical department here at AVNet in South Afica and they havent been able to help out.
Please email me back in regards to this
Hi Pieter Kapp,
Thanks for your question and for your interest in our DA14531MOD BLE solution. Could you please try to explain a bit more what your is issue is?
Form your initial post, I can understand that the DSPS is working perfectly with the Pro-DK, so I assume that you can connect to a peer device and send/receive data from/to it.
>>>But as sson as we move away from the Dialog applications to start using a custom app that an embbed device will be using as a Serial Port.
So, do you have a custom board with the module, and you are not able to use the DSPS? Is my understanding correct? Or you are using a custom mobile application?
If you flash the module with the DSPS firmware using theDialog Smartbond Flash Programmer for Windows OS, what is the behavior? Can you detect the device over the air?
If you could provide extra inputs or a high lever description of your project, it would be very helpful to understand what is getting wrong and provide support.
Thanks, PM_Dialog
Hi there yes we can detect the device perfectly. They all work just fine.
We have a custom PCB we developed and are thinking of using the DA14531 modules due to their low power consumption and their small size.
We also have our own custom app. But we use general serial comm ports over Bluetooth to test our connections. We are able to see the device and we can make a connection to the DSPS flashed module but after a second we drop the connection.
https://play.google.com/store/apps/details?id=de.kai_morich.serial_bluetooth_terminal&hl=en_US
We are working on a data logging product where the download link over Bluetooth so we can easily download the units with no external devices onto a mobile phone.
We have a U-art port between P0_06 and P0_05.
If you could please help us out that would be wonderful as we have about 20 modules on hand
Hi Pieter Kapp,
So, if I understood correctly, the main problem is the data pumping between your own board and the mobile phone. You mentioned that you are using P0_5 and P0_6 for the UART. However, the DSPS requires UART Hardware Flow Control (4 signals : URX, UTX, RTS, CTS) too.
Please se UART configuration in user_periph_setup.h
#if defined (__DA14531__)
#define GPIO_UART1_TX_PORT GPIO_PORT_0
#define GPIO_UART1_TX_PIN GPIO_PIN_6
#define GPIO_UART1_RX_PORT GPIO_PORT_0
#define GPIO_UART1_RX_PIN GPIO_PIN_5
#define GPIO_UART1_RTS_PORT GPIO_PORT_0
#define GPIO_UART1_RTS_PIN GPIO_PIN_7
#定义GPIO_UART1_CTS_PORT GPIO_PORT_0
#define GPIO_UART1_CTS_PIN GPIO_PIN_8
To do so, can you please indicate if you are using flow control in your setup?
Thanks, PM_Dialog
We have CTS and RTS linked to each other so the only issue we are sitting with is maintaing the bluetooth connection between our phones and the module we are sending very small single byte commands, so our main issue remains that we dont have a stable bluetooth link as advertised all over the website
Hi Pieter Kapp,
Could you please indicate how the DA14531MOD is placed in your custom board? Did you follow the Design Guidelines from the module’s datasheet?
Thanks, PM_Dialog