User Manual
Table Of Contents
- Contents
- Getting Acquainted — Read This First!
- Chapter 1 Basic Operation
- Chapter 2 Manual Calculations
- 1. Basic Calculations
- 2. Special Functions
- 3. Specifying the Angle Unit and Display Format
- 4. Function Calculations
- 5. Numerical Calculations
- 6. Complex Number Calculations
- 7. Binary, Octal, Decimal, and Hexadecimal Calculations with Integers
- 8. Matrix Calculations
- 9. Vector Calculations
- 10. Metric Conversion Calculations
- Chapter 3 List Function
- Chapter 4 Equation Calculations
- Chapter 5 Graphing
- 1. Sample Graphs
- 2. Controlling What Appears on a Graph Screen
- 3. Drawing a Graph
- 4. Storing a Graph in Picture Memory
- 5. Drawing Two Graphs on the Same Screen
- 6. Manual Graphing
- 7. Using Tables
- 8. Dynamic Graphing
- 9. Graphing a Recursion Formula
- 10. Graphing a Conic Section
- 11. Changing the Appearance of a Graph
- 12. Function Analysis
- Chapter 6 Statistical Graphs and Calculations
- 1. Before Performing Statistical Calculations
- 2. Calculating and Graphing Single-Variable Statistical Data
- 3. Calculating and Graphing Paired-Variable Statistical Data
- 4. Performing Statistical Calculations
- 5. Tests
- 6. Confidence Interval
- 7. Distribution
- 8. Input and Output Terms of Tests, Confidence Interval, and Distribution
- 9. Statistic Formula
- Chapter 7 Financial Calculation (TVM)
- Chapter 8 Programming
- Chapter 9 Spreadsheet
- Chapter 10 eActivity
- Chapter 11 Memory Manager
- Chapter 12 System Manager
- Chapter 13 Data Communication
- Chapter 14 PYTHON (fx-9860GIII, fx-9750GIII only)
- Chapter 15 Distribution (fx-9860GIII, fx-9750GIII only)
- Appendix
- Examination Modes (fx-9860GIII, fx-9750GIII only)
- E-CON3 Application (English) (fx-9860GIII, fx-9750GIII)
- 1 E-CON3 Overview
- 2 Using the Setup Wizard
- 3 Using Advanced Setup
- 4 Using a Custom Probe
- 5 Using the MULTIMETER Mode
- 6 Using Setup Memory
- 7 Using Program Converter
- 8 Starting a Sampling Operation
- 9 Using Sample Data Memory
- 10 Using the Graph Analysis Tools to Graph Data
- 11 Graph Analysis Tool Graph Screen Operations
- 12 Calling E-CON3 Functions from an eActivity
11-7
u Error Checks During Data Copy
The following error checks are performed while a data copy operation is being executed.
Low battery check
The calculator performs low battery check before starting the data copy operation. If the
battery is at Level 1, a low battery error occurs and the copy operation is not performed.
Available memory check
The calculator checks to see if there is enough free memory available to store the copied data.
A “Memory Full” error occurs if there is not enough memory available.
A “Too Much Data” error occurs when the number of data items is too great.
A “Fragmentation ERROR” occurs when there is enough free memory available, but a garbage
collection operation is required.
If a “Fragmentation ERROR” occurs, perform the optimization procedure (
page 11-11).
Overwrite check
The calculator checks to see if there is any existing data at the copy destination with the same
name as the data being copied.
An overwrite confirmation message appears if there is data
with the same name.
• 1(Yes) ... overwrites the existing data with the new data
• 6(No) ... advances to the next data item without copying the data with the same name
• Pressing A will cancel the copy operation and return to the MEMORY mode initial screen.
Overwrite check is performed for the following types of data only. All other types of data are
copied, without checking for data files with the same name.
• Programs
• Matrices/Vectors
• List files
• Graph memories
• Dynamic Graph memories
• Spreadsheet data
Overwrite check is performed for data of the same type only. If different types of data have the
same name, the copy operation is performed without regard to the data with the same name.
Overwrite check applies only to the destination of the copy operation.
Type mismatch error check
eActivity data, add-in applications, add-in languages, add-in menus, and backup data cannot
be copied to main memory. Attempting to do so will cause a type mismatch error.