Overview
Makeblock Orion is a main control board upgraded and improved for teaching and entertainment on the basis of Arduino Uno. With powerful driving ability and maximum output power of 36W (3A), it can drive four DC motors simultaneously. Well-designed color system is used with sensor modules perfectly, and eight user-friendly independent RJ25 ports implements circuit connection easily. In addition, it supports most Arduino programming tools (Arduino/ArduBlock), and provides the GUI programming tool (mBlock) upgraded from Scratch and mobile APP to meet the needs of various users.
Technical specifications
Makeblock Orion or mBot on OSX El Capitan. Just like Yosemite, El Capitan requires kext driver signing. How this can be disabled in OSX 10.11 is changed however. To get the drivers to work in El Capitan you need to use the new tool csrutil as follows: Reboot and press CMD+R immediately after hearing the startup sound to boot to Recovery Mode. . The Antelope Audio Windows Thunderbolt™ Driver supports ultra-low latency – down to sub-millisecond round-trip latency including AD/DA. The driver is very efficient and maintains stable playback on busy sessions with lots of channels and effects – the Discrete 8 achieved LLP Rating of 9.30 on the DAW Bench low-latency benchmarks.
● Output voltage: 5V DC
● Input voltage: 6V-12V DC
● Maximum input current: 3A
● Communication mode: UART, I²C,digital I/O, analog input
● Control chip: Atmega 328P
● Dimension: 80 x 60 x 18 mm (L x W x H)
Functional characteristics
● Easy to connect with a variety of sensors, electronic modules, and drive modules
● Support the DC motor, stepper motor, servo driver, and encoder motor driver
● Drive two motors directly
● Supply 5V voltage and 2A current
● Onboard buzzer
● Over-current and over-voltage protection
● Fully compatible with Arduino
● Easy to use RJ25 cable
● Provide specific Arduino library functions in Makeblock to simplify programming
● Support mBlock (upgrade of Scratch 2.0) and applicable to users of all ages
Introduction to ports
Makeblock Orion provides eight RJ25 ports identified by labels of six different colors. Their colors and functions are as follows:
The output voltages of yellow, blue, gray, black, and white ports are constant 5V DC current. These ports are usually connected to modules of 5V supply voltage.
Guide to programming
1. This is an example that show you how to use a program in Arduino IDE to control the Me Sound Sensor.
A) Connect the Makeblock Orion to the computer with Micro-USB cable, and connect the Me Sound Sensor to the port No. 6.
B) Create a new Arduino IDE file and input the following codes into IDE.
C) Upload the program to the Makeblock Orion (Don’t connect the port No. 5 to the electronic module during upload).D) Open the serial monitor, and you can see that the output values increase with the increase of sound.
2. This is an example to show you how to write a program to drive the DC motor in Arduino IDE.
A) Connect the Makeblock Orion to your computer with Micro-USB cable.
B) Connect the Me 130 DC Motor to the Makeblock Orion as follows.
C) Create a new Arduino IDE file and input the following codes into IDE.
D) Upload the program to the Makeblock Orion (Don’t connect the port No. 5 to the electronic module during upload).
E) When it is uploaded successfully, connect with external power supply (6-12V), turn on the switch, and you can see the motor rotating clockwise for 2 seconds, stopping for 2 seconds, rotating counterclockwise for 2 seconds, stopping for 2 seconds, and the operation goes repeatedly.
3. The example uses an mBlock program to control the RGB LED, set it as red, and let it flash for a second and extinguish for a second alternately.
A) Connect the Makeblock Orion to your computer with Micro-USB cable, and connect the Me RGB LED module to the port No. 3.
B) Turn on the mBlock, and create a program for the module as follows.
C) Select a corresponding port in the (“Connect”to“Serial port”) option and make a connection.
D) After they are connected, click the green flag in mBlock. The Makeblock Orion will execute the program, and the red LED will flash.
Schematics
Resource
Getting Driver and Tool Link: https: //www.dropbox.com/s/y8o6u64awxoc10m/Orion%20firmware.rar?dl=0
Description
This driver decodes the solution and field messages of Optimal Ranging's underwater utility surveying product Orion. The driver does not have the capability to command the device. Please use the vendor's tooling to configure the device prior to using it in Qinsy.
Driver Information
Driver | Orion | Interface Type | Serial | Driver Class Type | Terminated |
---|---|---|---|---|---|
UTC Driver | No | Input / Output | Input | Executable | drvQpsTerminated.exe |
Related Systems |
| ||||
Related Pages |
Database Setup
General
The Orion system does not provide a time stamp with the messages. Therefore, the time of arrival is used as the time stamp for the decoded observation.
Because the Orion has a fixed delay between the actual observation and the time at which the message arrives in Qinsy, a fixed latency should be entered for each system that uses the Orion driver.
The latency can be entered in the first page of the 'Edit system' dialog. The latency that should be used is 1.386 seconds.
Pitch Roll Heave Sensor
Use 'Optimal Ranging Orion (R-P)' as driver. The default settings (apart from the port settings and the latency) are correct.
Gyro Compass
Use 'Optimal Ranging Orion' as driver. The default settings (apart from the port settings and the latency) are correct.
This driver will provide the magnetic heading of the Orion.
Multibeam Echosounder
Use 'Optimal Ranging Orion' as driver.
Set the proper latency and port settings and set the 'Max beams per ping' field to '2'. Other than that the default values are correct.
USBL system
The USBL system provides the position of utility detection relative to the Orion. The USBL system can be used to display a projection of the utility in the Navigation display and/or the Profile display.
To create such a setup:
- Make sure that you have configured an Orion object with at least a gyro system.
- Make sure that a Miscellaneous system is added to the system that at least decodes slot 'INV_YAW'
- Create a new object that represents the utility.
- Type: Vessel.
- Use a proper shape that mimics the shape of the utility.
- Add a gyro system to the 'utility' object.
- Use 'System Cloner' for the driver.
- Choose the gyro system on the Orion object as the system to clone.
- Choose the inverted yaw observation of the miscellaneous system (see step 2) as the offset.
- Position the utility object by adding a USBL system to the Orion object:
- Use 'Optimal Ranging Orion' as driver & set the appropriate port settings
- Use the CoG of the Orion as the transducer position
- Use the CoG of the utility object as the USBL target
- Use 'Optimal Ranging Orion' as driver & set the appropriate port settings
Miscellaneous System
Use 'Optimal Ranging Orion' as driver and provide the proper port settings.
All slot ID's as described in the system chapter are available.
Systems
The following systems are decoded by the driver:
Pitch, Roll & Heave
Pitch and roll are decoded from the solution message. There is no heave in the message.
Gyro Compass
Magnetic heading is decoded from the solution message.
Multibeam Echosounder
A multibeam system is decoded from the solution message. This multibeam system consists of two 'beams'. Beam one indicates 'top of utility', beam two 'top of seabed'.
X,Y and Z coordinates of the footprints are calculated from the solution message in the following way:
Beam | X | Y | Z |
---|---|---|---|
1 | -1.0 * offset * cos(cable yaw) | offset * sin(cable yaw) | depth from reference point |
2 | Altimeter |
USBL
A USBL system is decoded from the solution message. This USBL system gives the position of the detected point in the utility relative to the Orion.
X, Y and Z coordinates are calculated in the same way as beam 1 of the multibeamer system.
Miscellaneous system
All fields that are not decoded by one of the aforementioned systems, are available as a miscellaneous observation:
Orion Others Drivers Education
Value | Slot ID |
---|---|
Solution ($IISOL) message | |
Solution status | SOLSTAT |
Solution frequency | FREQ |
AC magnetic field | MAGFIELD |
Offset from reference point | OFFSET |
Offset confidence | OFF_CONF |
Depth confidence | DEP_CONF |
Current | CURRENT |
Current confidence | CUR_CONF |
Current phase | CUR_PHASE |
Yaw of cable from E-Pod | CABLEYAW |
Inverted yaw of cable from E-Pod | INV_YAW |
DC magnetic gradient along sensor pair #1 axis | MGRAD1 |
DC magnetic gradient along sensor pair #2 axis | MGRAD2 |
DC magnetic gradient along sensor pair #3 axis | MGRAD3 |
Pressure | PRESSURE |
Magnetic heading | HEADING |
Field ($IIFLD) message | |
Sensor pair | SNSRPAIR |
Frequency | FLD_FREQ |
AC field for sensor 1X, real part | ACFLD1XR |
AC field for sensor 1X, imaginary part | ACFLD1XI |
AC field for sensor 1Y, real part | ACFLD1YR |
AC field for sensor 1Y, imaginary part | ACFLD1YI |
AC field for sensor 1Z, real part | ACFLD1ZR |
AC field for sensor 1Z, imaginary part | ACFLD1ZI |
AC field for sensor 2X, real part | ACFLD2XR |
AC field for sensor 2X, imaginary part | ACFLD2XI |
AC field for sensor 2Y, real part | ACFLD2YR |
AC field for sensor 2Y, imaginary part | ACFLD2YI |
AC field for sensor 2Z, real part | ACFLD2ZR |
AC field for sensor 2Z, imaginary part | ACFLD2ZI |
DC field for sensor 1, real part | DCFLD1R |
DC field for sensor 1, imaginary part | DCFLD1I |
DC field for sensor 2, real part | DCFLD2R |
DC field for sensor 2, imaginary part | DCFLD2I |