EIM Modbus RTU - Revision history

Thomas Peterson: /* CAT Shutdowns */

2026-05-08T15:11:35Z

CAT Shutdowns

← Older revision		Revision as of 15:11, 8 May 2026
Line 113:		Line 113:

	==== CAT Shutdowns ====		==== CAT Shutdowns ====
	If the CAT ECM triggers the shutdown, the annunciator shutdown code mentioned above will simply be the "CAT Run Status" digital in contact. In this case, the CAT shutdown code can be read from EDT register 30125, which is also on the unified data table at register 32020. This value can be decoded from this list: https://~~drive~~.~~google~~.~~com~~/~~open?id=1zGHh2RmHCGNMZBgyr9QDblb_LLB5ipP3~~		If the CAT ECM triggers the shutdown, the annunciator shutdown code mentioned above will simply be the "CAT Run Status" digital in contact. In this case, the CAT shutdown code can be read from EDT register 30125, which is also on the unified data table at register 32020. This value can be decoded from this list: https://xtest.blob.core.windows.net/wikistaticfiles/EDT_J1939_DTC_SPNS.xlsx

Thomas Peterson: /* Annunciator Shutdowns */

2026-05-08T15:11:03Z

Annunciator Shutdowns

← Older revision		Revision as of 15:11, 8 May 2026
Line 104:		Line 104:
	On shutdown, the shutdown code can be read using a variety of registers. There are several options, which are just arranged different ways. The tables decoding these registers can be found here:		On shutdown, the shutdown code can be read using a variety of registers. There are several options, which are just arranged different ways. The tables decoding these registers can be found here:

	Annunciator Reg 35015 and 35017: https://~~drive~~.~~google~~.~~com~~/~~open?id=1GyCeOG0lYrgj97tP3rrb8Hv76WeVYChp~~		Annunciator Reg 35015 and 35017: https://xtest.blob.core.windows.net/wikistaticfiles/EMIT_Regsiter_35015_or_35017_Decode.xlsx

	Annunciator Register 35016: https://~~drive~~.~~google~~.~~com~~/~~open?id=1de1KlMhbg3ZsiZHVexJuSIFBHFOrKVJ_~~		Annunciator Register 35016: https://xtest.blob.core.windows.net/wikistaticfiles/EMIT_Register_35016_Decode.xlsx

	Note that in the "Unified Data Table", Register 32042 pulls the same value as Annunciator Register 35015 above.		Note that in the "Unified Data Table", Register 32042 pulls the same value as Annunciator Register 35015 above.

Thomas Peterson: /* Modbus Table */

2026-05-08T15:09:31Z

Modbus Table

← Older revision		Revision as of 15:09, 8 May 2026
Line 86:		Line 86:
	The modbus table(s) can be downloaded here: https://xtest.blob.core.windows.net/wikistaticfiles/ETS_Modbus_Tables_combined.pdf		The modbus table(s) can be downloaded here: https://xtest.blob.core.windows.net/wikistaticfiles/ETS_Modbus_Tables_combined.pdf

	Note that the Dynamic Control Touchscreen (12" model) has a different modbus table, available here: https://~~drive~~.~~google~~.~~com~~/~~open?id=1uZHGhsb_jMc-kCS1jnT7NDkBjcN0WOxf~~		Note that the Dynamic Control Touchscreen (12" model) has a different modbus table, available here: https://xtest.blob.core.windows.net/wikistaticfiles/Dynamic_Control_Touchscreen_Modbus.pdf

	=== Modbus TCP/IP ===		=== Modbus TCP/IP ===

Thomas Peterson: /* Modbus Table */

2026-05-08T15:08:42Z

Modbus Table

← Older revision		Revision as of 15:08, 8 May 2026
Line 84:		Line 84:

	=== Modbus Table ===		=== Modbus Table ===
	The modbus table(s) can be downloaded here: https://~~drive~~.~~google~~.~~com~~/~~open?id=0BzOiNHLPWdg1UGQzLUktcTZfTVU~~		The modbus table(s) can be downloaded here: https://xtest.blob.core.windows.net/wikistaticfiles/ETS_Modbus_Tables_combined.pdf

	Note that the Dynamic Control Touchscreen (12" model) has a different modbus table, available here: https://drive.google.com/open?id=1uZHGhsb_jMc-kCS1jnT7NDkBjcN0WOxf		Note that the Dynamic Control Touchscreen (12" model) has a different modbus table, available here: https://drive.google.com/open?id=1uZHGhsb_jMc-kCS1jnT7NDkBjcN0WOxf

Thomas Peterson: /* Annunciator Shutdowns */

2022-10-04T20:05:29Z

Annunciator Shutdowns

← Older revision		Revision as of 20:05, 4 October 2022
Line 109:		Line 109:

	Note that in the "Unified Data Table", Register 32042 pulls the same value as Annunciator Register 35015 above.		Note that in the "Unified Data Table", Register 32042 pulls the same value as Annunciator Register 35015 above.

			You can generate a labeled version of the shutdown code registers by uploading a config file here: https://data.emittechnologies.com/tools/

	==== CAT Shutdowns ====		==== CAT Shutdowns ====
	If the CAT ECM triggers the shutdown, the annunciator shutdown code mentioned above will simply be the "CAT Run Status" digital in contact. In this case, the CAT shutdown code can be read from EDT register 30125, which is also on the unified data table at register 32020. This value can be decoded from this list: https://drive.google.com/open?id=1zGHh2RmHCGNMZBgyr9QDblb_LLB5ipP3		If the CAT ECM triggers the shutdown, the annunciator shutdown code mentioned above will simply be the "CAT Run Status" digital in contact. In this case, the CAT shutdown code can be read from EDT register 30125, which is also on the unified data table at register 32020. This value can be decoded from this list: https://drive.google.com/open?id=1zGHh2RmHCGNMZBgyr9QDblb_LLB5ipP3

