Skip to content
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

GPIO 14 modem hardware control needed? (AEGHB-383) #294

Closed
sirtet opened this issue Sep 9, 2023 · 3 comments
Closed

GPIO 14 modem hardware control needed? (AEGHB-383) #294

sirtet opened this issue Sep 9, 2023 · 3 comments

Comments

@sirtet
Copy link

sirtet commented Sep 9, 2023

Is GPIO 14 mandatory in all cases?
In the Photo in the readme, only USB seems to be connected...
I am considering using a 4g USB dongle. That would not be possible then, right?

@github-actions github-actions bot changed the title GPIO 14 modem hardware control needed? GPIO 14 modem hardware control needed? (AEGHB-383) Sep 9, 2023
@leeebo
Copy link
Collaborator

leeebo commented Sep 11, 2023

@sirtet Sorry, I didn't get your point. Do you mean the Modem Reset Control in usb_cdc_4g_module#hardware-requirement? in this case it's better to let esp32 control modem reset to handle some error case.

@sirtet
Copy link
Author

sirtet commented Sep 11, 2023

Yes, that was my point. So, this line is not mandatory, but optimal? If so, the readme should maybe be corrected.
Am I correct that the demo photo&video do not use the reset line?
And as a follow up question: I guess the reset could also be done by Interrupting the USB 5v, if no direct access to the modem's reset line is available?

@leeebo
Copy link
Collaborator

leeebo commented Sep 11, 2023

@sirtet Yes, the demo photo does not use the reset line, but it is recommended in the product.

If the VBUS can be controlled by your ESP32, power-off then power-on has the same effect as reset, In this case reset line is optional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants