Our MP3 system was designed for a specific project. The development system is tested and available but the device package would need to be specified by the customer. The system can take streamed data from any valid source (CAN bus, ANT, BLE) and play an MP3 sample according to the value. The sound can be played direct to a small speaker or connected to an amplifier. The system has been successfully proven and is used to provide audio status updates to the user.
The yellowcog MP3 player can be attached to most of our hardware and here is the help on how to Audio MP3 Properties.
The audio MP3 player uses a small daughterboard to play pre-recorded MP3 files according to the specified stream value. MP3 are played on a loop for as long as the stream value is non-zero and an MP3 is available for the current value.
Bitmapped Value -
- unchecked - the stream value specifies the MP3. Zero is no audio, '1' would play the first MP3, '2' the second etc.
- checked - the stream value is checked to see which is the highest bit set. e.g. decimal 19 is '00010011b' so we can see the highest bit is the fifth, so the fifth MP3 is played
Volume Level - For a connected speaker (with no amplifier) this controls the maximum volume. For systems using the pre-amp output it is arguably best to set this to just less than maximum for compatibility purposes.
Serial Port Properties
This panel is shared by all modules that input or output serial data. Options are:
- Port – almost always to be set as Primary since this is the port wired to the device’s connector. The secondary or higher ports are only available in custom units.
- Baud rate – all standard rates are supported up to 115200. Contact support if other rates are required.
- Bit options – Reserved, currently only “N81” is supported. Contact support for information.
- Frequency – the rate in Hertz that the port will perform an update. An update may or may not result in data being transmitted or processed, depending on the protocols settings.
All modules have this panel. Options are:
- Type – is determined when first adding the module and governs which module properties can be configured.
- Name – used to identify the module in the module list but may also play a part on the embedded device, for example it may be required for it to appear in the outputted data.
- Enable on Pilot – if this is set then this config item will be included and enabled when transferred to the Pilot. If not, then it will still be editable on the PC but will not be used by the Pilot.
- Default Filter – see Streams, Advanced Concepts.
- User Number – This can be used to identify this module elsewhere in the system. For example, by outputting this number whenever the device is connected. In general, it can be left as zero.