The Motor Log is one of the most crucial sections inside PiCAD-Motor, acting as a digital workspace where all your motor projects are stored, tracked, and managed. Whether you are a researcher experimenting with sample motors, an engineer designing custom solutions, or a student exploring how motor parameters affect performance, this section provides both flexibility and control.

From here, you can create, organize, and manage your motors, ensuring you always have a clear view of your design evolution. More importantly, the Motor Log is the gateway to the Motor Wiz module—the core engine where deep simulations and optimizations take place. Without a properly set-up motor in your Motor Log, you cannot fully harness the analytical power of PiCAD-Motor.

 Categories in Motor Log   

When you open the Motor Log, you will notice it is neatly divided into two tabs:

• Sample Motors

• User-Defined Motors

This dual categorization ensures users can either start quickly with pre-loaded reference designs or build their own motors from scratch.

 a) Sample Motors   

Sample Motors are ready-made templates provided by PiCAD-Motor. These are pre-configured with standard specifications and are useful for:

• Learning: Beginners can explore how motors are structured and how their parameters affect outputs.

• Reference: Engineers can benchmark their custom designs against well-tested industry-standard configurations.

• Quick Testing: Instead of starting from zero, you can pick a sample motor, tweak parameters, and run simulations immediately.

Examples of sample motors include:

• Small EV motor for two-wheelers

• Medium-sized induction motor for three-wheelers

• High-voltage permanent magnet motor for cars

Each sample motor is equipped with baseline parameters, making it an excellent entry point before diving into complex user-specific designs.

 b) User-Defined Motors   

The User-Defined Motors tab is where your creativity and engineering insights take center stage. Here, you can:

• Create brand-new motors with customized parameters.

• Store multiple versions of the same motor for iterative improvements.

• Maintain a personal library of designs for long-term projects.

Unlike sample motors, these are unique to your account and reflect your experimentation, R&D, or project-specific requirements.

 Create New Motor – The Starting Point   

At the top of the Motor Log, you’ll find the “Create New Motor” button. This is the first step towards bringing your design ideas into PiCAD-Motor.

When clicked, you are prompted to:

1. Enter a Motor Name

• The system encourages naming conventions for clarity and organization.

• Suggestions include:

• Project-based naming: EV_Scooter_72V_2025

• Functional naming: HighTorque_BusMotor_v2

• Iteration naming: CarMotor_Design1, CarMotor_Design2

• A good naming convention helps when you have dozens of designs and need to track versions or compare outcomes quickly.

2. Define Key Specifications

• Voltage range

• Power rating

• Expected application (EV, Non-EV, industrial, etc.)

• Performance focus (efficiency, torque, speed, or cost balance)

Once you confirm, your motor is instantly added to the User-Defined Motors tab.

 Motor Log – Tabular View   

All motors—sample or user-defined—are displayed in a tabular format that is designed to be clean, searchable, and action-oriented.

The table includes the following key columns:

• Motor Name – As entered by you or chosen from the sample library.

• Category – Indicates whether it is Sample or User-Defined.

• Created On (Date & Time) – Helps track project timelines, especially in collaborative or academic environments.

• Action Buttons – Tools that allow you to manage and evolve your motor designs.

 Action Buttons – Managing Your Motors   

Every row in the Motor Log table has an Action column that includes four powerful options:

1. Edit

• Modify existing parameters of a motor.

• Useful when correcting mistakes or updating designs with new insights.

• Example: Changing battery voltage from 72V to 96V to evaluate performance improvements.

2. Version

• Create a new version of an existing motor without overwriting the original.

• Perfect for iterative design—you can try multiple variations and compare outputs.

• Example: CarMotor_v1 (initial design) → CarMotor_v2 (with improved winding structure).

3. Share

• Collaborate by sharing your motor with team members, colleagues, or clients.

• Shared motors can accelerate teamwork by allowing multiple engineers to simulate or validate the same design.

• Example: A professor sharing sample designs with students for lab assignments.

4. Delete

• Remove unused or outdated designs from your workspace.

• Helps keep the Motor Log clean and focused.

• Example: Clearing trial runs that are no longer relevant.

 Why Motor Log is the Key Section   

While the Motor Log seems like a storage area at first glance, it is much more:

• Organizational Hub – Keeps all your designs structured and accessible.

• Version Control Tool – Allows smooth iteration and avoids overwriting mistakes.

• Collaboration Gateway – Enables sharing across teams or classrooms.