Here is some helpful information for those of you who have been banging your head against the wall in regards to MRSS Feeds not updating properly.
I have asked, as well as others, as to what the method is that the BrightSign Players use to determine when to update a cached image in the MRSS Feed. There have been several responses and theories, but nothing worked, and nothing really concrete from the BrightSign folks. I even have a support ticket in about this, and I still haven't received a response to it.
So I have spent the last few days trying different things, and looking at the server log files for my server, and the files on the SD card on the player.
The key is the “guid” element, as this is what the player uses to name the cached file, and to see if it needs to be replaced. The string in the "guid" element must be unique to the version of a image file. Even if you alter the image every 5 minutes on your server (lets say weather radar image), if the player sees the same "guid" string that is already has a file for in the feed, it will just use the cached copy. Only when the "guid" string is different, and not the same as any other file in the cache on the player, will the player download an updated copy of the image to store in the cache.
If you are publishing your feed with a script that you are writing on your own server, you could use the script to create a SHA1 hash of the file:
If you are publishing by hand, you can do something much easier that will work just as well, using your name or company name, filename, 6 digit date, and 4 digit time:
This is easy to remember, just update the date and time every time you make an update to the MRSS feed file, and the next time the Player checks the Feed, it will see that it needs to update the images.
The “guid” element is usually after the “description” element in each of the “item” trees.
Hopefully this will help some of you out!
Any questions, please let me know, I will try and answer them if I can.