跳到主要内容

PAN1740A

Bluetooth®5.0尺寸小

PAN1740A

All the advantages of theDA14585.with greater flexibility!

Pan1740a是Pan1740的优化版本,提供了减少的启动时间并支持最多8个连接,以便更大的灵活性来创建更多高级应用程序。亚博国际官网平台网址它可以用作独立应用处理器或托管系统中的数据泵。该设备针对需要支持语音命令和运动/手势识别的远程控制单元(RCU)进行了优化。Bluetooth®低能量固件包括L2CAP服务层协议,安全管理器(SM),属性协议(ATT),通用属性配置文件(GATT)和通用访问配置文件(GAP)。支持Bluetooth®SIG发布的所有配置文件以及自定义配置文件。松下成本工程降低了成分计数和应用BOM。采用完全屏蔽的外壳,集成晶体振荡器和芯片天线,PAN1740A的占地面积为9.0 x 9.5 x 1.8 mm,使其成为可用的最小蓝牙低能量模块之一。

特征

Bluetooth® Low Energy 5.0

ARM®Cortex®-M0,96KB SRAM,64KB OTP

Bluetooth® 5.0 Low Energy core features and High Duty Cycle and Efficient Non- Connectable Advertising

Autonomous Bluetooth® Low Energy stand-alone operation possible

电流消耗:4.9mA Tx(0dBm)/ 4.9ma Rx(1Mbps)

SMT Size: 9.0mm x 9.5mm x 1.8mm

集成天线和预认证

亚博国际官网平台网址

Industrial IoT

  • Connected Sensors
  • 人类界面设备

智能家居/建筑

  • 智能照明系统
  • 计量
  • Smart Home Nodes

Beacons

  • Proximity Tags
  • 追踪器
  • 遥控器

Stay connected

通过我们的全球销售办事处直接与我们联系,或联系我们的全球经销商和代表之一。

Inquiries Distributors and Representatives 注册新闻通讯
产品Brief
名称 Date 版本
Pan1740ABluetooth®5.0低能量模块传单(636.71 KB) 01/11/2019 Rev. 1.0
PAN1740A Bluetooth® 5.0 Low Energy Module Product Brief(405.88 KB) 01/11/2019 Rev. 1.0

订单信息

ENW89852A1KF – PAN1740A

ENW89852AXKF - Pan1740A评估USB棒

ENW89852AWKF - Pan1740A评估套件

Buy now

产品 Shop
enw89852awkf. digikey. Mouser
回到结果

2 months ago

No data when trying to start streaming data before enabling notifications

Posted bygme_johannes15分 5 replies
0 upvotes

Hi Dialog support,

We are developping a project based on the IoT sensor SDK (DA14585 IoT Multi Sensor Development, v6.160.4)
If we connect to a device and
1.开始流数据(发送0x01至Char UUID 2EA78970-7D44-44BB-B097-26183F402409)
只有在此之后
2.启用侦听通知(Char UUID 2EA78970-7D44-44BB-B097-26183F402410)
the sensor is not sending any data.

在此之后,即使我们断开连接,我们也不会从设备接收数据,重新连接并切换序列
1.启用侦听通知和
2。start streaming data.

这是预期的行为吗?如何让设备再次开始发送数据?

Thank you
凯瑟琳娜

2 months ago

PM_DIALOG.

嗨gme_johannes,

Thanks for your post. Since it is a custom code, could you please describe a bit more what is the issue? If I am not mistaken and according to the title, the device is not sending data only when the notifications are disabled by the peer device. In that case, the notifications should be enabled from the peer device in order to start sending data over the air.

谢谢,PM_DIALOG.

2 months ago

gme_johannes 15分

正如我不知道您还在监控旧论坛,我正在重新发布我的评论
no data when trying to start streaming
here.

嗨pm_dialog,

Thank you for coming back to us. Yes, I know that notifications have to be enabled in order for notifications to be sent (kind of obvious :)). But only enabling notifications will not start sending data over the air. In order for this to happen, streaming data has to be started too. And here it depends on the sequence in which this is enabled and started:
- 首先开始流式传输数据和第二个启用通知_does not_开始发送数据。
- First enable notification and second start streaming data _does_ start sending data.

我们确实启用通知:当启用通知时,设备未发送数据(在空中)_AFter_我们发送命令以开始流数据。

Our code is based on IoT MSK v6.160.4. We did not implement any custom code for receiving notifications or for sending the command to start streaming data.
我们特别没有改变负责编写和发送传感器数据的代码。

