mRobotics.io - mRo CAN Node F303 für Ardupilot AP Periph

Ausführliche Informationen und Technische Daten: 

%0amRo AP_Peripheral / CAN Converter / Prototyping module.
%0a
%0a[The product picture denotes the old F103 chip, be assured you will receive the F303 version]
%0a
%0aThe mRo CAN Node has been the product of a collaborative project with Ardupilot, which began with a desire to make CAN peripherals more standard in the drone community. Compared to other boards that have open-source hardware but closed source code, mRo CAN node is completely open. The CAN Node F303 is the second version of our CAN Node, featuring more flash space.
%0a
%0amRo CAN Node uses an open-source code similar to the one written by Andrew Tridge from Ardupilot, which utilizes the existing and proven Ardupilot driver library (currently supporting uBlox GPSs, Barometer, Airspeed, and Magnetometers). It features a CAN bootloader for "over CAN" firmware updates and an RTOS running Chibios.
%0a
%0aSet onboard parameters to a specific CAN Node ID or set to auto-allocated CAN Node IDs (not yet supported in stable Ardupilot). The hardware from this design is free and open-source so that anyone can contribute to the CAN peripheral world with a proven CAN / MCU interface.
%0a
%0aWith this board, you can easily utilize the Ardupilot driver library to convert from UART/I2C/SPI/GPIO to CAN using LibCanard. It is currently set to be plug-and-play as a GPS and Magnetometer by simply plugging in the 6-pin GH connector from any mRo GPS and utilizing it as a CAN-GPS.
%0a
%0a[Quickstart]
%0a
%0aMake sure you are using the latest version of Mission Planner. With the following firmware versions or newer:
%0a
%0aArduPlane >= V4.0.5
%0aArduCopter >= V4.0.3
%0aArduRover >= V4.0.0
%0a
%0aGo to Full Parameter Tree on Mission Planner and verify those are enabled (some firmware versions are enabled by default, others are not).
%0a
%0aCAN_P1_DRIVER -> 1
%0aGPS_TYPE -> 9 UAVCAN
%0a
%0aThen, make sure the UAVCAN compass driver is not disabled (UAVCAN should be unchecked). If your controller has more than 3 internal compasses, you should disable the least important one:
%0a
%0aCOMPASS_TYPEMASK -> UAVCAN (Unchecked).
%0a
%0aConnect your mRo Location One to your controller via CAN and Restart.
%0a
%0aNTF_LED_TYPE -> UAVCAN -> Checked (Only if you want the RGB enabled).
%0a
%0aIf you want to enable the I2C airspeed, on the autopilot/controller parameters via Mission Planner set:
%0a
%0aARSP_TYPE -> 8 UAVCAN
%0a
%0aThen, you must access your mRo Location One CAN parameters and follow these steps:
%0a
%0aMission Planner -> Initial Setup -> Optional Hardware -> UAVCAN -> SLCan Mode CAN1 -> Parameters
%0a
%0a1 min later inside the CAN Parameters, change the following:
%0a
%0aARSP_TYPE -> 1
%0aFor mRo I2C Airspeed Sensor JST-GH MS4525DO
%0a
%0aARSP_TYPE -> 4
%0aFor mRo Next-Gen MS5525 Airspeed Sensor
%0a
%0a
%0aWrite and reboot. Enjoy!
%0a
%0aYou can go to Mission Planner->Initial Setup->Optional Hardware->UAVCAN-> SLCan Mode CAN1 (or 2), and you should see your board alive. From there, you can access the CAN Node parameters and change the default node address among other parameters.
%0a
%0aMCU:
%0aSTM32F303 ARM Microcontroller
%0a
%0aJST GH Plug Connections:
%0aGPS Port (UART and I2C)
%0aI2C Port
%0a2 x CAN Ports
%0a
%0aSolder Pad Connections:
%0a1 x SPI (2 Chip Selects)
%0a2 x ADC lines
%0a3 x GPIO lines
%0a2 x UART
%0a1 x I2C
%0a
%0a$5 from each board sale will be donated to Ardupilot.org.
%0a
%0aSchematic: https://github.com/mRoboticsIO/CANNode/tree/master/Schematic
%0aDesign Files: https://github.com/mRoboticsIO/CANNode/tree/master/Altium
%0a
%0a[Made in USA]