-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quectel BC95-G AT-command doesn't require quotation marks #14918
Comments
@alcheagle thank you for raising this issue.Please take a look at the following comments: What target(s) are you using? NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered. |
Looks like you're right. We can't break the command for other modules though. How about we fix it driver level? I don't know what other modules are supported. People might be using the at handler for their devices so we can only fix the devices at the driver level that we already support. @jarvte do you know anything about this discrepancy between our code and the spec? Is there variability in devices, should this be a configuration option? |
#14922 was merged, shall this be closed (besides some questions above, discussion can still be ongoing) ? |
I I think the issue can be closed since It had been resolved by the PR you are mentioning |
Description of defect
The cellular module BC-95-G is returning code
50
, meaning 'incorrect parameters '. By inspecting the AT debug mode I noticed the commands had quotation marks surrounding the hex string, from Quectel AT datasheet I saw they are not requiring them.If I comment the following lines the device started working.
mbed-os/connectivity/cellular/source/framework/device/ATHandler.cpp
Line 1561 in cecc47b
mbed-os/connectivity/cellular/source/framework/device/ATHandler.cpp
Line 1568 in cecc47b
Logs of the non working version:
Logs of the working version with the quoted lines commented:
I am using a slightly modified version of https://github.com/ARMmbed/mbed-os-example-cellular in order to include more debug info.
Target(s) affected by this defect ?
Nucleo_l476rg
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
https://github.com/ARMmbed/mbed-os/#cecc47b4a53951527dd3f670465c8566396ad101
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
How is this defect reproduced ?
The text was updated successfully, but these errors were encountered: