Terms And Conditions Please Read and Accept the Daytona Drone Club Terms to participate in the Forum
All attempts to communicate with the can bus have failed. I have tried 2 different control boards with different cpu. This will be my documented learning on WTF
makes this can bus function and how to set it up.
This is a tool from https://forum.uavcan.org/t/uavcan-gui-tool-v1-0-0/1212, says it's legacy but gonna give it a try to try to get an idea of the bus functionality
https://github.com/UAVCAN/gui_tool
Equiptment so far has been
here3 gps antenna setup (big time fail)
matek m8q gps module ( trying to communicate with this on canbus)
The Kore board made a connection I believe, the pixhawk 4 said no
now to figure out what is says, discovery not possible
This is the response when i connect the here3 gps to can1 on the kore carrier
DEAD! This direction hit a dead end. Next
Here we go. Starting to pick up some pieces
SLCAN (sometimes referred to as LAWICEL protocol) is the protocol you are looking for. There is no formal specification but a reasonably common subset is described here:
https://daytonadrone.com/3954-2/
page16 for SLCAN Protocol
What is UVCAN UAVCAN is an open interoperability standard for off-the-shelf equipment
Designed for complex, high-integrity, real-time vehicular computing systems.
UAVCAN is an open lightweight data bus standard designed for reliable intravehicular communication in aerospace and robotic applications via CAN bus, Ethernet, and other robust transports. The acronym UAVCAN stands for Uncomplicated Application-level Vehicular Computing And Networking.
UAVCAN/UDP and UAVCAN/serial are very new transports that are reviewed in detail in other sources like the PyUAVCAN docs 8 or the post on Alternative transport protocols in UAVCAN. Essentially they all reify the same concepts using the functional means provided by the underlying networking technology. For example, in the case of UAVCAN/UDP, the subjects are modeled as multicast groups, and services are manifested as UDP port numbers, which is optimal because it allows the implementation to offload the network traffic handling to the standard IP stack and the underlying networking hardware.
On of the most interesting things so far is the canbus controlling the ESC, This is a update I will explore. This is a Zubax combination motor/ESC, it is open spec and Zubax has a controller they sell as an item
This has some real potential
https://zubax.com/products/mitochondrik-lv
Not to get off track the purpose of all this brain strain is to figure out about canbus and why my here3 gps isn't working.
here are a couple new images the first my here3 actually
came up after going through the advanced settings again but the information is the same software vers 0
This second image is a new canbus gps from mateksys, I only purchased this for testing the canbus and as you can see it reads the information
I had purchased a usb programmer to update this unit but i might be able to do it through mission planner
http://www.mateksys.com/?portfolio=m8q-can#tab-id-8
Some days God throws me a bone. The update via mission planner worked and now I actually got parameters from the m8q-can gps
it says it's the same version , guess it's just my imagination , but at least it's talking to it, better than the here3