Indeed, I missed the offset. I used 0x0800C000. My apologies.
I used the quick Python program you supplied previously to generate the signature file.
(firmware.bin (222 Bytes))
I’m sorry, how do I go about this?
EDIT: I used Yukon to find: 0x3f001b000b5136313036383800000000
Thanks, Arjun
Okay. I am noticing that now you’re dealing with a different device, because in your original logs posted here you had this:
2024-12-01 23:50:28 0085034 INF yakut.cmd.file_server: Node 125 info: uavcan.node.GetInfo.Response.1.0(protocol_version=uavcan.node.Version.1.0(major=1, minor=0), hardware_version=uavcan.node.Version.1.0(major=1, minor=3), software_version=uavcan.node.Version.1.0(major=0, minor=0), software_vcs_revision_id=0, unique_id=[48, 0,67, 0,10,81,54,49,48,54,56,56, 0, 0, 0, 0], name='com.zubax.telega', software_image_crc=[], certificate_of_authenticity='')
Notice unique_id=[48, 0,67, 0,10,81,54,49,48,54,56,56, 0, 0, 0, 0], which is:
>>> bytes([48, 0,67, 0,10,81,54,49,48,54,56,56, 0, 0, 0, 0]).hex()
'300043000a5136313036383800000000'
And now you have 3f001b000b5136313036383800000000. A different UID requires a different signature. For this UID, the signature is:
d15efee3f628b60de85b1cf1028183fcbc416c42623216b15f8d7e88cd38e3ebd2e45db9c40f9d0a2dd7331977e18e8ecc1a9a7332560fa01127f954435c7fb5c32f9da45663deac8709666aa05f12748ab1fa87960bb6e36750e029b1b86240691cbccdd258b45a60d28326fa0a8c1ee7db5ff7680853d8ffdc9e3776f39599b7d9f1f30fee8320e9d6769199354bfdd257a67b7ec56de7ae501ff0c18a119953a06c94476fe46f9333dcd33577619994e047b992818f2e10d86fcf73583f348b5f885ab61c551a66f5ff5fcaab2adda891c69c36ac4763e86754a967e4
You can store that into a file using the script I shared earlier.
Rejoice!
All motors spin and work properly. Thank you @pavel-kirienko for helping me out here; please excuse my youthful inexperience.
To further tune my multi-rotor (which I hope you’ll let me post here after its successful completion), what are the next steps? I’d like to optimise the setup as much as possible to maximise performance and increase efficiency. I’m using a Turnigy Multstar motor with some 14" props (Getting some EOLO ones soon).
Thanks!
Configure the velocity controller in the ESC (use feedforward terms as explained in the docs), then tune the flight controller.
Good afternoon, we have the following problem: when connecting ESC ZUBAX via CAN bus to FC Cube with Ardupilot, data from the motor is displayed, but there is no possibility to control the motor. Ardupilot Motor test tab is inactive and does not respond to gas from the remote control either. Another question is that we cannot connect to KUCHER via CAN bus. The connection works only via micro-usb. Can you help?
This sounds like a flight controller configuration problem.
Kucher does not support CAN bus.
Please consider switching to Telega v1.0 instead. It has a much better documentation and many improvements to the control loop. There is no support for DroneCAN, but you can use Cyphal with ArduPilot with the help of this script: GitHub - PonomarevDA/cyphal_lua_ardupilot: ArduPilot Cyphal/CAN LUA Driver
And what can the message ‘warning 1’ mean in yellow
I will need more context to answer that
DroneCAN ESCs — Copter documentation
This is all you need @VYAch for it to work. I can attest to that.
Are you using Telega v1.0 or v<1.0? Please send over your Arducopter params file and I’ll help out as best I can.
ghj.param (1.1 KB)
PlaneParam.param (19.1 KB)
There are 2 profiles here, one from the plane, one from the regulator. Please, help
Please update to Telega 0.6. That will remove your warning immediately.
How many ESC’s do you have? I’ll assume that you have 2.
I think you mean “How can Arducopter send the power commands to the ESC through CAN rather than PWM”.
Assuming that you have 2 ESC’s, please try this updated Plane Params (20.0 KB) after updating your Myxa’s to Telega v0.6. This will work. Please refer to the link I previously posted in the unlikely event that it doesn’t.
Thank you, after reflashing the engine started working and is controlled by the stick, but for some reason on channel 4, not 3, while the equipment is calibrated, RSMAP - default for the aircraft throttle on channel 3. Servo output 3 - there is a throttle, what could it be?
Does this mean you want to control the throttle of the motors using RC 3 rather than RC4? Then you might have to change the mode of your Transmitter. I think is a question better answered on the Ardupilot forums. However, as a start, look into changing the mode of your transmitter or, switching the RCIn wires of your receiver (if possible).
From your attached picture, considered changing the 3rd and 4th channels. This may solve your problem (i.e. switch the Throttle and Yaw channels).
I’m not sure I understand. You are using CANBus, no? This means that the PWM instructions are irrelevant in the motor control of CANBus. I believe that the Myxa (after correct motor tuning) will run the motors, from Ardupilot in a ratiometric control. I urge that if people please correct me if I’m wrong.
Thanks!
In real life it looks like this: at the minimum Throttle value, the engine is already rotating at about 10 percent of the speed. It turns out that I need to reconfigure the ESC so that at the minimum Throttle value, the current value does not allow the engine to rotate yet?
I’m not too sure that’s possible. The whole point of arming a drone is for the motors to spin.
If you don’t want the motors to spin, don’t arm the drone? I think this is a better question asked in the Ardupilot forum unless someone else from the Zubax forum here can help answer the question as well, given the helpless nature of Ardupilot devs.
Might I ask if my previous posts to your answers helped at all? Did the plane params help? Did upgrading to Telega help?
Thanks!
Thanks for your help! Updating to version 0.6 helped. The plane has a catapult launch, so it should be armed but with a fixed propeller.
That’s good!
I think you could look here: Setting Motor Range for more infomation. If you are using Arduplane, the concept should still follow through. You just have to lower the MOT_SPIN_ARM to be low enough for the motors to just be under the threshold of spinning when armed. NOTE:This will mean that you will have a deadzone at the bottom of your transmitter throttle.
Good day, after flashing the firmware on TELEGA V1 the LEDs are blinking red and green, does this mean that everything is bad?
