Recurring COM4 Communication Fault on Honeywell Galaxy GD96 (Need Help)

[bubbletea]

Hi everyone,

I’m having an issue with a COM4 COMMUNICATION FAULT on my Honeywell Galaxy GD96 (v7.02) panel.

I’ve tried absolutely everything: I swapped the Ethernet module several times, reconfigured the panel, optimized the network setup—nothing seems to fix it.

The Ethernet module is an E080-10 v4.16, showing 100% in the diagnostics menu. The module does receive connections via GX Remote Control and the Honeywell RSS software, but the SIA connection stops teletransmitting to the monitoring station after a while and display COM4 COMMUNICATION FAULT. The only way to restore communication is by power-cycling the module.

It’s connected to the panel via RS232.

The fault appears randomly, usually after 4–5 days of operation. I’ve optimized the transmission settings, but the issue persists.

I’m reaching out because after months of trying, I still haven’t found any solution. I manage the panel myself.

Does anyone have an idea what could be causing this?
I’m attaching the Ethernet module configuration and the log history.

@GalaxyGuy I saw your posts, if you can help

(PS: I'm not using selfmon, i just figured out what it is, i failed the tag in the post, i'm in France. Do you think i should use it to avoid this problem ?)

Thanks in advance!

 

[GalaxyGuy]

Hi, it's difficult to know if this is internet availability or your provider service is the cause. You have heartbeat set to every 30 minutes, switch that to 0.

If you do end up using SelfMon, then at least I can review the account log at the server side to advise what's going on.

Who are you sending event reports to currently?

 

[sparkymarka]

This may a long shot ….as you are using SIA format …does it transmit text description to the ARC ? if so are there any non SIA text in any of the descriptors , I’ve had with panels if you put say a / in , it locks up the communications ( dual com ) …

 

[bubbletea]

First of all, thank you both for your replies.


@GalaxyGuy

I’ve disabled the Heartbeat as you suggested. I had only enabled it recently for testing purposes.

Previously, I was sending SIA reports to a French monitoring company, but to be honest, I wasn’t fully confident in their service.

So I created an account on SelfMon and configured the settings as instructed. I was able to send an immediate test event, and it shows up correctly in the Events tab.

Regarding my network setup: I have an "SFR" router with a DMZ pointing to a Draytek 2865 Series.
If the router loses its connection, it automatically switches over to 4G. I’ve left almost everything at the default settings, except for the “Data Packet Filtering,” which I disabled.

I can attach the full configuration file if needed.


@sparkymarka

So you would recommend sticking with the MicroTech protocol? ChatGPT told me that this protocol was deprecated by most monitoring companies.

But I’ll try to find a new company that still accepts it if it’s the better option.

Also, for the transmission mode, is it preferable to keep it on Single or Dual?


Thanks to both of you!

 

[GalaxyGuy]

Okay, I can see your account.

The 'Dual' setting means the event will be sent to both receivers. This will increase the likelihood of failure. When you set to 'Single' and have a secondary receiver configured with IP and port, then the second is used only when the primary fails. Note that annoyingly, when this happens, you still get the COM4 error.

When using SelfMon, you're better off with the VMOD module, as I designed it not to give the COM4 errors at the panel side - they're extremely annoying especially when the network has an issue at 2am and the horn beeps. The VMOD leaves the line path error reporting to the SelfMon platform, so can be filtered appropriately. I've tried many times to get Honeywell to implement the comm's fail suppression option in the Dimension firmware, like it is on the Flex Grade 2 and Grade 3 panels but the request has been ignored.

 

[bubbletea]

Thank you very much for your assistance.

Do you know if updating the E080-10 firmware to 4.17, or updating the panel firmware to 7.04, resolves this issue? Or is the COM4 error behaviour unchanged with these versions?

 

[GalaxyGuy]

Dimension 7.04 release only had an Ethernet fix for a keypad wrong code tamper issue and 4.17 on Ethernet module was for TLS support. I don't think your issue is firmware related.


7.04 Notes:

Miscellaneous Changes/ Fixes
• Auto set. timer control (option 45.4) timer status ON and OFF fix.
• Hold up alarm when from Duress Pin is not displaying Partition and user details in alarm page.
• Wrong Code Tamper Issue in Galaxy Dimension Ethernet Module.
o Panel firmware fix in combination with E080-10 V4.14

 

[bubbletea]

Thanks for the clarification.
I’ll wait for the full diagnostic through SelfMon, but if the issue is indeed related to how the ARC handles the communication path, I’m wondering whether there are any monitoring providers on the market that follow a design similar to SelfMon.

I’ve already tried four well-known French monitoring companies, and none of them support the MicroTech protocol. Even if I eventually find one, their implementation of the protocol probably won’t be as specific, stable or well-engineered as what SelfMon does.

My requirements are quite strict :

support for MicroTech,

proper handling of communication path errors (without unnecessary COM4 triggers),

physical on-site intervention when needed,

and video verification.


Do you know if it’s realistically possible to find an ARC that meets these criteria, or is this type of issue common with most monitoring centres?

 

[GalaxyGuy]

I think you'd need to fit a third party communicator that the ARC supports. Where the communicator sits on the rs485 bus and then talks to the ARC via the third party. Something like an Emizon or DualCom module. These would normally be installed by an approved alarm company under maintenance and monitoring contract.

 

[bubbletea]

OK, I’ll check on my side.

Regarding the notifications through the GX Remote Control app: I’ve registered for the service and added my phone, but I’m not receiving anything. Is there any specific action required on the panel side?

 

[GalaxyGuy]

Are you talking about the Honeywell service or SelfMon?

 

[bubbletea]

The honeywell service. Does this work with SelfMon too with the Gx Remote Control app?

 

[GalaxyGuy]

When setting up the Honeywell app for push notifications, you need to enter the IP address of their server in your control panel ARC receiver - given by them when you set up the app push email confirmation. Note that they are ending the free push service on Dec 31st, so little point setting that part up.

Since you have configured SelfMon, you can install the SelfMon app. In the app config (gear icon) add your SelfMon account number and one of the 9 character push queue ID's, then save the setting. You will find the push queue ID's in your selfmon account under 'Configuration -> Push queue' menu. You cannot share the ID between devices. You can have both the GX app and SelfMon app installed and use either for connecting to the panel, but only the SelfMon app will receive push from SelfMon.

 

[bubbletea]

When I try to download your app on Android 15 from the Play Store, I get a message saying it was made for an older version of Android.

I can still download and install it using APKPure, but I'm not sure it will work properly.

Does the app push notifications for all events, or only for alarms?

 

[bubbletea]

Okay it seems to be working.