EDR Troubleshooting - Missing Compressor Data - Revision history

Thomas Peterson at 17:08, 2 July 2024

2024-07-02T17:08:59Z

← Older revision		Revision as of 17:08, 2 July 2024
Line 35:		Line 35:

	==Check Configuration==		==Check Configuration==

	9. Connect to the EDR wifi console at the location. For instructions, see Appendix A.		9. Connect to the EDR wifi console at the location. For instructions, see Appendix A.

	10. Go to the “Alerts” tab of the console		10. Go to the “Alerts” tab of the console

	11. Open “Current Run Register”		11. Open “Current Run Register”

	12. Verify that the Configuration is correct		12. Verify that the Configuration is correct

	a. The ID should be 1, and the Value/Register should be the following depending on annunciator:		a. The ID should be 1, and the Value/Register should be the following depending on annunciator:

	i. Murphy Centurion C4: 40191		i. Murphy Centurion C4: 40191

	ii. Murphy Centurion Plus: 40641		ii. Murphy Centurion Plus: 40641

	iii. Murphy TTD: 40004		iii. Murphy TTD: 40004

	iv. Altronic DD40: 40004		iv. Altronic DD40: 40004

	v. Altronic DE3000: 40004		v. Altronic DE3000: 40004

	vi. EMIT EIM: 31001		vi. EMIT EIM: 31001

	vii. Others: See annunciator manual for run status register		vii. Others: See annunciator manual for run status register
	b. If the config is not correct, it is possible that the module is not configured at all. See [[EDR_Field_Configuration]] on how to configure an EDR in the field
			b. If the config is not correct, it is possible that the module is not configured at all. See [[EDR_Field_Configuration]] on how to configure an EDR in the field

	==Alter port timings==		==Alter port timings==

	13. In some cases, increasing some port delays can help with communications		13. In some cases, increasing some port delays can help with communications

	c. In the wifi terminal under the “Modbus Master” tab, open the heading “Port Timings”		c. In the wifi terminal under the “Modbus Master” tab, open the heading “Port Timings”

	d. Increase the Write Delay Us to 50,000		d. Increase the Write Delay Us to 50,000

	e. Increase the Read delay Us to 4,000		e. Increase the Read delay Us to 4,000

	After the above steps there should be some sort of value on the current run register under “Alerts”, and it shouldn’t say TIMEOUT. If it does, there is still an issue, it is possible that either the annunciator or EDR port has a hardware issue.		After the above steps there should be some sort of value on the current run register under “Alerts”, and it shouldn’t say TIMEOUT. If it does, there is still an issue, it is possible that either the annunciator or EDR port has a hardware issue.

Thomas Peterson: /* Check EDR Port Setup */

2024-07-02T17:08:32Z

Check EDR Port Setup

← Older revision		Revision as of 17:08, 2 July 2024
Line 8:		Line 8:

	2. Under the “Modbus Master” tab of the wifi console, go to the section “Network Configuration”.		2. Under the “Modbus Master” tab of the wifi console, go to the section “Network Configuration”.

	3. Typical settings, if not using ethernet:		3. Typical settings, if not using ethernet:

	a. Baud 9600		a. Baud 9600

	b. Data size 8 bit		b. Data size 8 bit

	c. Parity none		c. Parity none

	d. Stop 1		d. Stop 1

	e. “Use Serial” should be checked		e. “Use Serial” should be checked

	f. If anything above is changed, be sure to hit ‘save’ button further down below ‘Use IP’. Note that ‘Use IP’ should not be checked.		f. If anything above is changed, be sure to hit ‘save’ button further down below ‘Use IP’. Note that ‘Use IP’ should not be checked.

Thomas Peterson: Created page with "Symptom: On the Connect site there is no compressor data (e.g. Annunciator Run Code, Suction Pressure, etc.), or on the Wifi console there are expected data items with a timeout of “Never”. ==Note that some values may not be present== 1. For a TTD or DD40, there won’t be any process pressures or temperatures (though there can be temperatures if a TDXM or DSM are set up). The Run Status and Fault Code should still show up though. ==Check EDR Port Setup== 2. Unde..."

2024-07-02T17:06:09Z

Created page with "Symptom: On the Connect site there is no compressor data (e.g. Annunciator Run Code, Suction Pressure, etc.), or on the Wifi console there are expected data items with a timeout of “Never”. ==Note that some values may not be present== 1. For a TTD or DD40, there won’t be any process pressures or temperatures (though there can be temperatures if a TDXM or DSM are set up). The Run Status and Fault Code should still show up though. ==Check EDR Port Setup== 2. Unde..."

New page

Symptom: On the Connect site there is no compressor data (e.g. Annunciator Run Code, Suction Pressure, etc.), or on the Wifi console there are expected data items with a timeout of “Never”.

==Note that some values may not be present==

1. For a TTD or DD40, there won’t be any process pressures or temperatures (though there can be temperatures if a TDXM or DSM are set up). The Run Status and Fault Code should still show up though.

==Check EDR Port Setup==

2. Under the “Modbus Master” tab of the wifi console, go to the section “Network Configuration”.
3. Typical settings, if not using ethernet:
a. Baud 9600
b. Data size 8 bit
c. Parity none
d. Stop 1
e. “Use Serial” should be checked
f. If anything above is changed, be sure to hit ‘save’ button further down below ‘Use IP’. Note that ‘Use IP’ should not be checked.

==Check Panel Modbus Setup==

4. The panel should also be set up to 9600 baud. Details on how this is done for different panels is found here: [[Default_Panel_Settings_for_EDRs]]

==Check Wiring==
5. The panel modbus connection should go from pin 4,5 of the EDR to the A,B of the panel. Some panels have multiple modbus ports, see the installation guide for the proper location. [[EDR Installation Guide]]
6. The red switch next to pin 5 of the EDR should be on (toward outside of module)
7. Note that for Altronic panels, the wire will connect from “B” of the EDR to “A” of the annunciator, and “B” to “A”. For Murphy or EMIT panels, the wire will connect from “A” to “A” and “B” to “B”.
a. Note that wires supplied by EMIT will be labeled with this in mind.
8. Make sure nothing else is wired into the modbus going to the annunciator. Only one SCADA can communicate with an annunciator.

==Check Configuration==
9. Connect to the EDR wifi console at the location. For instructions, see Appendix A.
10. Go to the “Alerts” tab of the console
11. Open “Current Run Register”
12. Verify that the Configuration is correct
a. The ID should be 1, and the Value/Register should be the following depending on annunciator:
i. Murphy Centurion C4: 40191
ii. Murphy Centurion Plus: 40641
iii. Murphy TTD: 40004
iv. Altronic DD40: 40004
v. Altronic DE3000: 40004
vi. EMIT EIM: 31001
vii. Others: See annunciator manual for run status register
b. If the config is not correct, it is possible that the module is not configured at all. See [[EDR_Field_Configuration]] on how to configure an EDR in the field

==Alter port timings==
13. In some cases, increasing some port delays can help with communications
c. In the wifi terminal under the “Modbus Master” tab, open the heading “Port Timings”
d. Increase the Write Delay Us to 50,000
e. Increase the Read delay Us to 4,000

After the above steps there should be some sort of value on the current run register under “Alerts”, and it shouldn’t say TIMEOUT. If it does, there is still an issue, it is possible that either the annunciator or EDR port has a hardware issue.