I am new to Dynon. But, trying to understand how the system figures out the ranges (and names) for both the MAP and TACH/RPM sensors. When I view the User_Config file, and look within the "ems1 ={", the definitions for MAP and TACH/RPM are confusing:
1) With respect to the MAP definition (and I assume that widget is defined by c37_p26), it just has a single valid range between 0 and 17.1884. Why? And, yet, when I look at the widget in the 100% screen, it shows a much larger range that appears to be between approx 0-30. Why is that? Does the MAP widget pull its range from some other location within the code (not from the MAP definition)?
2) With respect to the TACH, I am confused too by what I see in the User_Config file. First, there appears to be two "valid" definitions that may apply. The first is "c37_p32/34_v2", and the second appears to be "c37_33/35_v2." Does that make sense--to have two valid definitions devoted to RPM/Tach? Second, both of those definitions list names ("RPM L," and "TACH R," respectively) that are different than the name within the EMS 100% screen, which is just "TACH"). Further, the ranges for those definitions do not appear in the widget for the 100% screen. The widget only shows a single green band, not multicolored as the ranges of these sensors imply. What gives? Am I wrong to think that the Widget in the 100% screen is dictated by one of these two definitions?
I have attached the User_Config file and screenshot of the EMS 100% screen.
Lastly, what are the "can_XXXX" definitions within the User_Config file? Are those just ignored by the system and placed in there to help with manual edits to the User_Config file?
Thank you in advance.
1) With respect to the MAP definition (and I assume that widget is defined by c37_p26), it just has a single valid range between 0 and 17.1884. Why? And, yet, when I look at the widget in the 100% screen, it shows a much larger range that appears to be between approx 0-30. Why is that? Does the MAP widget pull its range from some other location within the code (not from the MAP definition)?
2) With respect to the TACH, I am confused too by what I see in the User_Config file. First, there appears to be two "valid" definitions that may apply. The first is "c37_p32/34_v2", and the second appears to be "c37_33/35_v2." Does that make sense--to have two valid definitions devoted to RPM/Tach? Second, both of those definitions list names ("RPM L," and "TACH R," respectively) that are different than the name within the EMS 100% screen, which is just "TACH"). Further, the ranges for those definitions do not appear in the widget for the 100% screen. The widget only shows a single green band, not multicolored as the ranges of these sensors imply. What gives? Am I wrong to think that the Widget in the 100% screen is dictated by one of these two definitions?
I have attached the User_Config file and screenshot of the EMS 100% screen.
Lastly, what are the "can_XXXX" definitions within the User_Config file? Are those just ignored by the system and placed in there to help with manual edits to the User_Config file?
Thank you in advance.
Attachments
Last edited: