Previous: Usage
Up: Running it all
Next: Bugs
Previous Page: Usage
Next Page: Bugs
It's difficult to know what to write here, as there are so many interacting
systems. A reasonable procedure is:
- Set up the codec as you think is correct. Type to the ``tip" window. Check that the send and receive data rates are
what you expect, and that the video is looped back correctly.
- Check that the device driver stats are reporting the correct data rate.
- With the codec still looped back, run the codec controller and the
interface. Check that the indicator is flashing.
- Set the , even if it says it's correct.
- By this time you should have and . If you haven't, try pressing . If this
still fails, either the codec is in a strange mode, or you've got a device
driver that doesn't run properly on your machine.
- If you have and , then type
to the ``tip" window. The lights should go red,
as the codec loses sync, but should stabilise green again fairly quickly.
If the don't stabilise, it may be worth pressing .
It's also possibly the machine's overloaded for some reason. If they both
go red and stay red, you should check the codec configuration and data rates
again.
- Set up the codec controller to send and receive from itself. Check
that it's receiving it's own data (ie the light is
green). You should also see looped back video again.
- If you've got this far, the codec controller appears to be functioning
correctly. Set up the codec controller to and the remote site you want to communicate with. It's important to
set the port and ttl before you start sending or receiving, as the
change only takes place at start of transmission/reception. Changing packet
size however can be done at any time.
Previous: Usage
Up: Running it all
Next: Bugs
Previous Page: Usage
Next Page: Bugs