Re: Upgraded GEM, now shows errors.
Posted: Sun Aug 06, 2017 10:25 am
Hello Micael,
Would you please confirm the second GEM is set with the same parameters for the packet chunks and similar. There is a thread which I will try to find where Ben states the packet chunks, com flow, and various other parameter should be set to lower, off, etc values.
Could you compare the two GEM's you have on site to one another and match the second GEM to the first incase there is a difference. Also, in the DB Settings-> Admin Settings-> Log Packet Every: Could you change the value to 2 and report back what you observe.
It should also be noted there are a few things happening just in case its not apparent or the same as to what I see.
Different Scenarios:
- I will receive a no packet received email from the DB. But, the system is in fact logging data packets and there is no loss present in the system. You can confirm this by looking at any circuit to see if data gaps are present.
- You will receive a loss of connectivity message from SEG. In this case I've observed the DB has indeed stopped sending packets to third party services / hardware. A reboot is the only method to restore that lost connectivity at this time.
- You see that the DB is displaying an error in the system LED or receive a loss of data packet email. The enable data logging button has been toggled off for what ever reason. The remedy is to re-enable data logging to restore logging.
As an aside I would create a secondary email to send these down events to Ben at Brultech. This would give him more insight as to the frequency and interval of the loss of communications. Please inquire with Ben if this next step is appropriate though.
Lastly, there have been instances where the power supply has been the culprit in random faults. You may want to review the Brultech *General* section as to how to identify if your PSU is one of the faulty units and replace it in case it is.
Would you please confirm the second GEM is set with the same parameters for the packet chunks and similar. There is a thread which I will try to find where Ben states the packet chunks, com flow, and various other parameter should be set to lower, off, etc values.
Could you compare the two GEM's you have on site to one another and match the second GEM to the first incase there is a difference. Also, in the DB Settings-> Admin Settings-> Log Packet Every: Could you change the value to 2 and report back what you observe.
It should also be noted there are a few things happening just in case its not apparent or the same as to what I see.
Different Scenarios:
- I will receive a no packet received email from the DB. But, the system is in fact logging data packets and there is no loss present in the system. You can confirm this by looking at any circuit to see if data gaps are present.
- You will receive a loss of connectivity message from SEG. In this case I've observed the DB has indeed stopped sending packets to third party services / hardware. A reboot is the only method to restore that lost connectivity at this time.
- You see that the DB is displaying an error in the system LED or receive a loss of data packet email. The enable data logging button has been toggled off for what ever reason. The remedy is to re-enable data logging to restore logging.
As an aside I would create a secondary email to send these down events to Ben at Brultech. This would give him more insight as to the frequency and interval of the loss of communications. Please inquire with Ben if this next step is appropriate though.
Lastly, there have been instances where the power supply has been the culprit in random faults. You may want to review the Brultech *General* section as to how to identify if your PSU is one of the faulty units and replace it in case it is.