Please help me out here to open the altair one application

How can I plot the outputs of the SOGI-PLL against each other in a single monitor buffer? is it even possible in embed?

My ADC is running at 10khz to read this 50hz signal.

The orange plot is the ADC output of the sense 50hz signal, I plotted it against a 50hz sine wave. There is a huge mismatch. The output of the ADC is not 50hz. These are the settings that produced this weird result

I have noticed that if i reduce the simulation frequency to 0.5khz then the ADC produces a 50hz signal like it should but it messed up my PLL theta output. I didnt find any answers online so here I am. Please help team

Fresh install to see if something was broken on the previous install.
Amutil indicates the license is working, but something is corrupted or locked up.

I found this post:

SOAP 1.1 fault SOAP-ENV:Client [no subcode] "End of file or no input: message transfer interrupted or timed out (5 sec max recv delay) (5 sec max send delay)" - Altair Community

But that user variable does not exist.

i've tried everything i can. I thought the fresh install would certainly fix it. I'm wondering if this is on the server side.

i've deleted the user account and started a new one with the same credentials.

and a new one with different credentials.

Really stuck now.

corrupted dialog

In the e-drive motor control project (open-loop and closed-loop), we initially worked with Launchpad F280049C mcu using the GANINV board, and the system was working fine….In this setup, the *main motor control is executed on interrupt, configured with *ADCBINT1 and EOC2 mode.

Later, we converted the same project to the Launchpad F28P550SJ mcu using the GANINV board. However, in this case, the *main motor control interrupt is triggered only once…In the setup, the main motor control is executed on interrupt: ADCAINT1 and Mode: EOC2.

Additionally,we have also attached the VSM files.

help us to identify the reason for this issue and guide us on how to resolve it.

Regards,

Reshmi Team.

This is the Analog Input block (Embedded→STM32→ADC→Analog Input).

The docs says it output between 0 and 1, this doesn't seem to be the case I tried reading a sine signal (0 to 3 ) using the simulated analog channel block. The output of the Analog input block also outputs sine (0 - 3).

Why is the block outputting 0 - 3 and not 0 - 1 as written in the docs? Its confusing

While opening Embed file , I'm getting this error. It happened after power outage while I was working on the file. Is there anyway to get it back? 😭 Does embed keeps local backup?

I have this simple diagram, I code gen for stm32g431, but when I view the code I can see double cast.

Why is embed using double even though I converted each input and output to float?

This is the inside of "MCU compound". it contains sense signals scaling and processing, inrush control, inner outer PFC loops.

This is the inside of "VAC-iL - Bus processing" compound. I'm using FPU since STM32g4 supports FPU.

this is the inside of "voltage current loop", also in FPU.

I'm trying to do PIL in a separate file, this is the main diagram. System time step is 200khz with run in real time unchecked and target interface sample rate is also 200kHz with sync target to this block checked. Code gets downloaded successfully but when I hit f5 after 3secs it say "program did not start on DSP"

Here are some of my doubts -

1. Is the problem with the MCU not being able to process the FPU?
2. Blocks like const, multiplier , summer etc is default to "double", do I need to add convert block to float for each of this blocks as stm32g4 only support single precision FPU?
3. If I decide to use the fixed point then do i need to convert each block to fixed point including simple blocks like const, multiplier etc?
4. as you can see in the image I'm using local time step for blocks like rms, PLL, PI,etc will code gen work with this set up?
5. When i run the MCU compound file, it works as expected, error happens only during PIL.

Any help is greatly appreciated. If any more information needed then please let me know.

Anthony Boon
Digital Power Consultant for Altair

Summary

The steps performed to develop a battery management system (BMS) demonstration for EV applications are outlined. Three application examples are given, differing by their hardware implementation, starting from the initial experimentation to the routine development and on to a final production-ready design:

