Network

1. Simple Wi-Fi Connection

[ INSERT BLOCK IMAGE HERE: Connect Wi-Fi ]

The first Wi-Fi block provides a simplified connection operation.

The supplied example generates:

Python

mixiot.wlan_connect(

'wifiname',

'wifipassword'

)

The block supplies:

Wi-Fi Name

Plain Text

wifiname

Password

Plain Text

wifipassword

Conceptually:

NETWORK NAME + PASSWORD → CONNECT

This is the simplest Wi-Fi connection concept for beginners.

2. Configuring the Wi-Fi Mode

[ INSERT BLOCK IMAGE HERE: Configure Wi-Fi Mode ]

The actual generation confirms two interface modes.

STA

Python

wlan = network.WLAN(network.STA_IF)

AP

Python

wlan = network.WLAN(network.AP_IF)

So the selector can now accurately be documented as:

For beginning students, the important conceptual distinction is:

STA

Used by the block to create the station interface.

AP

Used by the block to create the access-point interface.

The beginner sequence should start with STA when the objective is connecting to an existing Wi-Fi network.

3. Activating and Deactivating the Interface

[ INSERT BLOCK IMAGE HERE: Activate Network Interface ]

The original image showed Activate, but the real generator confirms both states.

Activate

Python

wlan.active(True)

Deactivate

Python

wlan.active(False)

Therefore:

Conceptually:

CONFIGURE INTERFACE → ACTIVATE → USE

4. Checking the Interface Active State

[ INSERT BLOCK IMAGE HERE: Get Active Status ]

The corresponding block generates:

Python

wlan.active()

This obtains the current active-state value of the interface.

That gives us an important distinction:

Set State

Python

wlan.active(True)

Get State

Python

wlan.active()

For students:

SET → Change something

GET → Read something

5. Scanning for Wi-Fi Networks

[ INSERT BLOCK IMAGE HERE: Scan Wi-Fi ]

The block generates:

Python

wlan.scan()

Conceptually:

D1 R32 → SCAN → Available Wi-Fi Information

For learning and troubleshooting, the scan result can be sent to the PC using Serial.

Wi-Fi Scan → Serial Port → PC

This makes an otherwise invisible network operation observable.

6. Connecting the Configured wlan

[ INSERT BLOCK IMAGE HERE: wlan Connect Wi-Fi ]

The supplied example generates:

Python

wlan.connect(

'127.16.0.8',

'01234567'

)

The two block fields supply:

• Network name
• Password

Conceptually:

Configured wlan + Credentials → Connect

This is different from the earlier simplified mixiot.wlan_connect() block because this operation explicitly uses the previously configured:

Python

wlan

interface.

7. Checking Whether Wi-Fi Is Connected

[ INSERT BLOCK IMAGE HERE: Wi-Fi Connect State ]

The actual operation is:

Python

wlan.isconnected()

Conceptually:

Wi-Fi → Connected? → Result

This can naturally feed into Logic and Control:

Wi-Fi Connected?

↓

TRUE / FALSE

↓

IF

↓

Next Action

🧠 A good network program should distinguish between requesting a connection and checking the resulting connection state.

8. Getting Wi-Fi Network Information

[ INSERT BLOCK IMAGE HERE: Get Wi-Fi Information ]

This block is considerably more capable than the original screenshot revealed.

The real generator confirms four indexes:

Python

wlan.ifconfig()[0]

wlan.ifconfig()[1]

wlan.ifconfig()[2]

wlan.ifconfig()[3]

The previously visible selection was:

IP address

which corresponds to the real generated:

Python

wlan.ifconfig()[0]

For the remaining selector labels, we should use the actual names displayed in Clu-Blocks Pro's menu when they are available rather than inventing labels solely from the array indexes.

Technically, however, we can safely document that the block provides selectors generating:

ifconfig()[0] through ifconfig()[3].

9. Disconnecting Wi-Fi

[ INSERT BLOCK IMAGE HERE: Disconnect Wi-Fi ]

The block generates:

Python

wlan.disconnect()

This ends the Wi-Fi connection associated with the configured interface.

The complete beginner Wi-Fi cycle therefore becomes:

CONFIGURE → ACTIVATE → CONNECT → CHECK → USE → DISCONNECT

10. Access Point Information

[ INSERT BLOCK IMAGE HERE: Get Access Point Information ]

The actual generation confirms two AP configuration queries.

ESSID

Python

wlan.config('essid')

Channel

Python

wlan.config('channel')

Therefore, the selector provides at least these two confirmed operations:

ESSID

and:

Channel

The visible block wording can continue using the interface's own label, while the technical explanation documents the exact generated property.

11. Setting Access Point Information

