Skip to main content
pxia.1
pxia.1
Associate II
Oct 14, 2026 10:23 PM UTC
Solved

STEVAL-STWINBX1 not receiving telemetry from EVLSPIN32G4-ACT

I am following https://www.st.com/resource/en/product_presentation/evlspin32g4-act-and-stwinbox-high-speed-datalogging-for-motor-control-and-sensors-quick-start-guide.pdf using hardware STEVAL-STWINBX1+EVLSPIN32G4-ACT 

 

https://github.com/STMicroelectronics/stdatalog-pysdk.git v1.5.0 stdatalog_MC_GUI.py is able to start/stop the motor operated in sensorless mode, correct GUI view and .dat file stored for all onboard sensors. But enabling slow/fast motor telemetries leads to error message: 

“HSDatalogApp.stdatalog_gui.HSD_GUI.HSD_Controller - ERROR - No data from fast_mc_telemetries Component.”

 

For suggestion “Restart the acquisition lowering component ODR to acquire data correctly.”, I tried to only enable one data item in slow telemetry, and had the same failure.

 

FW build env for both PMSM and STWIN.box:

  • MotorControl Workbench_6.3.0
  • STMCubeIDE 2.1.1
  • STMCubeMX 6.12
    • STM32 FW V1.5.2

When importing the STWIN.box FW project, among three projects(DATALOGMC, DATALOGMC_CubeAI, DATALOGMC_NanoEdgeAI) in STM32CubeFunctionPack_DATALOGMC_V2.2.1, I selected DATALOGMC.

 

Misc:

  • Flex cable STEVAL-FLTCB04 is connected, being able to start/stop the motor from stdatalog_MC_GUI.py confirms the electrical connection.
  • Motor Pilot can also control EVLSPIN32G4-ACT

 

I guess there might be a compile/run time switch to enable the telemetry from EVLSPIN32G4-ACT. I tried but wasn’t successful in finding such instruction. Many thanks in advance for your suggestions.

 

SimonePradolini
SimonePradoliniBest answer
ST Technical Moderator
Oct 26, 2026 2:06 PM UTC

Hello ​@pxia.1 

We tested the software and firmware with a couple of different hardware setups, and it is working fine on our side.

Could you please perform some additional testing? This is how we expect DATALOGMC to work:

  1. Flash both boards.
  2. Connect the boards to each other using the flex cable.
  3. Connect the STWIN.box board via USB and open the Python example.
  4. Press Start Motor with the default parameters. The motor should start running.
  5. Press Start Log with the default parameters. A logging session will start, and we expect all data to be captured.

If the motor does not start at all, there may be a fault in the Motor Control firmware. DATALOGMC can help resolve this issue:

  1. Press Start Log even if the motor is blocked.
  2. If a fault is acknowledged, press Ack Fault to reset the Motor Control status.

This procedure should solve the issue. From the next log session, the motor should start working properly.

Please also note that the DATALOGMC firmware expects data from the Motor Control side. Therefore, make sure not to start logging before starting the motor.

 

Best regards,

Simone

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
View in thread

4 replies

SimonePradolini
SimonePradolini
ST Technical Moderator
Oct 21, 2026 12:06 PM UTC

Hello ​@pxia.1 

I’m checking with the team in charge of the package. Let’s see if we can replicate your issue. I’ll keep you posted.

 

Best regards

Simone

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
SimonePradolini
SimonePradoliniBest answer
ST Technical Moderator
Oct 26, 2026 2:06 PM UTC

Hello ​@pxia.1 

We tested the software and firmware with a couple of different hardware setups, and it is working fine on our side.

Could you please perform some additional testing? This is how we expect DATALOGMC to work:

  1. Flash both boards.
  2. Connect the boards to each other using the flex cable.
  3. Connect the STWIN.box board via USB and open the Python example.
  4. Press Start Motor with the default parameters. The motor should start running.
  5. Press Start Log with the default parameters. A logging session will start, and we expect all data to be captured.

If the motor does not start at all, there may be a fault in the Motor Control firmware. DATALOGMC can help resolve this issue:

  1. Press Start Log even if the motor is blocked.
  2. If a fault is acknowledged, press Ack Fault to reset the Motor Control status.

This procedure should solve the issue. From the next log session, the motor should start working properly.

Please also note that the DATALOGMC firmware expects data from the Motor Control side. Therefore, make sure not to start logging before starting the motor.

 

Best regards,

Simone

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question.
pxia.1
pxia.1Author
Associate II
Oct 26, 2026 5:08 PM UTC

Hi, Simone, thank you so much for your help. I manage to get Fast Motor Telemetries working through recreating MC firmware. In my MC firmware used earlier, I enabled some debug features such as open-loop, I haven’t narrowed down to the root-cause. Any hints?

GMA
GMA
ST Technical Moderator
Oct 27, 2026 4:31 PM UTC

Hello ​@pxia.1,

Open Loop should be enabled in the MCSDK Workbench: Drive Settings tab, Debug Settings and enable Open Loop flag.

If you agree with the answer, please accept it by clicking on 'Best answer'.Best regards.GMA
Terms & ConditionsAccessibility statement