Ah… An errata that affects all full carrier boards shipped before July 2019 is that CAN1 and 2 are mislabeled.
swap CAN ports.
CAN2 is the one to use.
Right, I am aware of the reversal in ports. Can2 is the port I used
It took me several tries and reboots to get slcan to connect. Then it all worked
You are using latest master on ardupilot yes?
Ctrl-Q on mission planner in the firmware page, 3.7 etc
Yes
An Update for these instructions - this is for updating the firmware part only
- Make sure you have Mission Planner 1.3.64, and the Here2 plugged into port labeled CAN2
- Connect in Mission Planner as normal via USB to the cube
- Goto Intital Setup
- Optional Hardware
- UAVCAN
- Click SLCAN Mode CAN1 (this is labeled as Can2 on the carrier board)
- a device should appear in the list, click update
- Mission Planner will download and install the latest CAN firmware for you.
- once updated switch to any other screen
- connect as normal in Mission planner again and config the parameters as listed above
1 Like
On the Mini Carrier Board CAN port is labeled as CAN2, would the GPS work also there, after updating the firmware with a standard full carrier board?
Followed the steps but doesnt show the device.
Using Mission Planner 1.3.64
Arducopter 1.3.7(from Ctrl-Q option on firmware page in MP)
Internal switch in Here2 set to CAN and Cable changed
Connected to CAN2 port on the Carrier Board ( Aware of the reversal)
Am I missing anything?
Same probleme here. After pressing button SLCan Mode Can1 nothing appears. Maybe it has todo with the Windows 10 driver. Changed driver from Microsoft STM to The Cube F4 FMU (or is BL he right one?) but without result…
1 Like
If you install mission planner from the MSI it will install all drivers.
Can you film the process? If we are missing a step in our instructions, this may help
I’ve recorded the steps:
It’s flashing Arducopter 3.7 firmware and then trying to update on SLCAN.
To skip firmware flashing go to 3:22
Also attaching pictures of the setup and Here2 switch position.
I have again followed all procedures and changed between can1 and can2 with all appropriate parameter changes and the Here2 will not communicate with mission planner slcan. It appears to me to an issue directly related to the here unit, if I change nothing but swap gps units with a Zubax GNSS it communicates perfectly. That being said, the Here will communicate with the Zubax Babel and UAVCAN GUI
I have tried all combinations multiple times with no results. Have tried with standard protocol at least a dozen times if not more. I have about four hours in this at this point and am no expert but certainly not a stranger to UAVCAN as I have been using can devices for several years and gone through many changes.
Thanks for your help,
Cheers, RB
Update on this. The Here only connects with Babel/UAVCAN GUI it will not fetch configuration data
Has anyone had success with the external barometer? I have the GPS and compass working as expected but can’t seem to pick up the external barometer. If I use a Zubax GNSS 2 the barometer is detected and becomes the primary baro (BARO1). Also minor point but it doesn’t seem to be reporting HDOP. (Running Pixhawk 2.1, Mission Planner 1.3.64, Arducopter 3.7.0).
Cheers
Jason
The only thing I did differently was I didn’t like that it loaded generic fmuv3 version of firmware. So I downloaded firmware from from ardupilot firmware page in cube folder and installed it before I tried. Mine took a few tries but it did work
Update2. Finally had success by wiping the firmware on the cube and starting from scratch with latest master. I connected mission planner and set the can parameters then opened the slcan dialog and it connected first shot. Loaded the here firmware, rebooted and all worked as expected except that as jasclarke308 reported HDOP is not reported in telemetry stream
Cheers, RB
2 Likes
Awesome!
did you save a parameter set from when it was not working? so you could compare to see what was blocking it?
Steps to get it to work (same as @rbachtell)
Loaded firmware by downloading it from ardupilot site (copter/latest)
http://firmware.ardupilot.org/Copter/latest/CubeBlack/
Changed the following parameters:
Reboot and then followed update steps as posted by @Michael_Oborne
1 Like