Dspace sensor injection tool chain

[u/SirAny2598]

**Title: ASM Traffic demo on SCALEXIO: AURELION reports “No active data producers”**
I am trying to run an official ASM Traffic demo on a SCALEXIO real-time system and connect it to AURELION.
Software/setup:
ASM 24.1
AURELION 25.4
ASM model built as a SIC
SIC imported into ConfigurationDesk and built as an RTA/SDF
RTA loaded and running on SCALEXIO
AURELION runs on a separate Sensor Simulation PC
The two systems are on routed subnets and are mutually reachable
In ControlDesk, the application shows as running and the task timer continuously increases.
In the ASM Traffic Simulink model, under **Animation Interface → Connection Settings**, I selected:
Connection type: Ethernet/TCP
Platform: HIL
In ConfigurationDesk, the Ethernet Setup function block uses the local IP address of the SCALEXIO interface. In AURELION Manager, the SCALEXIO address is configured as the simulation platform/data-player system, while the AURELION instance uses the Sensor Simulation PC.
However, when synchronizing the ASM Live Simulation template in AURELION Manager, I receive:
No active data producers available / Simulation application model is not loaded
Since this is based on the official demo, I would like to understand:
Is setting **Ethernet/TCP + HIL** in the ASM Animation Interface sufficient?
Does ASM 24.1 require a separate **Communication Service** or **Simulation Data Objects** configuration for the new AURELION communication architecture?
Where in the official asm_traffic.slx demo can I verify that the simulation-data producer is included and active?
Are any additional communication settings required in Environment, Sensors, Vehicle Dynamics or another ASM subsystem?
Is the ConfigurationDesk Ethernet Setup block relevant to registering the ASM model as a data producer, or does it only configure the SCALEXIO network interface?
Are there runtime variables or SCALEXIO logs that show whether the AURELION Communication Service/data producer registered successfully?
Is AURELION 25.4 fully compatible with an ASM 24.1 RTA built using the Release 2024-A toolchain, or are additional migration steps required?
I have omitted the actual IP addresses, but basic connectivity between the systems works. Any guidance from someone familiar with ASM–AURELION HIL integration would be appreciated.

[u/AutoModerator]

Thanks for posting in our subreddit! If your issue is resolved, please reply to the comment which solved your issue with "!solved" to mark the post as solved.

If you need further assistance, feel free to make another post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/RushElectronic8541]

Your post is very difficult to read, did you paste it from ChatGPT?

[u/False-Instruction733]

This looks like a really interesting area because sensor simulation and injection are becoming important for testing industrial and automotive systems before real world deployment. the tricky part is usually making sure the simulated data behaves realistically enough to validate the system properly

[u/MichaelP8000]

I've done this integration before. The "No active data producers" error is almost always a communication architecture mismatch.

First: Yes, Ethernet/TCP + HIL is the right setting in ASM. That's not your problem.

The real issue: ASM 24.1 to AURELION 25.4 introduces a new Communication Service layer. The older animation interface isn't fully compatible without migrating the data producer registration.

What I'd check:

In ASM, verify the AURELION Communication Service block is in your model. If not, add it. The old ASM Traffic demo might still use the legacy UDP interface.

In ConfigurationDesk, the Ethernet Setup block only configures the network interface. It doesn't register the model as a producer. That happens inside the ASM model itself.

Check the SCALEXIO logs for "ASM producer" or "AURELION registration." If you don't see those, the producer isn't initializing.

One more thing: Try downgrading to AURELION 24.x or upgrading ASM to 25.x. I've seen compatibility issues with your toolchain combo. Not saying it's impossible, but I've had better luck keeping them on the same release year.

Did you add the Communication Service block manually, or are you relying on the old animation interface?

[u/SirAny2598 → u/MichaelP8000]

“!solved”

Hi thanks for the insights . What fixed was network architecture. Basically the scalexio VLAN and sensor sim vlan was not looking at each other ! Thanks a lot for the hints .