Note that as long as you have that file on your Mac – say, in your Downloads folder – it doesn't matter if the Mac launched Archive Utility, and then refused to process the file any further.
I can think of at least one good reason why a Mac might try to process a downloaded file with a .bin extension. A Mac file can contain both a data fork and a resource fork. In the old days before Mac OS X, failing to preserve the resource fork was a sure way to destroy any application sent through a non-Mac system. So people came up with archive-like schemes, including one called MacBinary, to encode the data and resource forks into a single file that would survive transmission. Safari may have "thought" that a file with a ".bin" extension could be a MacBinary file that it could have Archive Utility helpfully unpack for you.
In this case, since the ".bin" file was meant for your camera, your Mac didn't recognize its format. But again – as long as the Mac didn't delete the file, you're still good to go.