Your comments

It works differently on MD4 compared to the DCC channels for MD3/MDL2.
On the MD4, there is one property in the display page properties for controlling the backlight.

Your question came in as a helpdesk case. Do you mind if I publish this in the public section for questions?
Hi Nick,

For the font, what you can do today is to change the font in the language settings. (not sure the example I show here makes it more readable though.. )

Changing this font property affects the entire project file, both menu system and display pages.

For the font size and theme colors, the properties for this currently only affect the display pages, and not the built-in menu system.

If you send out TSC1 with the same priority and source address, you will undoubtedly get a CAN arbitration error. One of the CAN controllers will quickly go into bus-off, and that MD3 will show a CAN error.

If you send TSC1 with different priority and same source address, then CAN in itself will not be the reason for failure. But the engine would receive conflicting messages from what it would believe is the same controller.

If you send TSC1 from different source addresses, then it depends on the engine which source address it is that will win, if it does not see this as an error. Most engines only accept TSC1 from a few limited source addresses.

Obviously, if your add-on goes in and overrides the original system, then the machine may not work as designed.
What I suggest you do is to speak to the OEM about this modification, we should be able to provide you with a contact person.
Hi Zach,

I am not sure that I understand what the error is?
I made a quick test with four text labels, the top one at 100 pixels from top, and the bottom one at 400 pixels from the top.

Before pressing Distribute controls vertically:

Just after pressing Distribute controls vertically:

The Distribute controls vertically has moved the middle objects, they are now at 200 and 300 pixels from the top.

Only the middle objects are highlighted after the operation, these are the ones that are moved.

Thanks for pointing this out, I checked and the same problem exists in 3.17.
Hi Zach,
For the control of a state via both drop down (state picker) and buttons for next/previous, try the attached file:
state picker and next-previous.ids3
The trick here is to make use of the MEM channel value type, by connecting a State Parameter as the input to the MEM, the MEM get value type State. The MEM can now be adjusted via the state picker.
You can now also use the Activating function in the MEM to replace its valve with the value from the State Parameter, this value comes directly from the ECNT. This way the MEM value will be modified by the buttons for next/previous.
The final part is that the ECNT is reset if there is a change in the MEM when there is no button input. This way you know there state was changed using the state picker. The reset value for the ECNT is the new state number.

Hi Kerim,

There is a quite big difference in the leakage current for DOUT-A to DOUT-C compared to DOUT-D to DOUT-E.
DOUT-D to DOUT-E are designed to work with smaller loads and to work with LED:s where a low leakage current is needed.

You can find the specified leakage current in the Appendix A of the MC3 instruction book:
Interesting. I did some quick checking about that rule, and I believe that the rule that you must register the IMEI within a certain time period is specific Turkish legislation. Some info (about normal cell phones for personal use) here:

I have never heard of this being an issue in any other European country.
The RS232 modem (IQAN-G1) is not possible to use with the MD4, but you can use the IQAN-G2 and have the same SMSOUT functionality.