Function pin soft triggered
Wireless
No replies yet. Be the first to reply.
Join the discussion.
Wireless
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: Function pin soft triggered
by wizdaniel ·
I understood that you’d like to execute the AP mode with MAC address using AT commands
Right?
there is no software trigger to set configuration with just one command.
but you can see the MAC address using AT+MMAC=?
then you should make SSID using MAC address
the FUNC pin is defined 2 functions.
if it triggered once, the module will start AP mode as you know. and run TCP Server using 5000 port.
if it triggered 3 times, the module will set initial(factory default) configurations.
RE: RE: Function pin soft triggered
by Luis Villegas ·
Yes i wanted to run the func pin AP mode with one command, the default ssid should contain the MAC address, because as it’s now, every module has the same default SSID, that it’s not useful, that’s why i wanted to run or trigger the AP mode of the func pin in one go.
So many design issues with this module
RE: Function pin soft triggered
by wizdaniel ·
yes, I agree your opinion.
and now the WizFi310 doesn’t provide that function.
why don’t you try to set the AP mode with several commands like +MMAC to get the MAC address.
RE: Function pin soft triggered
by Luis Villegas ·
Yes, is actually what i did, even though, that way cost me memory and processing time, that in bare metal embedded systems mean wasted of resources.
That also means to detour the current developed work flow of the wifi layer, to make this is required to develop an “internal” state machine for this module, so it can handle multiple instructions in the “background”, to simulate one (actually slower) instruction for the general wifi layer state machine.
Anyways, it is as it is, thanks for your support