MPINO STUDIO 2 Phase 9 · Troubleshooting

Find where to start when a build, upload, monitor connection, or I/O result does not work as expected.

1. Start with the Symptom

Identify the stage where work stopped. The first place to check differs before a build, during an upload, and while the board is running.

What you see	Check first	Continue here
You cannot open or save a project.	File menu and save path	Phase 7 · Open and Save Projects
Ladder cells do not edit as expected.	Ladder tab and selected cell	Phase 3 · Ladder Editing
Arduino Code does not edit as expected.	Code tab and selected file	Phase 5 · Arduino Code Editing
The build output shows an error.	Build Output and Problems tab	2. When the Build Fails
The upload does not start or stops.	Build result, status bar port, upload log	3. Upload Problems
The Serial Monitor shows no values.	Connection, baud rate, sending code	4. Monitor Values
Ladder power flow or values are missing or frozen.	Monitoring port, uploaded settings, connection	4. Monitor Values
Ladder status differs from physical I/O.	Selected board and ladder pin map	5. I/O Results
Edits or settings are not reflected.	Required save, apply, build, or upload step	6. Changed Results

2. When the Build Fails

Select Run → Build, then check the Build Output panel for the stage where the error appeared. If the Problems tab shows a file and line or a ladder location, select the item to locate the edit. A problem in the first Arduino Code file can jump to its code location. For an additional code file, use the filename and line number to open that file in Explorer.

Error location	Next action	Details
Arduino Code file and line	Correct the syntax or name at that line, then build again.	Phase 5 · Code Errors
Ladder cell or address	Check the address and data type of the indicated cell.	Phase 2 · Memory Addresses / Phase 3 · Ladder Cells
Box-function command or argument	Check that box function's input format and valid range.	Phase 4 · Box Functions
No location in the Problems tab	Read the error in Build Output and the log immediately above it.	Phase 1 · Build

Build again after making a correction. Check the build result before moving on to the upload.

3. When the Upload Does Not Start or Stops

If the build succeeds but the upload does not proceed, check the port selector at the right of the status bar and the board selected in the project. The port list refreshes when opened. If the list is empty, check whether the PC detects the port and whether the download cable for that product is connected; then reopen the list. For MPINO-8A4R(T)-S, see Phase 1 · Select a Port and Upload.

Use the upload log to decide what to check next.

Result in the log	Check
The selected port cannot be accessed.	Check whether another program is using the port. MPINO Studio 2 temporarily disconnects its own monitor during an upload.
The board does not respond.	Check the selected port, cable connection, and whether the project board matches the connected product.
The port cannot be found.	Check the cable and the port detected by the PC, then reopen the port list.
Another upload error occurs.	Read the first error and the preceding step in the upload log.

Check the product documentation for model-specific cables, terminals, and board specifications.

4. When the Monitor Is Connected but Shows No Values

The Serial Monitor shows data sent by Arduino Code. Ladder monitoring shows power flow through contacts and coils and current memory values. First identify which view has no values.

State	Check first
The Serial Monitor does not connect.	Select the PC port in the status bar and check the monitor's Connect state.
It connects but receives no serial data.	Check that `Serial.print()` runs and that the monitor baud rate matches `Serial.begin()`. If text is garbled, check the receive encoding.
Ladder monitoring cannot start.	Check the Monitoring Port setting and whether you built and uploaded again after changing it.
Ladder monitoring starts but shows no values.	Check that the configured communication channel matches the connected channel.
Previously displayed ladder values stop changing.	Check board operation and the connection, then turn monitoring off and back on.

The two monitors use the same PC serial port selected in the status bar, so they cannot connect simultaneously. See Phase 6 · Serial and Ladder Monitoring for connection steps and port sharing.

5. When Ladder Status Differs from Physical I/O

Check whether the relevant contacts and coils change their power-flow indication during ladder monitoring. If no indication appears, check the monitoring connection first.
Confirm that the board selected in the project matches the connected product.
Open Settings → Ladder Pin Map Settings and check Use, I/O direction, and the physical pin mapping for the P address.
Compare the address shown on screen with the actual terminal in the product documentation.

The P0 input and P32 output example belongs to the Phase 1 project with MPINO-8A4R(T)-S selected. Do not apply those P addresses or terminals to other boards. See Phase 1 · First Project and Phase 7 · Board and Pin Map Settings.

If a C memory value differs from what you expect, check whether the board-function mapping overlaps a counter address. The C0–C10 mapping for MPINO-8A4R(T)-S is in Phase 2 · Memory Areas. Follow the product's specifications for physical wiring and output types.

6. When Settings or Edits Are Not Reflected

What changed	Check before expecting the result	Details
Project code, ladder, or symbols	Save the edited project. Build and upload again if the result must change on the board.	Phase 7 · Save Projects
Shortcuts or ladder design	Shortcuts take effect in Preferences immediately. Select Save to apply ladder-design changes.	Phase 7 · Preferences
Monitoring port or board communication settings	Build and upload again with the changed settings.	Phase 6 · Monitoring Settings / Phase 7 · Communication Settings
Code files or completion	Check the active code file and the file list in Explorer.	Phase 5 · Code Files
Libraries or symbols	Check Refresh in the library list or the validation message in the Symbols dialog.	Phase 8 · Libraries and Symbols

7. When You Still Cannot Find the Cause

Record which step failed, what you did, and the exact message shown, in that order. Include the selected product, board, and port. For example: “The MPINO-8A4R(T)-S project builds, but uploading to COM3 reports that the board is not responding.”

You can enter the description under Help → Report a Bug. Basic diagnostic information is included. Attach the project, a screenshot, or contact information only if you choose to. See Phase 7 · Help Menu for the report dialog.

ILOGICS Product Documentation

Table of Contents