When the audio tour isn’t working, there are a few things you should check.
If a Podcatcher isn’t working as it should, we recommend reading this article instead. Most misbehaving Podcatchers can be brought back in line by synchronizing them.
If a Podcatcher seems to not respond to one or more IDentifiers, there’s a few things you can try. First you have to make sure if you hear a beep when pointing the Podcatcher at an IDentifier.
The Podcatcher beeps when pointed at the IDentifier, and either plays the “Invalid IDentifier Stop” content or no content at all:
- 1. Make sure you activate a tour by pointing at a Start IDentifier before testing an Object IDentifier. And make sure the Stop you’re testing with is linked to the correct Tour. Read more about Start IDentifiers here.
- 2. Check if the content is published and synced.
- 3. Check if the code written on the back of the IDentifier matches the one linked in the TourEditor.
- 4. Check if the Stop has audio content.
- 5. Publish any unpublished changes in the Tour.
- 6. Sync the content onto the Podcatchers again to be sure.
If that doesn’t work, it’s possible (though rare) that the code the IDentifier sends out is different from what’s printed on the sticker. You can check this by using the Podcatcher to read the code to you. Here you can read how to do that.
The Podcatcher does not beep when pointed at the IDentifier:
This is usually a sign that the battery in the IDentifier is empty. Try with a few different Podcatchers to confirm that this might be happening (and isn’t just the Podcatcher’s fault), then replace the battery. If that doesn’t work, the IDentifier can be sent for repairs.
We hope to be helpful enough with this Knowledge Base, but it’s entirely possible you have a question that isn’t listed anywhere. Should that happen, contact us. We’ll be glad to help you get back up and running with the system.