这是在以下文件和函数中实现的:
- file user_dws_reports.c,函数bool user_prepare_multi_sensor_report(...)
- file user_dws_reports.c,函数void user_add_multi_sensor_report(...)
- file user_dws_reports.c,function void user_send_multi_sensor_report(...)
- file user_dws_task.c,function user_dws_val_ntf_cfm_handler(...)

When I connect to the serial debug console (to see the results of any archprintfs) I can see the following error message
“错误:删除NTF - <计数器>优秀NTFS”如果计数器(NTF_SENT_CNTR)是大于15的数字(有阈值#define(d)开始打印此错误消息而不是组成和发送数据报告- 在上面输入的IOT MSK V6.160.4中配置,并未被我们触及)。

每次Streaming数据都停止(发送命令停止流数据)并重新启动(发送命令开始流数据)此计数器增加两个(无论是否启用或禁用通知)

This behaviour persists when the device is disconnected from the peer device and reconnected.

通知发送计数器NTF_SENT_CNTR在功能中增加
user_send_multi_sensor_report(...)

user_dw user_send_command_reply(…)(在文件s_reports.c)
并在功能下减少
user_dws_val_ntf_cfm_handler (in file user_dws_task.c)

通过向DWS_CONTROL_CHAR发送0x01来启动流数据(UUID 2EA78970-7D44-44BB-B097-26183F402410)
Streaming data is stopped by sending 0x00 to dws_control_char

This entre behaviour described above has not been altered by us. So my question reformulates to:

是行为,设备无法从丢弃的通知中恢复,想要
(a)即使设备断开并重新连接?
(b)在启动流时,启用流_Before_通知(它不会在流启动时发生_AFter_通知时)?

I hope this describes it clearer.

Thank you
凯瑟琳娜

1 month ago

PM_DIALOG.

嗨Katharina,

这IOT MSK application code provides the wrbl_dws_control_char characteristic (wriatable) and wrbl_dws_control_reply_char (notifiable) for configuring and controlling the device

So, every time the device is connected to a Central device, first you should write 0x01 to the Control Point ( wrbl_dws_control_char) characteristic, enable the notifications in the wrbl_dws_control_reply_char, and then start streaming data. If the device disconnects and re-connects, then the aforementioned procedure should be followed again.

If the Control Point characteristic is written with 0x01 and start streaming data without enable the notifications in the wrbl_dws_control_reply_char, you will not see the streaming data in the peer device because the notifications should be enabled.

谢谢,PM_DIALOG.

1 month ago

gme_johannes 15分

Dear PM_Dialog,

您正在描述的程序1。将0x01写入控制点,2。enable notifications for wrbl_dws_control_reply_char3.enable notifications for wrbl_dws_multi_sens_char)不会使设备发送数据at all但是将其留在无法恢复的状态下(通过例如,断开和重新连接)除非完全重新启动!(这是由于我在上面的冗长帖子中解释的ntf_sent_cntr)

Contrary to your statement如果我将0x01写入控制点,我将无法为WRBL_DWS_CONTROL_REPLY_CHAR启用通知(但仅启用WRBL_DWS_MULTI_SENS_CHARS的通知),我会收到传感器数据。

Obviously, I will not receive sensor data if I do not enable notifications for wrbl_dws_multi_sens_char.

correct procedure for receiving datawithout having to reboot/reset it regularly is

  1. enable notifications for wrbl_dws_control_reply_char
  2. enable notifications for wrbl_dws_multi_sens_char
  3. 通过将0x01写入控制点来开始流传输数据

But this was not my question.

My question was(而且我只用我的最后一个回复复制它):

是行为,设备无法从丢弃的通知中恢复,想要
(a)即使设备断开并重新连接?
(b)在启动流时,启用流_Before_通知(它不会在流启动时发生_AFter_通知时)?

Thank you
凯瑟琳娜

23 hours ago

gme_johannes 15分

Dear PM_Dialog,

In order to resolve the above described issue we now manually reset the ntf_sent_cntr to 0 when

  • writing 0x00 to Control Point (STOP_COMMAND / stop streaming)

什么时候

  • 断开设备的连接

This resolves the described issue that the device is not streaming data anymore as soon as the ntf_sent_cntr exceeds a certain threshold even if the device was disconnected from the central device. With this approach the device does not have to fully reboot its firmware to be able to send data any more.

无论如何,谢谢
凯瑟琳娜