|Home All DIY Kits All Expansion Boards Accessories Web Store OEM/ODM Contact|
|X300 EXPANSION BOARD|
1 x X300 expansion board
1 x USB adapter
1 x 2.4GHz WIFI antenna
4 x nylon spacers (M3 x 20mm)
8 x nylon screws (M3 x 6mm)
|QUICK START GUIDE|
|A. FITTING THE EXPANSION BOARD|
|B. OPERATION SYSTEM|
|C. POWER SUPPLY|
Xseries expansion board supplies the RPi with a regulated +5V through the GPIO header using a 2A poly-resettable (PTC) fuse. With the wide voltage input range (6~18vdc), the RPi can be powered from a wide variety of external sources such as batteries, 12V power adapters, solar battery sources, etc.
Recommended Power Adapter : 110~240VAC input, 12VDC 2A output
Dimension of input plug (Unit: mm)
Warning: do not connect a +5V supply through the Raspberry Pi micro-USB connector when used with this expansion board.
|D. MICROPHONE INPUT AND AUDIO OUTPUT|
To configure X300 sound card as the default audio device.
<1> Right-click the volume icon, a pop-up menu appears to allow you to select "USB PnP Sound Device".
<2> Click "Device Settings..." to allow more detailed control of the X300 audio devices – you can access this either under Device Settings from the volume right-click menu or from the Preferences section of the main menu, where it is listed as Audio Device Settings.
<3> From this dialog, select the device you want to control from the drop-down at the top, and then press the Select Controls button to choose which of the controls the device offers that you want to display. Pressing the Make Default button on this window has the same effect as choosing an output source in the volume right-click menu.
<4> Let's record the sound with LXterminal
<5> Press Ctrl + C to abort recording
<6> Playback the recording with aplay
|E. AUDIO INPUT AND OUTPUT INTERFACE|
|F. SETTING RTC TIME|
This page details how to setup the RTC Pi on the Raspbian Jessie image from http://www.raspberrypi.org/downloads
<7> Ensure that the CR2032 coin battery was inserted into the battery holder. Using the expansion board without a battery installed may damage the RTC chip and will stop it from appearing on the I2C bus.
<8> Follow the instructions on how to install and configure I2C on Raspbian Linux.
<9> Once you have installed I2C check that the RTC Pi has been detected using:
The RTC Pi should appear on channel 68 as shown in the screen shot below. If the RTC Pi does not appear check that the battery is installed correctly and is fully charged:
<10> Enable I2C by running:
Find the I2C line where the I2c is black listed
Comment it out by replacing it with the line below
<11> To ensure that the necessary kernel modules are loaded at boot, ensure your /boot/config.txt file has the entry below …
<12> Save your changes by pressing Ctrl-x then Y
<13> Edit /lib/udev/hwclock-set with
<14> Locate the lines and edit
<15> Comment following three lines in config.txt by adding '#' located at start of the line. (check Images below)
<16> Save your changes by pressing Ctrl-x then Y
<17> Reboot your Raspberry Pi
<18> Get the right time set on the Pi ,
<19> Write the system time to the expansion board,
<20> Verify the time ,
If everything worked correctly the expansion board should be initialised on boot and the current date and time will be loaded into Linux.
|G. TESTING THE IR RECEIVER|
<21> Installing LIRC
<22> Add the two lines below to /etc/modules . This will start the modules up on boot. Pin 8 bellow will be used to take the output from the IR sensor.
<23> Save your changes by pressing Ctrl-x then Y
<24> Edit your
<25> Edit /etc/lirc/hardware.conf and have it appear exactly as shown below.
# /etc/lirc/hardware.conf # # Arguments which will be used when launching lircd LIRCD_ARGS="--uinput" # Don't start lircmd even if there seems to be a good config file # START_LIRCMD=false # Don't start irexec, even if a good config file seems to exist. # START_IREXEC=false # Try to load appropriate kernel modules LOAD_MODULES=true # Run "lircd --driver=help" for a list of supported drivers. DRIVER="default" # usually /dev/lirc0 is the correct setting for systems using udev DEVICE="/dev/lirc0" MODULES="lirc_rpi" # Default configuration files for your hardware if any LIRCD_CONF="" LIRCMD_CONF=""
The highlighted text are the parts that will need changing, though it’s worth checking the rest of the text incase you have a different initial configuration.
<26> Save your changes by pressing Ctrl-x then Y
<27> Reboot the Raspberry Pi
<28> Run these two commands to stop lircd and start outputting raw data from the IR receiver
<29> Point a remote control at your IR receiver and press some buttons. You should see something like this:
|H. SATA PORT|
The SATA port allows you to connect SATA devices to your Raspberry Pi, a very useful tool for data transfer, backup and cloning. It supports most SATA devices such as CD ROM, DVD ROM, CD drive, 2.5 inch hard disk and 3.5 inch hard disk.
Installation for SATA drives:
1. Connect you SATA drive to the SATA port with a SATA cable.
2. Connect SATA Power Cable to a power adapter which is used to power hard disk OR to the power connector on X300 (Output voltage of power adapter used must be 12Vdc).
|I. BLUETOOTH SERIAL COMMUNICATION|
BC04-B Technical specification BC04-B_AT Command
Required additional hardware
A computer or device with a Bluetooth terminal softwareTo establish a communication with the Raspberry Pi over Bluetooth you need another device that can speak Bluetooth. If your computer has a Bluetooth adapter then you just need to find a terminal software that you can use to send and receive data, like HyperTerminal on Windows, or
Raspberry Pi configuration
I'm going to assume you are running a recent release of Raspbian on your Raspberry Pi. If you are running another OS then you will need to find out how the changes below are done in your system.
By default the Raspberry Pi is configured to write boot time messages to the serial port, and also to start a login console on it. Unfortunately, the default baud rate that the RPi uses for its serial port is 115200 bps, while the Bluetooth module comes preconfigured to 9600 bps. There are two config files that need to be updated.
Additional setting for Raspberry Pi 3 only (Not suitable for Raspberry Pi 2 and Pi Model B+)
If you've tried to use the UART on the GPIO header of the new Raspberry Pi 3, you may have been frustrated to discover that it doesn't work properly. until we get an official 'proper' fix (possibly setting PLLs correctly or dynamically with any changes to the core frequency), the best option seems to be setting the core clock to 250MHz, with core_freq=250 in /boot/config.txt.
Add the line core_freq=250 , Save and reboot!
With those changes made the RPi is configured to talk to the Bluetooth module. If you now power up your Raspberry Pi you will notice that the LED in the Bluetooth module blinks rapidly. This is the sign that the Bluetooth module is ready and waiting to be paired with another device.
Connecting from a Bluetooth terminalNow leave the RPi running with the Bluetooth module in its blinking state and go to the Bluetooth enabled computer or smartphone that you will connect to it. Your device should now find the Bluetooth module with the name
If you are using an Android device with BlueTerm then start the app and from the app menu select "Connect device". Android does the baud selection automatically so you don't have to configure it. From a terminal software running in a computer it is likely that you will need to configure the speed, number of data bits per character, parity, and number of stop bits per character. The values you need to use are:
The Bluetooth module
comes preconfigured with a PIN number. To complete the connection
your computer or smartphone will ask you to enter this PIN. The
factory default PIN is
The LED in the Bluetooth module will now stop blinking and remain lit, indicating that it has made a connection.
And here comes the fun part. You need to reboot the Raspberry Pi so that the new serial port settings take effect. To reboot the RPi run the following command in a local or network shell:
Now watch the Bluetooth terminal on your PC or smartphone while the Pi reboots. Boot messages should be appearing on your terminal, and as soon as the RPi is up you should get a login prompt there as well.
You can now login from your Bluetooth terminal and use the command line prompt as you normally would over a local or network shell.
Configuring the Bluetooth module
Firstly you will need to install
The Bluetooth module comes preconfigured from the factory with a set of defaults, which are:
These special commands that configure the Bluetooth module can be sent from a connected remote device, or they can be sent from the local system, in this case the Raspberry Pi. Since the Raspberry Pi is the star of the article I'm going to also use it to do the configuration.
Here is a quick summary of the most useful configuration commands:
One tricky aspect of sending these commands is that the Bluetooth module has a very short timeout, so all the characters in a command must be entered really quickly. The safest way to get the entire command in time is to type it in a text editor window and then use copy/paste to send it really fast.
To send the commands we can use
Note that it isn't necessary to have a connection to do this, so you can do this while the Bluetooth module is in its blinking state.
You now need to use any method to get the string
When you send
If you get this response then you know that everything is all right. If you don't get a response then for some reason the Raspberry Pi is unable to communicate with the Bluetooth module.
When I send
To change the baud rate to the fastest rate of 115200 we need to issue the command
Because the baud rate was changed now the communication will break, and we will need to exit and restart minicom with the updated speed:
change the name of the module to MyBT we must issue the command
And to change the PIN to 4321 the command is
Note that when the name and/or the PIN change the module requires a power cycle for the changes to take effect.
Also don't forget that if you change the baud rate and later want to reestablish the serial console you will need to change the two config files to reflect the new baud rate you have selected in the Bluetooth module.
SALES AND AGENT
All Rights Reserved.