RN4020 MLDP模式只发送一个字符并挂起

TY900900800和30002000。我可以从容不迫地向另一个人发送。以一种方式。



      以下为原文

    try 90000800 and 30002000. I can send constntly from on to another. In one way.

不。。。我试着从中央和外围发送。没有什么。我确实把它们设置为上面，然后：通过USB UART扫描连接中央模块，识别对等体，停止连接（E，0，ID），文本“连接”出来，注意到它进入MLDP模式（没有答案），但是没有什么东西出现在外设的RX上。我用115200个BPS同时用于两个模块和控制台。好吧，我想…



      以下为原文

   
No... I tried both sending from the central and peripheral. Nothing. I did set them up as above, then:
- connected the central module through u***-uart
- scan, identify peer, stop
- connect (e,0, id)
The text 'Connected' came out, noticed it went into MLDP mode (no answer), but nothing sent appeared on the Peripheral's RX.
I'm using 115200 bps for both modules and console, that's alright I assume...

文本“连接”出来了，注意到它进入MLDP MODENO。你应该发送我的命令。MLDP响应必须是。您没有启用MLDP的CONECT。



      以下为原文

    >>The text 'Connected' came out, noticed it went into MLDP mode
 
No. YOu should send I command. And MLDP responce must be. YOu have not enabled MLDP on conect.

嗨，你实现了流量控制（RTS/CTS）吗？RN4020评估板显示流量控制引脚连接。从我过去的经验，你会遇到麻烦而不实施它…



      以下为原文

    Hi,
Did you implement flow control (RTS / CTS) ?
The RN4020 evaluation board shows that flow control pins are connected.
From my past experience, you'll have trouble without implementing it...
Regards
 

不，我没有…我在一台控制台上用UB-UART电缆打字，发送1-2字节/秒。如果我必须使用流量控制（4线加上所有的SW开销），即使在那个字节速率下，我也会真诚地，真诚地，停止使用Microchip来维持我的职业生涯（而且它比我们落后的少），并把这个事实作为一个理由。



      以下为原文

   
No, I haven't... I'm typing on a console with an USB-UART cable and sending 1-2 bytes/sec. if I must use flow control (4 wires plus all the sw overhead) even at that byte rate, I would really, honestly, sincerely, stop using Microchip for the rest of my professional life (and it's less ahead than behind) and keep that fact as a justification.

完成。。。。MLDP的窍门是（似乎是）：启用UART流量控制事件，不使用ITSO，所以我用SR、9200000和外围设备建立中心模块32000800（用于自动MLDP），然后通过USB UART通信到中央模块，扫描、连接，使TX引脚连接到RX上的PII上。模块，和VoILA！我输入的所有字符都回来了。我没有流量控制。



      以下为原文

    Done.... the trick for MLDP is (seems to be):
Enable UART Flow Control event and don't use it

So I set up the central module with SR,9200000 and the peripheral with 32000800 (for auto MLDP)
Then communicating through USB-Uart to the central module, scanned, connected, had the TX pin connected to RX on the peripheral module, and voila! all characters I typed in came back. I had no flow control.
 

你能在两个方向发送数据吗？



      以下为原文

    Can you send data in both directions?

是的，我刚查过。这里是我做的：-模块A（中央）与SR，92000000 - Module B（外围）设置与SR，32000000 -连接USB UART电缆到模块A（仅RX/TX/GND）-扫描和连接模块B -连接CMD引脚模块B到3V（它们是浮动的，所以下拉）如果这可能不是必要的为汽车MLDP与SR，32000800 ] -发送“我”到模块A，返回“MLDP”-连接RX和模块B上的TX -发送控制台上的字符，他们出现回来[丢弃你'本地回声'欺骗你，打破RX - TX连接，然后再试一次-尝试发送一个TXT文件（短）。它回来后，循环无线旅行：-我交换USB电缆到模块B（再次，只有RX，TX，GND）-连接RX和TX上的模块A -在控制台和文本出现回注：我读到某处MLDP流量限制为50 kbps，所以我改变波特夸大到38400与“SB，3”在这两个模块中。这可能与流量控制的需要有关。流量控制是为了防止填充缓冲器。我的假设是发送不比RF链路快，没有缓冲区被填满，并且不需要流量控制。那些有空闲时间，喜欢冒险，没有女朋友/妻子等待和头发在头上拉，被邀请尝试其他速度（56K，112K）。我已经够兴奋了。微芯片不是它们过去的样子…



      以下为原文

   
Yes, I just checked. Here is what I did:
- Module A (central) set up with SR,92000000
- Module B (peripheral) set up with SR,32000000
- Connect USB-Uart cable to module A (only RX/TX/GND)
- Scan and connect to module B
- Connect CMD pin in module B to 3V (they were floating, so pulled down) [this may not be necessary if set up for Auto MLDP with SR, 32000800]
- Send "I" to module A, returns "MLDP"
- Connect RX and TX on module B
- Send characters on the console, they appear back [to discard you have 'local echo' fooling you, break the RX-TX connection and try again]
- Tried sending a txt file (short). It comes back after the round wireless trip :-)
 
