It is plug and play assuming you follow the steps to enable UAVCAN.
No, our products are made and sold from the USA.
The DPS310 is not new and we have switched to is on all of our newer products. It’s specifications are better than the older MS5611 and it is not sensitive to light. It works very well.
One note, I believe only the LED and Compass are supported in the older 3.6.11 Arducopter. You’ll need 4+ to take advantage of the Baro and safety button.
It is ok to use only led and compass. I think it should work plug and play because i already use a UAVCAN compass inside the zubaxx uavcan gps.
If i order from your site is there a way to have it shipped with ups, fedex or similar?
Please confirm you have the board in stock so i can order it.
We use USPS or Fedex to ship to Europe.
Yes, they are instock.
Can i specify fedex at time of order? I do not want usps because it gets stuck in customs forever once it gets to Italy.
You confirm this is the product i need?
https://store.mrobotics.io/ProductDetails.asp?ProductCode=MRO10025
The item is correct and yes, you can choose FedEx.
Thanks, will order tonight!!
Hello, you have done a very good choice with kitcan…with the new rm3100 you will fly as a sharm…ive tested a rm3100 and you will have awesom results, plus the baro on the board you will have a precise measurement…Mro know how make better all of that
Judging by the commentary on the product page, it isn’t immediately clear whether the KitCAN supports a variety of airspeed sensors, or if it is hard-coded to the MS5525.
The following implies that only the MS5525 is supported:
" . . . supports all legacy uBlox GPS sensors and a firmware that supports our MS5525 Airspeed Sensor (via I2C)."
The following instead implies that multiple sensor types are supported, by inclusion of the ARSP_TYPE parameter:
Then access your KitCAN parameters this way via mission planner:
Mission Planner->Initial Setup->Optional Hardware->UAVCAN-> SLCan Mode CAN1 (or 2) -> Parameters
1 min later inside the CAN Parameters change the following:
ARSP_TYPE -> 4
ARSP_USE -> 1
ARSP_BUS -> 0
I’d like to know as I prefer the SDP33 or DLVR on my builds, and it would be a great feature to allow installation of these particular sensors at a distance.
Hi Evan,
The simple answer is
This device runs Ardupilot supported AP_Periph, so any devices supported by the parent project can be supported by the CANNode. Our tutorial relates to a popular product we sell.
Complex answer is
On this board we expose a UART and I2C bus as well for optional devices. So you could also connect a GPS+MAG or i2c airspeed sensor as suggested.
If you have a look at the current airspeed driver, that value can be any on the I2C airspeed sensors:
enum airspeed_type {
TYPE_NONE=0,
TYPE_I2C_MS4525=1,
TYPE_ANALOG=2,
TYPE_I2C_MS5525=3,
TYPE_I2C_MS5525_ADDRESS_1=4,
TYPE_I2C_MS5525_ADDRESS_2=5,
TYPE_I2C_SDP3X=6,
TYPE_I2C_DLVR_5IN=7,
TYPE_UAVCAN=8,
TYPE_I2C_DLVR_10IN=9
One item of note, the DPS310 baro uses I2C device id 0x77, which is also one of the values that the MS5525 can be set to. So you would need to make sure that any I2C devices use a WHOAMI value other than 0x77.
I hope this answers your question, if not let me know.
yes, it supports all the I2C airspeed sensors that ArduPilot supports. It does not yet support the old analog sensors.
I just wanted to compile f103-periph with waf. Unfortunately, waf always stops with the following comment:
don’t build f103-periph, it is a base set of definitions and is not meant to be built. Instead build a derived target like f103-GPS
Thanks a lot - f103GPS build works
So far so good with AP_Periph nodes via Arduino IDE. I have a couple of Sparky V1 F3’s (https://github.com/geosmall/Sparky_FCs_for_Arduino_Core_STM32) I am working toward converting to AP_Periph nodes. The Tau Labs folks were ahead of their time, their Sparky boards are ideal with already built-in CAN transceivers. See CAN pins below:
I also have a few Sparky V2 F405 flight controllers I would like to work to convert to AP_Periph nodes.
How hard would it be create an F405_periph base bootloader? I’m hoping not too hard as they are already supported AP Chibios targets?
yes, very easy. Have a look at the CUAV_GPS, it is a F412 based AP_Periph GPS. Your hwdef.dat and hwdef-bl.dat will be very similar:
Good day, its possible use dual can node board for attach more supported periph?
you can certainly use two CAN nodes. We don’t yet support two CAN interfaces on one CAN node. I do plan to add that, but not done yet.
Knowing that the CANBUS is insensitive to interferences, you really want to know it:
This distance would be impossible with an unshielded I2C bus. With Tridge’s AP_Periph Firmware, CAN BUS and two mRo 103 nodes the connection works fine without any disturbances and only 4 wires between Pixhawk and GPS (including NTRIP data upstream !), compass and airspeed sensor.
Does the f103 have enough power to control ESCs and / or servos too ?
nice test, thanks!
Depends how it is controlling them. If it is just outputting PWM or DShot then yes, I’d expect it would have no trouble, but I’d far prefer to use the f303, especially for DShot, as the DMA on the f103 is a pain.
