- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
This one isn't quite what Andreas had posted earlier, so I thought I'd start another one.
I've had two sites do this now, so it doesn't look like it's an isolated case and it ONLY affects the ComX510 using firmware V2.1.17.
Essentially what is happening is that these two sites are remote sites set for publication (one site is set for hourly and the other 12 hourly).
The communications isn't stable, so sometimes it drops out for a couple of days and then picks up again.
However when the Com'X510 comes back on-line and publishes, it doesn't publish ALL the unpublished data. It ONLY publishes unpublished data for a single day starting from the last published time and then we have to wait for another publication to get another day.
I've got a screenshot of the site publishing hourly, as you can see from the "Date Modified" column, the files are created in January (every hour) as expected. But the time-stamp on the files are back in Dec, when there was a drop out. It's slowly catching up to the current time period.
Again, this is also happening at another site which is publishing 12 hourly, they've just got comms back and they're getting published data back in December as well. A day's worth of data with each publication.
I find this quite strange because the Com'X200 does this correctly, it publishes all the unpublished data when it comes back on-line.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Steven.
Have you submitted through Technical Support? I ask that you please do, so we can properly track the issue.
James
FYI...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Steven.
Have you submitted through Technical Support? I ask that you please do, so we can properly track the issue.
James
FYI...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi James,
Sorry for the delayed response, just got back from holidays.
Yes, the issue was raised back around the 10th of January. Not sure if it has gotten anywhere as my L2 guy has gone on holidays as well.
I'm going to try the new 2.1.18 firmware, hopefully it has been fixed in this.
Regards,
Steven Yan

