-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add SH-M08 Module #2
Comments
Running a terminal directly on the module and trying various commands I have come up with the following:
Also I found this: http://www.dsdtech-global.com/2017/09/sh-m08.html I'm working out adding it to the sketch now. I'll fork it and do a pull request once it is working. |
@NicholasTracy thanks for the info. What end line mode did you use to send commands to it? I checked if I can order one but it didn't seem that popular. Can you suggest a place that sells these and ships worldwide? Looking forward to a pull request or to more information. |
Correct it handles AT commands differently from either the HM-10 or the clones. In some commands it uses the ? at the end to return the current value and in others it does not. and it has no help command. the firmware version returned is also unique. They are sold by DSD-TECH which also happens to be a legitimate re-seller of the genuine HM-10 modules as well. I purchased mine off of Amazon US but they also sell on their own website, I think. I might be wrong on that one. I was using \r\n\ end line mode in my terminal as it would not respond otherwise. |
I received another module based off the HM-10 that supposedly is the same but only in a smaller form factor for the carrier board. it has the same pin outs on the break out board as the HM-10. However when trying to use the Ident-n-set sketch on this module I get:
Detecting module type Unexpected result of length=4 OK
Not sure what is different there. I will be doing some research on the AT commands structure for this module as the typical AT+VERS? command returned nothing in all its variations.
The text was updated successfully, but these errors were encountered: