# FAQs
Q: Does Mac support accessing the webpage for controlling device via USB connection between the computer and the device?
A: Yes.
Q: The playback command doesn’t work.
A: You can take the following steps if the playback command cannot be executed:
- Make sure the interaction between the host computer and the device is correct and functioning properly.
- Check the logs and find the corresponding records related to the response of the playback command, and then take actions accordingly.
Q: Do I need to wait for some time after sending a command?
A: Yes. When you publish a program, it takes time for the device to receive and confirm the command. During this period, delays may occur due to a poor network connection or other issues.
Q: Do I need to wait for some time after the device receives commands related to programs?
A: Yes. The execution of commands related to programs involves downloading files such as media materials and vsn files. If the program contains videos, the wait duration may vary depending on the size of the videos.
Q: Any thing I should pay attention to when creating a new program?
A: You should pay attention to:
- Ensure that vsn files and media material files are named in the format: name_md5_size.
- In the demo, remember to update the URL for downloading files on the device, and make sure to update the responded resources as well.
Q: Is there a maximum limit for storing messages on the device?
A: Yes. You won’t be able to send new messages when the limit is about to be reached. Please remember to clean up the storage regularly.
Q: What should I do if I don’t want to play a program as scheduled?
A: You can modify the time for publishing the program. Accordingly, the “Publish time” and “Update time” of “TerminalProgramDTO” will be changed to the current time.
Q: How can I verify the validity of a command?
A: You can send the command via USB connection (http://192.168.42.129/ (opens new window)) and tell whether this command is correct according to the response.
Q: If you encounter any problems, you can export the device’s logs via LAN for troubleshooting purposes.
A: You can view the logs via this link: http://192.168.42.129/api/logcat.json (opens new window)