Before anything else, confirm that the control is a Fanuc 0i-TF and that the problem occurs while editing a CNC program. On the documented keyboard layout, the physical keys expose square brackets but not parentheses. The required characters are available through the control's softkey menus in program EDIT mode.
Character-entry approaches
Two approaches apply to this symptom: a shifted physical-key combination or the character-entry softkey menu. The installed keyboard layout decides whether the first approach works. Square brackets are not substitutes for parentheses; the program parser and the connected DNC system treat them as different characters.
| Approach | When it applies | Confirmation | Decision for this case |
|---|---|---|---|
| Shifted physical keys | The keyboard firmware and key legends support alternate characters | The editor displays ( or ) at the cursor |
Shift+O for ( and Shift+N for ) were proposed, but did not work on the installed 0i-TF layout |
| Softkey character entry | The physical keyboard omits parentheses | The softkey pages expose T.EING, followed by the special characters |
Confirmed method for the installed control |
Use the shifted keys only as a quick layout test. Do not move on until the character visible in the editor is the requested parenthesis rather than a letter, bracket, or other alternate symbol.
Recommended entry method
Use the T.EING softkey path. It avoids dependence on a keyboard mapping that may differ between control panels, even when the CNC family is similar. The method also gives direct visual confirmation before the program is stored or transferred.
The decisive test is the displayed character, not an assumed key assignment. If Shift+O or Shift+N enters another character or performs no useful action, stop testing undocumented combinations and use the softkey menu. A key sequence associated with another panel layout does not establish the mapping on this one.
Editing prerequisites
- Select the target CNC program. Display the program and place the cursor at the exact insertion point. Confirm that the intended block is visible before continuing.
-
Select program
EDITmode. The special-character path was found from this mode. Confirm that the editor accepts ordinary character entry and that the cursor can be positioned. -
Identify the required delimiter. Use
(to open the text and)to close it. Confirm that the receiving DNC workflow requires these exact characters. - Preserve the current program. Follow the site's normal program-control practice before changing production code. Confirm that the correct revision and program are open.
If T.EING is not visible on the first softkey page, that is not proof that the function is absent. The entry is hidden behind additional program-edit menu pages on the documented panel.
Parenthesis entry procedure
-
Open the program editor. Put the control in program
EDITmode and position the cursor where the opening parenthesis belongs. Confirm the cursor location against the surrounding block. -
Page through the lower softkey menu. Advance through the available menu pages until
T.EINGappears. Do not move on until that exact label is visible. -
Open
T.EING. Select the softkey to display the special-character choices. Confirm that the menu includes round parentheses. -
Insert the opening character. Select
(and confirm that the editor places it at the cursor. Check the glyph carefully against[. - Enter the required text. Type the comment or DNC-required content. Confirm that the text remains inside the intended program block.
-
Insert the closing character. Return to the special-character selection if necessary, select
), and confirm that the pair is balanced. -
Review the complete block. Check that the result has the form
(text), not[text], and that no unintended letter from a failed shifted-key test remains.
Keyboard-layout mechanism
The visible key legends describe only the characters directly assigned to the installed panel. They do not list every character accepted by the program editor. The control therefore exposes additional symbols through contextual softkeys.
Physical keyboard mappings are panel-dependent. A shifted combination that produces parentheses on one layout may produce a letter or no parenthesis on another. This explains why copying a key sequence from a different control keyboard can fail while the editor still supports the required characters.
The distinction also matters at the program level. The characters (, ), [, and ] have different character codes. Replacing parentheses with square brackets changes the transmitted data and may change how a CNC parser or external DNC application interprets the block. The correct troubleshooting target is therefore character generation, not visual resemblance.
DNC transfer preparation
The connected DNC system in this installation requires round parentheses for data transfer. Treat local editing and transport as two separate checkpoints: first prove that the CNC editor contains the correct characters, then prove that the transferred file preserves them.
-
Create a controlled test block. Insert a short, recognizable parenthesized string through
T.EING. Confirm both delimiters on the CNC display. -
Store the edited program. Use the site's normal save operation. Reopen or redisplay the block and confirm that
(and)remain present. - Run the normal DNC transfer. Use the established connection and transfer settings; changing communications parameters is unnecessary unless the transfer itself fails.
- Inspect the received representation. Confirm that the receiving system shows the same opening and closing parentheses. If it shows square brackets, missing delimiters, or replacement characters, troubleshoot the transfer path rather than the CNC entry method.
A successful local entry proves only that the editor can generate the characters. End-to-end acceptance requires the stored program, transmitted data, and receiving application to retain the same character pair.
Symptoms and corrective actions
| Symptom | Likely cause | Action | Pass condition |
|---|---|---|---|
Only [ and ] appear on the keyboard |
Parentheses are not assigned to visible physical keys | Enter program EDIT mode and page to T.EING
|
The special-character menu displays ( and )
|
Shift+O or Shift+N does not enter parentheses |
The installed keyboard uses a different mapping | Stop using the shifted-key method and select the symbols through T.EING
|
The requested parenthesis appears at the cursor |
T.EING is not on the first softkey row |
The editor has additional softkey pages | Continue paging through the program-edit menu | The exact T.EING entry becomes visible |
| Parentheses appear locally but DNC rejects the data | The stored or transferred representation differs from the edited block, or the DNC requirement involves more than delimiter entry | Reopen the stored program, then compare the received text character by character | Both endpoints show the identical balanced pair |
| The block contains mixed brackets and parentheses | A previous test or manual substitution left incorrect characters | Delete the wrong delimiters and reinsert both through the confirmed method | The block contains only the required delimiter type |
Program and transfer verification
-
Verify the opening delimiter. Inspect the edited block at the cursor and distinguish
(from[. - Verify the closing delimiter. Confirm that every opening parenthesis used for the required text has a closing parenthesis.
- Verify storage. Redisplay the saved block and confirm that neither character changed or disappeared.
- Verify transfer fidelity. Compare the CNC program with the DNC-side copy. The characters and their order must match.
- Verify operational acceptance. Submit the controlled test through the normal DNC workflow. Do not proceed with the production program until the receiving system accepts the parenthesized data without substitution or rejection.
Frequently asked questions
How do I type parentheses on a Fanuc 0i-TF?
Open the program in EDIT mode, page through the lower softkey menus until T.EING appears, and select ( or ) from the special characters.
How do I use Shift+O and Shift+N for parentheses?
Test Shift+O for ( and Shift+N for ) only if the installed keyboard mapping supports them. On the documented Fanuc 0i-TF layout they did not work, so use T.EING.
How do I verify Fanuc parentheses before DNC transfer?
Confirm (text) in the editor, redisplay the stored block, transfer the test, and compare the received copy character by character. The final pass condition is DNC acceptance with both parentheses preserved.