Trying to track down an unexpected behavior with a BG96 design. I have not yet been able to test the behaviors with the BG95-M3 module.
When using the AT+QMTOPEN? command via the USB-AT port, the results are the expected behavior, the response is the like below with the TCP connection ID, hostname, and port displayed.
But, if I issue the identical command via the UART-AT port there is no response. I have not seen any other deviation in AT command behavior based on USB vs. UART ports, like is present on the AT+QMTOPEN?. Note the AT+QMTOPEN write command works the same USB-AT or UART-AT.
This hinders checking validity for an existing connection if the system containing the module is restarted and the embedded application is attempting to reuse existing connections or is attempting to get the host name of the MQTT server after opening it.
Anyone seen this? Anyone have a workaround?