Thomas Peterson: /* Custom Modbus Map */

2022-08-04T17:21:31Z

Custom Modbus Map

← Older revision		Revision as of 17:21, 4 August 2022
Line 81:		Line 81:

	=== Custom Modbus Map ===		=== Custom Modbus Map ===
	The EIM has the capability to re-map the register numbers to a custom map. This custom map is stored in a csv file, and can be used to create a block of registers with data from various modules. This allows a single read to the EIM Slave ID to pick up all the desired data across multiple modules. This file can be downloaded / uploaded by going to the EIM Modbus screen and choosing “Custom Map…”. More detail can be found on this article: ~~http://forum.emittechnologies.com/knowledgebase/articles/1156870-eim-custom-modbus-map~~		The EIM has the capability to re-map the register numbers to a custom map. This custom map is stored in a csv file, and can be used to create a block of registers with data from various modules. This allows a single read to the EIM Slave ID to pick up all the desired data across multiple modules. This file can be downloaded / uploaded by going to the EIM Modbus screen and choosing “Custom Map…”. More detail can be found on this article: [[EIM Custom Modbus Map]]

	=== Modbus Table ===		=== Modbus Table ===

Sean Sanders: /* Register Scaling */

2022-08-02T20:44:15Z

← Older revision		Revision as of 20:44, 2 August 2022
Line 48:		Line 48:
	=== Register Scaling ===		=== Register Scaling ===
	Each module in ETS has its own Modbus table showing the data at different registers. An example section of the AFRC Lite Modbus table is shown below.		Each module in ETS has its own Modbus table showing the data at different registers. An example section of the AFRC Lite Modbus table is shown below.



	For many registers, the value is scaled to go from a decimal number to an integer. To decode from a Modbus register value to the real value, use the equation below<blockquote>[real value] = [register value][Resolution/Bit] + [Offset]</blockquote>The last two items in the above equation are in the Modbus tables. As an example, perhaps the register 30001 (Pre-Cat Exhaust Temp) was read and the value was 37,077. Using the values from the above table:<blockquote>[real value] = 370770.03125 + (-273) = 885.6 degrees</blockquote>		For many registers, the value is scaled to go from a decimal number to an integer. To decode from a Modbus register value to the real value, use the equation below<blockquote>[real value] = [register value][Resolution/Bit] + [Offset]</blockquote>The last two items in the above equation are in the Modbus tables. As an example, perhaps the register 30001 (Pre-Cat Exhaust Temp) was read and the value was 37,077. Using the values from the above table:<blockquote>[real value] = 370770.03125 + (-273) = 885.6 degrees</blockquote>

Sean Sanders: /* Register Scaling */

2022-08-02T20:13:10Z

← Older revision		Revision as of 20:13, 2 August 2022
Line 49:		Line 49:
	Each module in ETS has its own Modbus table showing the data at different registers. An example section of the AFRC Lite Modbus table is shown below.		Each module in ETS has its own Modbus table showing the data at different registers. An example section of the AFRC Lite Modbus table is shown below.

	<nowiki></nowiki>Insert Image

	For many registers, the value is scaled to go from a decimal number to an integer. To decode from a Modbus register value to the real value, use the equation below<blockquote>[real value] = [register value][Resolution/Bit] + [Offset]</blockquote>The last two items in the above equation are in the Modbus tables. As an example, perhaps the register 30001 (Pre-Cat Exhaust Temp) was read and the value was 37,077. Using the values from the above table:<blockquote>[real value] = 370770.03125 + (-273) = 885.6 degrees</blockquote>		For many registers, the value is scaled to go from a decimal number to an integer. To decode from a Modbus register value to the real value, use the equation below<blockquote>[real value] = [register value][Resolution/Bit] + [Offset]</blockquote>The last two items in the above equation are in the Modbus tables. As an example, perhaps the register 30001 (Pre-Cat Exhaust Temp) was read and the value was 37,077. Using the values from the above table:<blockquote>[real value] = 370770.03125 + (-273) = 885.6 degrees</blockquote>

Sean Sanders: /* Slave IDs */

2022-08-02T20:12:29Z

Slave IDs

← Older revision		Revision as of 20:12, 2 August 2022
Line 43:		Line 43:

	For example, the EIM might have an ID of 10 and the AFRC Lite might be connected and have an ID of 11. If a Modbus master command arrives addressed to either ID 10 or 11, the EIM will respond. For any other address, the EIM will not respond.		For example, the EIM might have an ID of 10 and the AFRC Lite might be connected and have an ID of 11. If a Modbus master command arrives addressed to either ID 10 or 11, the EIM will respond. For any other address, the EIM will not respond.

	<nowiki></nowiki>Insert Image

	~~Modbus Screen showing slave ID setups~~

	If a Modbus request arrives matching a module ID, but that module is not actually attached currently, the EIM will not respond.		If a Modbus request arrives matching a module ID, but that module is not actually attached currently, the EIM will not respond.

Sean Sanders: /* Slave IDs */

2022-07-27T19:39:48Z

Slave IDs

← Older revision		Revision as of 19:39, 27 July 2022
Line 37:		Line 37:
	Any or all of the three connection options above can be used, but in all cases the register numbers and IDs being read (discussed below) are the same.		Any or all of the three connection options above can be used, but in all cases the register numbers and IDs being read (discussed below) are the same.

	<nowiki></nowiki>Insert Image		[[File:ETS Modbus Wiring.png]]

	=== Slave IDs ===		=== Slave IDs ===