RN4871恢复出厂设置后的行为没有像预期的那样运行

我在我的项目中使用RN1471BLE模块。我注意到，在进行工厂复位之后，模块不会像预期的那样运行。下面是重新创建问题的步骤：&确认：BLE模块在当前状态下工作良好（放置在命令模式下的设备）$$“然后发送各种命令SR、SS、GN等，并得到预期的答复，它表现为鳍。e）。在当前状态下，我已经设置了流控制＝[& lt；字体]，波特率＝230400，SS＝C0（这些相同的UART参数设置在我的MCU上）。现在工厂用“SF，1”重置设备，我假设（按用户指南）波特率和流量控制相关设置从模块中清除。重置UART参数在MCU上，使用缺省波特率和无流量控制（BR＝115200，流量控制＝无）进入命令模式，-gt；这是可行的。&再次设置流控制（使用SR，C020命令）-gt；这个命令回答“AOK”& GT；现在使用“SS，C0”命令设置服务。-即使我们等待了很长时间（如果我连续发送这个命令两次，那么它会回复“AOK”）。&发送“R，1”命令来重新启动模块-GT；这不会回答任何问题，尝试R，1次多次，然后我得到答复-gt；“ReBOtiN”。gn“重启n”“重启n”“%ReBOOT %”（意思是我得到以前的“R，1”一起尝试，然后最后设备重新启动）的答复有人注意到这个行为（模块在工厂复位后SR命令后没有回复）？请让我知道它可能是什么，什么是可以修复它。我在我的模块中观察到固件版本1.18和最新的1.23.3（更新固件没有任何区别）。谢谢！



      以下为原文

    I am using RN4871 BLE module in my project. I notice the module would not behave as expected after doing factory reset.

Here are the steps to recreate the problem:
> Confirm that BLE module works fine in current state (put device in command mode "$$$" then sending various commands SR, SS, GN etc. and getting expected replies, it behaves fine). In current state I have set Flow control = ON [ > Now Factory Reset the device using “SF,1”, I assume (as per user’s guide) baud rate and Flow control related settings are cleared from the module.
> Reset the UART parameters on MCU, Enter command mode using default baud rate and no flow control (BR = 115200, flow control = none), -> this works ok.
> Set flow control On again (using SR,C020 command) -> this command replies “AOK”
> Now set services using “SS,C0” command. -> This does not reply anything, even if we wait for long (If I send this command couple of times in row then it would come back with reply "AOK").
> Send "R,1" command to reboot the module - > This would not reply anything, attempt R,1 couple more times then I get the reply -> “rebootingn” “rebootingn” “rebootingn” “%REBOOT%” (meaning I get replies for previous attempts of "R,1" together and then finally device reboots)

Have anybody noticed this behavior (module does not reply after SR command after Factory reset)?
Please let me know what it could be and what could be the fix for it.

I am observing this in my modules having firmware version 1.18 and in latest one 1.28.3 (updating firmware did not make any difference).

Thanks!

0