[ INSERT BLOCK IMAGE HERE: Set Access Point ]

The supplied example generates:

Python

wlan.config(

essid = '127.16.0.8',

channel = 1

)

The block therefore configures:

ESSID

Plain Text

127.16.0.8

Channel

Plain Text

1

Conceptually:

AP NAME / ESSID + CHANNEL → CONFIGURE ACCESS POINT

This block belongs with AP mode, not with the initial beginner STA connection workflow.

12. Start Server

[ INSERT BLOCK IMAGE HERE: Start Server ]

The real Clu-Blocks Pro generation for this server operation is more substantial than the visible block suggests:

Python

if not wlan.isconnected():

connectWifi(SSID, PASSWORD)

ip = wlan.ifconfig()[0]

print(ip)

time.sleep(1)

DATA = listenData()

This confirms that the generated server sequence:

1. Checks the Wi-Fi connection.
2. Calls connectWifi(SSID, PASSWORD) when the generated condition requires it.
3. Obtains ifconfig()[0].
4. Prints the value.
5. Waits 1 second.
6. Calls listenData().

For the student-facing manual, I would simplify this to:

Starts the server workflow generated by Clu-Blocks Pro and obtains incoming data through the corresponding server library operations.

The generated details can remain in the technical reference.

🔌 Socket Communication

The second major half of Network introduces sockets.

The real code confirms two socket types:

TCP

and:

UDP

These are significantly more advanced than simply connecting to Wi-Fi.

Teaching recommendation: students should understand Wi-Fi connection, connection state, and IP information before beginning socket communication.

13. Creating a TCP Socket

[ INSERT BLOCK IMAGE HERE: Socket Init ]

When TCP is selected, Clu-Blocks Pro generates:

Python

s = socket.socket(

socket.AF_INET,

socket.SOCK_STREAM

)

The created socket is:

Plain Text

s

The important student concept is:

TCP → SOCK_STREAM

14. Creating a UDP Socket

When UDP is selected, the same block generates:

Python

s = socket.socket(

socket.AF_INET,

socket.SOCK_DGRAM

)

Therefore:

This is a major improvement over the original version, where only TCP was visibly selected.

15. Binding a Socket

[ INSERT BLOCK IMAGE HERE: Bind Socket ]

The supplied example generates:

Python

s.bind(('0.0.0.0', 80))

The block contains:

Address

Plain Text

0.0.0.0

Port

Plain Text

80

Conceptually:

SOCKET + ADDRESS + PORT → BIND

For beginner documentation, that relationship is enough. The deeper networking meaning of individual special addresses can be introduced in later networking lessons.

16. Connecting a Socket

[ INSERT BLOCK IMAGE HERE: Connect Socket ]

The visible example uses:

Plain Text

clu-block.org

and:

Plain Text

80

Clu-Blocks Pro generates:

Python

s.connect(

socket.getaddrinfo(

'clu-block.org',

80

)[0][-1]

)

This reveals an important detail:

The destination field can be supplied to:

Python

socket.getaddrinfo(...)

before the connection is made.

At the block level, students can think:

Socket + Domain/IP + Port → Connect

17. Listen

[ INSERT BLOCK IMAGE HERE: Socket Listen ]

The visible queue value is:

Plain Text

5

and the generated operation is:

Python

s.listen(5)

The numerical field is supplied directly to listen().

For beginner documentation, the key concept is:

Socket → Listen

Detailed queue semantics can be introduced later rather than overloading the first socket lesson.

18. Accept

[ INSERT BLOCK IMAGE HERE: Accept Socket ]

The block generates:

Python

s.accept()

This is the socket accept operation exposed by Clu-Blocks Pro.

For the student-facing explanation:

LISTEN → ACCEPT CONNECTION

This belongs to the more advanced server-side socket workflow.

19. TCP Receive

[ INSERT BLOCK IMAGE HERE: TCP Receive ]

The example generates:

Python

s.recv(1024)

The supplied value is:

Plain Text

1024

Conceptually:

TCP Socket → RECEIVE → Data

The 1024 value is supplied as the argument to recv().

20. TCP Send

[ INSERT BLOCK IMAGE HERE: TCP Send ]

This block contains one of the most important hidden selectors in the Network category.

The actual code confirms four data-conversion forms.

Integer

Python

s.send(int('Clu-Bots'))

Float

Python

s.send(float('Clu-Bots'))

UTF-8

Python

s.send('Clu-Bots'.encode("utf-8"))

Integer from Bytes

Python

s.send(

int.from_bytes(

'Clu-Bots',

"big"

)

)

Therefore, the Send block does not simply contain one toInt option. The selector controls how the supplied content is converted before being passed to send().

21. TCP Send Conversion Options