- I swapped the USB cable to module B (again, only RX, TX, GND)
- Connected RX and TX on module A
- Typed in the console and text appeared back
 
Note: I read somewhere that MLDP traffic is limited to 50 kbps, so I changed the baud rade to 38400 with "SB,3" in both modules. This could be related to the need of flow control. Flow control is to prevent filling the buffers. My assumption is by sending not faster than the RF link, no buffer is ever filled up and no flow control is needed. Those with free time, love for adventure, no girlfriends/ wives waiting and hairs in the head to pull off, are invited to try other speeds (56k, 112k). I had already enough excitement. Microchip is not what they used to be...

据我了解，您没有使用PICTHEN RN4020评估板吗？你把USB UART电缆直接连接到RN4020模块吗？



      以下为原文

    As I understood you are not using the PICTail RN4020 evaluation board?
You connect USB UART cable directly to RN4020 module?

不，我不是，我使用MikroE的BLU2点击，这是一个简单的突破板，所以它和使用模块引脚一样有效。



      以下为原文

   
No, I'm not, I'm using the BLE2 click from MikroE that is a simple breakout board, so it's effectively the same as using the module pins

好啊。谢谢。我猜我的问题是PiBead BARD上的UB-UART转换器芯片。我会尝试使用自定义板与USB到UART转换器，保证明天工作。



      以下为原文

    OK. Thanks. I guess my problem is the USB-UART converter chip on PICTail baard. I will try to use custom board with USB to UART converter which guarantee to work tomorrow.

我有一个应用程序板与一个MCU连接到BLE。我擦除MCU有高Z的引脚，所以我可以插入我的UART电线给它。你也可以这样做。



      以下为原文

   
I have the application board with an MCU connected to the BLE. I erase the MCU to have the pins in high-z so I can plug my uart wires to it. You can do that as well.

当RN-4020 PICTWER被连接到一个外部微控制器时，你必须非常小心（我在一年前有这个问题…）：PIC18F25K50上的板上必须永久复位，以确保引脚处于HIZ。这是通过在JP1上放置跳线来完成的。



      以下为原文

    Hi

 
When the RN-4020-PICTAIL is used connected to an external microcontroller you must be very careful (I had this issue one year ago...) : the on-board PIC18F25K50 MUST be put in reset permanently to ensure that the pins are in HiZ. This is done by putting a jumper on JP1 
Regards

我已经成功地在两个方向上实现MLDP。我已经启用了流量控制，但没有帮助。我看到您不使用0x00 000（仅服务器特性）。我已经禁用它的外围设备和MLDP开始工作。这个设置如何影响MLDP无法想象。谢谢帮助Joab.RISC我已经完全删除了芯片：从PCB。我以后再把它焊回去。



      以下为原文

    I have managed to implement MLDP in both directions. I have enabled flow control but that did not helped.
I see that you are not using 0x00002000 (Server only feature). I have disabled it on device which is peripheral and MLDP started working. How this setting affects MLDP can't imagine.
Thanks for help joab.
 
RISC i have removed the chip completely :) from the PCB. I will solder it back later.

这是否意味着服务器服务与MLDP不兼容？共享资源？缺陷？哦，烙铁溶液…这就是我的极限：



      以下为原文

   
Does it mean Server services are incompatible with MLDP? Shared resources? Bug?
Oh, the soldering iron solution.... that's my extreme :-)

GT是否意味着服务器服务与MLDP不兼容？共享资源？缺陷？我现在不知道。你能检查一下你的系统吗？仅启用设备外围设备。



      以下为原文

    >>Does it mean Server services are incompatible with MLDP? Shared resources? Bug?
 
I don't know currently. Can you check that on your system? Enable ServerOnly on device peripheral device.