1. BMS system set-up connected directly to the Embed GUI using real-time serial communication.
2. BMS system set-up using a microcontroller board performing the real-time communication, control, and monitoring functions while connected to the Embed GUI.
3. BMS system set-up using a central microcontroller and CAN communication with a vehicle control unit (VCU). 

Introduction

Battery Electric Vehicles (BEVs) are becoming ever more popular and in high demand. The most critical and costly element of the BEV is the battery system. In order to guarantee optimal performance, it is important to continually monitor the battery pack and the enclosed cells connected in series under all driving conditions and during battery charging.

The charging is required to occur in ever shorter intervals and at higher power, placing more stress on the battery if not managed correctly. The battery needs to be maintained in optimal condition to guarantee the maximum mileage range and life expectancy, by monitoring and controlling the equalization of the many cells in series, while maintaining the operating temperature of the battery pack within limits.

Balancing the cell voltages during charging is necessary in order to equalize the charge applied to the cells, therefore maximizing the available state-of-charge (SOC) of the battery pack. Balancing the cell voltages also aids in maximizing the lifetime and optimizing the performance over that lifetime, thereby maximizing the so-named state-of-health (SOH) of the battery pack.

The following BMS demonstration uses the bq76PL455EVM evaluation module (https://www.ti.com/tool/BQ76PL455EVM) from Texas Instruments (TI) as shown in figure 1. 

Figure 1: Texas Instruments bq76PL455EVM evaluation module.

The TI bq76PL455EVM evaluation module supports from six to 16 cells in series, and up to six bq76PL455EVMs can be connected in a series configuration for a maximum of 96 cells in series (96S). However, the bq76PL455-q1 BMS chip of the evaluation module supports up to 16x16 cells in series (256S).

The evaluation module requires a flexible battery setup in order to verify the configurability and robustness of the developed algorithms. For this reason, the battery board as shown in figure 2 was developed to connect directly to the TI bq76PL455EVM.

Figure 2: Battery board developed to evaluate the bq76PL455EVM together with Altair Embed.

The battery board supports from one to 16 type 18650 cells connected in series. Other battery boards can be connected in series (or parallel) for higher battery pack voltages (or capacity), together with multiple bq76PL455EVM evaluation modules (figure 9). 

Application example 1

In this first application example, the TI bq76PL455EVM evaluation module is connected directly to the PC via a real-time serial interface. The bq76PL455EVM is powered by eight LiFePO4 cells mounted in a series configuration on the battery board. The LiFePO4 cells have a nominal voltage of 3.2V and are charged at a nominal charge voltage of 3.6V/cell. 

Figure 3: BMS setup with 8 series cells connected to a charger/load. The serial communication interface of the bq76PL455EVM is connected directly to the PC running the Embed GUI.

The communication, monitoring, and control routine is performed in the Embed diagram running on the PC, which also forms the GUI of the battery monitoring system in this first application example. The Embed GUI reports all cell voltages, selected cell temperatures, alarms, balancing, and status of the BMS system and battery by constantly polling the bq76PL455EVM BMS module. Some pages of the Embed GUI developed for this system are shown in figure 4.

Figure 4: Example pages of the Embed GUI.

The BMS system is completely configurable using the Embed GUI, as shown in figure 5. 

Figure 5: Examples of the Embed GUI available configuration dialogs.

The Embed GUI accurately reports the current condition of the battery pack and the BMS system and balancing. The GUI is also configurable for logging data and can be easily modified for customer-specific applications using the Embed IDE.

         
Figure 6a: Cell voltage imbalance after charging with balancing disabled.               Figure 6b: Cell voltage balance after charging with balancing enabled.

Figures 6a and 6b compare the results of charging with balancing disabled and balancing enabled. Any small difference in the initial state of the battery cells and, in particular, the SOC of each individual battery cell causes differences in the cell voltages toward the end of the charging cycle. Even if initially small, these differences will increase over time after many discharge-charge cycles. Without cell voltage balancing, the result is an imbalance in the SOC of the cells, causing the battery pack as a whole to not be optimally charged and therefore not provide the optimal mileage range. Also, the charge imbalance can cause detrimental effects in the battery cells during use, decreasing the lifetime of the battery pack. In the worst case, catastrophic failure of one or more cells due to severe overcharging can occur.

The majority of the imbalance in the equalization of the cells normally occurs above 90% of SOC toward the end of charging and for this reason, the charging may be terminated at 90% of SOC to help prevent overcharging of individual cells. Similarly, the battery may be shut down from discharge during driving when the SOC reaches 10% in order to protect against over discharge (reference 4). This results in a nonoptimal mileage range due to the inability to utilize 100% of the battery capacity. A correctly balanced battery, along with an accurate SOC determination can optimize the SOC limits for the cut-off of the charger, as well as the battery when in discharge. 

The BMS system also monitors cell temperatures, which are particularly critical during rapid charging. If a cell temperature begins to rise unexpectedly, an appropriate action – such as reducing the charging rate or switching off the charger – must be immediately taken. By controlling the battery temperature with the cooling/heating system, together with the monitoring of the cell temperatures, the available mileage range can be optimized because the available battery capacity is temperature dependent.

Comparator thresholds are completely configurable for all cells and actions can be taken depending upon the type of event or measurement performed.

Application example 2

In this application example, the TI bq76PL455EVM evaluation module serial interface is connected to the TMS320F28379 microcontroller mounted on an experimenter kit baseboard (https://www.ti.com/tool/TMDSDOCK28379D). Communication with the bq76PL455EVM and the necessary BMS operations are now performed directly in the microcontroller, while the microcontroller communicates the data to the Embed GUI via the JTAG interface. The use of the JTAG interface together with the Embed IDE significantly improves debugging the BMS communication, control and monitoring software when compared to other development environments. 

The battery pack configuration selected in this example has 16 series 18650 Li-Ion cells that are charged at a nominal 4.2V/cell. The configuration is shown in figure 7.

Figure 7: BMS setup with a Texas Instruments TMS320F28379 microcontroller interfaced directly to the EVM.

The internal control block in the Embed GUI diagram of application example 1 is code-generated and compiled for the selected microcontroller using the compound block edge pins for data exchange. The generated OUT file is then linked in a target interface block to run the entire application in the microcontroller RAM. The Embed GUI, in this case, communicates with the microcontroller over the JTAG interface. The microcontroller communicates directly with the bq76PL455EVM over the serial interface. The microcontroller also measures the battery pack voltage and current through a direct connection to the battery board, which is used for the determination of the SOC.

       
Figure 8: Embed GUI applied to Application Example 2.

This application can be easily expanded to more cells in series for higher battery voltages, using multiple battery boards and bq76PL455EVM modules. An example is the 32 cell, series configuration (32S) as shown in figure 9.

Figure 9: BMS setup with stacked EVMs and battery boards for higher battery voltages (in this case with a nominal battery voltage of 134.4V).

In this case, EVM2 is also enabled in the Embed GUI resulting in the population of the cell voltages and temperatures for cells 17 to 32, as shown in figure 10.

      
Figure 10: Embed GUI for Application Example 2 with EVMs 1 and 2 enabled for up to 32 series cells.

Application example 3

In this application example, the TI bq76PL455EVM evaluation module is connected to the microcontroller as in application example 2; however, the routine has been programmed into the non-volatile flash memory of the microcontroller and the BMS control routine can operate independently. Communication with the vehicle control unit (VCU) and monitoring system is performed over a CAN bus interface as shown in figure 11.

Alternatively, the microcontroller can communicate with an external device through a serial RS485 or SPI interface, depending upon the desired final hardware infrastructure. The microcontroller can also concurrently communicate with the Embed GUI through a second serial interface or over the JTAG interface, if additional debugging is required during this procedure.

The firmware as developed in figure 11 can be applied to BEVs, with modules similar to the bq76PL455EVM located near the monitored cells in the battery pack and a single BMS monitoring and control, microcontroller board located in a central and accessible location in the vehicle.

Figure 11: Independent operation of the BMS system with CAN bus communication with the vehicle control unit (VCU), and BMS firmware ready for application with in-vehicle operation.

Conclusions

The examples have been successfully developed with the TI bq76PL455EVM evaluation module equipped with the TI bq76PL455-q1 BMS chip. The BMS algorithms can be completely developed, debugged and verified in the Embed IDE for production-ready applications. The algorithms can be easily developed for (or converted to) other manufacturer’s BMS chips, and their corresponding evaluation modules such as: 

• The evaluation module EVAL-L9963 using the ST L9963 chip -  https://www.st.com/content/st_com/eval-l9963.html

• The evaluation module TLE9012AQU_DTR_BMS2 using the Infineon TLE9012AQU chip - https://www.infineon.com/cms/en/product/evaluation-boards/tle9012aqu_dtr_bms2/
  
  
• The evaluation module FRDM33771BTPLEVB using the NXP MC33771B chip – FRDM33771BTPLEVB | MC33771 TPL EVB | NXP Semiconductors
  
  
• The evaluation module DC2259A using the Analog Devices LTC6811 chip – DC2259A Evaluation Board | Analog Devices
  
  
• The evaluation module MAX17853EVKIT using the Maxim MAX17853 chip – MAX17853EVKIT Evaluation Kit for the MAX17853 - Maxim Integrated

The communication, control, and monitoring algorithm has been developed for the TI TMS320F28379 microcontroller and can be easily converted for any automotive compatible or other microcontroller such as the TMS570 from TI, the Aurix series from Infineon or any of the STM32 chips.

The development and debugging of the communication, control, and monitoring algorithms was greatly simplified using the visual, model-based development environment of Embed: A complete, production-ready design of the BMS firmware can be developed using only the Altair Embed IDE.

Learn more about Embed through comprehensive help guide : Embed Help

References

1. Texas Instruments: SLUUBA7A, bq76PL455EVM and GUI User Guide;  https://www.ti.com/lit/ug/sluuba7a/ 
   
   
2. Texas Instruments: SLUSC51C, bq76PL455A-Q1 Datasheet; BQ76PL455A-Q1 data sheet, product information and support | TI.com 
   
   
3. Texas Instruments: SLVA617A, bq76PL455EVM Software Design Reference; bq76PL455A-Q1 Software Design Reference (ti.com) 
   
   
4. Electronic Design: Battery Management ICs give Electric Vehicle Batteries a Boost; https://www.electronicdesign.com/power-management/media-gallery/21150953/battery-management-ics-giveelectric-vehicle-batteries-a-boost 

About the author

Anthony Boon 

He has thirty-five years of experience in the power electronics industry in Australia and Europe, designing, developing and verifying complete power conversion systems, from the power and control electronics, magnetic and thermal design, control algorithms and firmware design. His last 25 years have been especially dedicated to the digital control of those systems for real-time embedded control and simulation of power conversion systems using Altair Embed, which has been a critical tool for his work in this area.

Over the past 20 years, he has been working as a consultant in the fields of power conversion technology and digital control, developing complete systems for customers such as critical battery back-up systems including the development of the appropriate battery management technology.

I set up a simple diagram. A pulse generator to PC6 (onboard LED) and PA10. In hardware i connected PA10 and PA1. PA1 is the ADC2 output, ADC is trigger by Tim1_trgo2, then finally ADC reading is send to PA4 where my LED is connected.

when I run this in HIL with "sync target to this block" enabled , nothing shows in plot not even the CPU usage (sometimes target not respond error), without the sync target I see PC6 led blink but not the wired led (I tested the led on the same port using the GPIO block only and it worked, wired led is healthy) . The error happens only when I do the ADC route.

These are the relevant screenshots

Things I tried -

1. Different PWM speed
2. Different Embed time step and target interface sample rate.
3. Enabled the execute on interrupt option.
4. Restarting embed and force reset the MCU

Please help me. I have been banging my head with all the AI chatbots and Embed Docs but cannot find a solution. I'm still a beginner in this field so please excuse me if anything seems illogical 😄

I have this SOGI-PLL from DPD , I want to edit this block , I edit this block by going to File → Diagram Information and made the changes but when I save and close the file then reopen , it reverts back to how it was. How can I make permanent change to any blocks inside DPD menu.

In the Induction motor project, the 1/x unit properties inside of slip frequency calculator block, there is a value like (Hz) = 10 (Slip Freq Calculator block location; main motor control -> foc /current controller im -> slip freq calculator -> 1/x unit properties).

1.What is the purpose of this Pole(Hz) value=10 ?

Induction motor project path; eDrives\Advanced User Guide Diagrams\IM_3ph_FOC_sensored_TI\HIL-F0049- GanINV\IMFOC_sensored_F0049-GANINV-compile.vsm

2. I am unable to open that block; it is locked.

Regards,

Reshmi Team

Hi everyone,
I'm trying to get DMA to transfer ADC1 data to memory (0x20000000) automatically on STM32G431CB. ADC1 is triggered by TIM1_CC1. If I set DMA trigger source to ADC1 and try to codegen then it throws this Picture 2 error.

I checked all the DMA block examples provided by Altair, but I did not understand anything since I am a beginner in this field and the examples don't seem to use ADC, but simple waveforms read and write.

I also checked YouTube and AI tools but couldn't find any useful information. It's very hard to learn Embed, there is very limited beginner-friendly docs and tuts.

Any help is greatly appreciated. Thank you

I have designed a PFC (Power Factor Correction) circuit using Altair PSIM and I now want to generate embedded code for it using Altair Embed v2025.1 targeting an STM32 microcontroller.

However, I'm struggling to get started because I can't find any beginner-friendly learning resources or tutorials for the latest version of Embed. The interface and workflow are very new to me, and it’s a bit overwhelming since I’ve never used this kind of software before.

Can anyone please guide me through the steps required to generate the embedded code for my PFC circuit using Embed? I’d really appreciate it if someone could walk me through the basics and help me understand the process clearly.

For context:

• I'm a Bachelor’s student in Electronics, very eager to learn.
• I can offer a small BTC payment for a personal tutorial, though it's not much.

Please help if you can 🙏.

Product/Topic Name :

Altair PSIM + Altair Embed v2025.1
Target: STM32 Microcontroller

We are currently using the Altair Embed 2024 license version.
While reading the encoder (GPIO24 & GPIO25) using the TMS320F28379D in our own microcontroller , we are experiencing missed pulse counts.
(Our motor has a tick count of 4000 per full rotation)

Ideally, the tick count should go from 0 to the maximum for one full rotation, but we are missing around 200 tick counts. Additionally,we have attached vsm file.

Regards,

Reshmi R&D Team.

Any ideas on what I could be doing wrong?

I have encountered an issue where a function regarding the Json create string block is missing an argument, even though all the connections are connected on the block. I have attached my vsm file below for review.

My vsm files are attached below as well. Is this a bug of the mqtt subscribing block, if not is there any solution? Thank you

Can I preload FLASH with option 'Use selected compound edge pins for data exchange' and after that attach JTAG Target Interface for debugging code in FLASH?

PS. No need to answer, everything works, thanks. I did not find how to remove the topic

Two Examples are described in this document:

Example 1: Include C code into your Embed diagram and simulate it.

Example 2: Create firmware from the same C code function, execute it on a target MCU, and plot the real time results on the PC running Embed. For this example, the Texas Instruments F28069M MCU is used.

Example 1: Include C code into your Embed diagram and simulate it:

Step 1: Copy/paste calcFactorial.c into the \cg\include subfolder located in the Altair Embed installation folder OR any folder, for example; had you created a “/test/codegen” folder in the Embed install folder (ex. “C:\Altair\Embed2025_64\test\codegen), calcFactorial.cfile would be copied into this subfolder.

Step 2: Create an Embed diagram using the Extern blocks. These blocks are universal and can be obtained from any of the Embedded targets, for this example blocks are obtained from the Arduino Target. Add one Extern Definition and Extern Function block to your diagram.

* The Altair Embed installation folder name will vary based on the version of Embed you are using.

Step 3: Configure the Extern Definition and Extern Function blocks to access your c code.

Step 4: Encapsulate the Extern Definition and Extern Function blocks into a compound block with one input and one output, we’ll name the block factorial. Make sure the Extern Function block in the factorial compound block is connected to the compound block input and output pins.

Step 5: Name the Embed diagram and save it. The codegen will produce a .c file with the same you assign to the Embed diagram. Make sure you do not use the C source file name as this will create a duplicate .c file. We will name the Embed diagram calcFactorial88.vsm

Step 6: Select the factorial compound block and select Tools/ Code Gen… to create a DLL

Step 7: After the Compile… is completed, a User Blocks dropdown is automatically added to the Embed Menu bar containing the DLL name in its dropdown menu.

Step 8: Run the diagram to test the DLL and display the results. The simulation will be terminated at 5-factorial because the calcFactorial function returns an integer which limits to 2^16 = 65536

Example 2: Create firmware from the same C code function, execute it on a target MCU, and plot the real time results on the PC running Embed. For this example, the Texas Instruments F28069M MCU is used.

Reuse Steps 1, 2, and 3 from Example 1

Step 4: Add a config block to the diagram for the MCU being used, in this example the F28x config block is used. The diagram becomes:

Step 5: Name the Embed diagram and save it. The codegen will produce a .c file with the same you assign to the Embed diagram. Make sure you do not use the C source file name as this will create a duplicate .c file. We will name the Embed diagram calcFactorial88.vsm

Step 6: Select the factorial compound block and select Tools/ Code Gen… This creates the .out file (firmware file) from the c source file.

Step 7: Insert a Target Interface block from the Embedded/ F280x menu and connect its inputs and outputs

Step 8: Connect the F28069M launchpad to your PC and run the diagram. The Target Interface module loads and executes the firmware to run on the F28069M target. Use the plot block to view the results.

I am using BLDC motor...in this motor magnetic encoder is provided with 4000 counts/revolution.
However, here I am attaching file for encoder base frequency which you can use in your diagram and you can see within the compound block the implementations using band pass filters (LPHPF) and Speedpole (2000Hz).
Can you please signify what is speed pole and why 2000 Hz value you have used here ?

We are trying to work to define a function and call it to another function.But shows below errors.

Error 1: "ReadHolding_Reg.c", line 23: error #18: expected a ")"

Error 2:"ReadHolding_Reg.c", line 23: error #142-D: unnamed prototyped parameters not allowed when body is present

Error3:"ReadHolding_Reg.c", line 74: error #141: too many arguments in function call

Below warnings are occured:

1.".\include\ti\f28004x\debug.h", line 86: warning #48-D: incompatible redefinition of macro "ASSERT" (declared at line 228 of "C:\Altair\Embed2023_64\vsdk\include\Vsuser.h")

2."ReadHolding_Reg.c", line 33: warning #225-D: function "crc16" declared implicitly

3."ReadHolding_Reg.c", line 40: warning #161-D: declaration is incompatible with previous "crc16" (declared at line 33)

We tried several methods but still the same error was occured.Here we attached our .VSM file generated c code also..

Thanks & Regards,

Reshmi R&D Team.