For the final manual, I recommend using the exact labels displayed by the Clu-Blocks Pro selector once those labels are available.

The MicroPython reference confirms the four actual generated conversion behaviors.

22. UDP Receive

[ INSERT BLOCK IMAGE HERE: UDP Receive ]

UDP uses a different receive operation:

Python

s.recvfrom(1024)

This should remain distinct from TCP:

TCP

Python

s.recv(1024)

UDP

Python

s.recvfrom(1024)

Students should recognize that TCP and UDP have their own corresponding receive blocks.

23. UDP Send

[ INSERT BLOCK IMAGE HERE: UDP Send ]

The UDP send operation includes:

• Content
• Conversion
• Destination
• Port

The supplied reference confirms forms such as:

Python

s.sendto(

'Clu-Bots'.encode("utf-8"),

('127.0.0.1', 80)

)

The example destination is:

Plain Text

127.0.0.1

and the example port is:

Plain Text

80

Conceptually:

DATA + DESTINATION + PORT → UDP SEND

24. UDP Conversion Options

The UDP Send block confirms the same four conversion patterns.

Integer

Python

s.sendto(

int('Clu-Bots'),

('127.0.0.1', 80)

)

Float

Python

s.sendto(

float('Clu-Bots'),

('127.0.0.1', 80)

)

UTF-8

Python

s.sendto(

'Clu-Bots'.encode("utf-8"),

('127.0.0.1', 80)

)

Integer from Bytes

Python

s.sendto(

int.from_bytes('Clu-Bots',"big"),

('127.0.0.1', 80)

)

So:

TCP Send

and:

UDP Send

share the same confirmed conversion family in the supplied Clu-Blocks Pro generation.

25. TCP vs. UDP in Clu-Blocks Pro

For the block manual, the differences can initially be kept simple.

Students do not need a full networking-theory lesson at this point.

The first goal is recognizing that:

TCP and UDP are two different socket communication paths represented by different Clu-Blocks Pro operations.

26. Closing the Socket

[ INSERT BLOCK IMAGE HERE: Close Socket ]

The final socket-management operation generates:

Python

s.close()

Conceptually:

CREATE → USE → CLOSE

This gives students a clear lifecycle for a socket.

27. Network Time

[ INSERT BLOCK IMAGE HERE: Network Time ]

The supplied example uses:

Plain Text

time1.google.com

and generates:

Python

ntptime.time(

host='time1.google.com'

)

This uses the supplied host in the NTP time operation exposed by Clu-Blocks Pro.

Conceptually:

NETWORK → NTP HOST → TIME VALUE

For students, the important first concept is:

Once the D1 R32 has network connectivity, the program can use network-based services such as the NTP operation provided by this block.

Wi-Fi vs. Network Services

This category becomes easier if students understand the layers.

Layer 1: Wi-Fi

Get connected

Layer 2: Network Information

Check state / inspect configuration

Layer 3: Communication

TCP / UDP

Layer 4: Network Services

Server / NTP

So the progression is:

CONNECT → VERIFY → COMMUNICATE → USE SERVICES

Network + HTTP

The next category, HTTP, naturally builds on Network.

Conceptually:

D1 R32

↓

Wi-Fi

↓

Network Connection

↓

HTTP Request

↓

Web Resource

↓

Response

This makes the curriculum progression very logical:

NETWORK first → HTTP afterward

Students should understand that HTTP is not the Wi-Fi connection itself. HTTP operates using network connectivity.

Using Serial Port While Learning Network

For your course, Serial should remain central.

First

Report the connection state:

Wi-Fi → isconnected() → Serial Port → PC

Then

Report network configuration:

Wi-Fi → IP Address → Serial Port → PC

Later

Observe communication:

TCP/UDP Receive → Serial Port → PC

This preserves the course's learning pattern:

CONNECT → OBSERVE → VERIFY → COMMUNICATE

Quick Guide for Students

• Do I simply need to connect to Wi-Fi? Use: Connect Wi-Fi
• Do I need a configured Wi-Fi interface? Use: Configure Wi-Fi
• Which modes are confirmed? STA / AP
• Do I need to enable or disable the interface? Use: Activate / Deactivate
• Do I want to find Wi-Fi networks? Use: Scan
• Do I need to know whether Wi-Fi connected? Use: Wi-Fi Connect State
• Do I need network configuration information? Use: Get Wi-Fi Information
• Do I want to disconnect? Use: Disconnect Wi-Fi
• Do I need an Access Point configuration? Use: AP mode + ESSID / Channel blocks
• Do I need TCP? Use: TCP Socket → Send / Receive
• Do I need UDP? Use: UDP Socket → Send / Receive
• Do I need network time? Use: NTP

Quick Reference