Hey there,
The problem may be caused because of the following reasons. Try all of these out, and it should solve the problem.
Check signal connection: Double-check the connection between the CO2 signal in Simulink and the gauge in your app designer interface. Ensure that you have correctly linked the output signal of the CO2 calculator to the input of the gauge.
Verify signal compatibility: Confirm that the CO2 signal from Simulink is compatible with the gauge in your app designer interface. Check if the signal type, range, and units match the requirements of the gauge component.
Update Simulink version: Make sure you are using the latest version of Simulink. There might be compatibility issues between the older version you are using (R2019b) and the app designer interface.
Check for errors or warnings: Look for any error messages or warnings related to the gauge component or the signal connection. Resolve any issues reported by Simulink or the app designer that could be causing the gauge to freeze.
Test with a different signal: Try connecting a different signal to the gauge in your app designer interface to see if it responds correctly. This will help determine if the issue is specific to the CO2 signal or if it's a general problem with the gauge component.
