You may have better luck with a .bin file - I see you are trying to read a .tlog file in your screenshot which often doesn’t have some of the data you are looking for.
Where is the data written for live tracking? If I want to see the RPM, does the script pass the data to the Missionplanner RPM plot?
No i don’t think the current script supports that. But can be added if necessary using telemetry logs functions.
This was helpful.
I tried plotting the .bin file and I could see the escs data under the hwes label.
The same was provided in the script in line 213,
logger.write(‘HWES’,‘I,PNum,RPM,Curr,Volt,InT,OutT,PCurr,MosT,CapT,Status’, ‘BHHfffffBBH’, ‘#-qAv–AOO-’, ‘–00000000-’, ofs+i, pnum, RPM, curr, volt, in_thr, out_thr, pcurr, mos_temp, cap_temp, status)
But i think all the escs data are updated in the same variables. So there is no provision for logging each esc data separately with the exisiting code.
I’m planning to make this modification and test it out soon. Rrplace that above line of code with this:
local label = string.format(“HWES%d”, ofs + i)
logger.write(label,
‘I,PNum,RPM,Curr,Volt,InT,OutT,PCurr,MosT,CapT,Status’,
‘BHHfffffBBH’, ‘#-qAv–AOO-’, ‘–00000000-’,
ofs + i, pnum, RPM, curr, volt, in_thr, out_thr, pcurr, mos_temp, cap_temp, status)
Yes there is, each one has a different instance number i.
But in the data log label it is a single parameter which denotes which esc but the voltage, rpm, current and other motor parameters are not unique to the instance I. The parameters of motor 1 2 3…8 are all updated or overwritten in same parameters.
How are you looking at the data?
- Ardupilog in matlab?
- pymavlink?
- MissionPlanner?
- plot.arduilot.org?
- plotjuggler?
There might be some bugs in plot.ardupilot.org.
I suggest you use plotjuggler it has a ardupilot plugin that correctly handles instances in messages.
1 Like
Using plot.ardupilot.org.
Now I’m unable to get what I got initially; nothing related to the HWES is visible in the .bin or .tlog files.
Help. Can anyone help me with the code and the implementation of this whole thing to read and store all telemetry data of esc from Datalink coming in this format?
Previously when viewing the .bin file, the parameters like volt, curre, inT, outT, rpm, temp etc were stored in the HWES dropdown label in plot.ardupilot.org. Now when I tried collecting data, the datalog files/.bin files doesn’t show this dropdown, but the message panel in mission control says ESC_HW: loaded.
Help
Use plotjuggler. That one works like it should And you can save a configuration for later use, unlike plot.ardupilot.org.
So can you guide me step by step?
Install this GitHub - ArduPilot/plotjuggler-apbin-plugins: ArduPilot Dataflash plugin for Plotjuggler
Read:
and
google is your best friend!!!
I also use Hobbywing Datalink v2, 4 motors connected. The script starts, in the mission planner status I see esc items for each motor, its own instance of RPM, temperature, current, etc. But in the .bin logs from the flight controller there are no records about esc (viewed via MP). I wanted to use it for notch filter as esc, so that it provides RPM. But it turns out that it does not give anything to the flight controller and just sends telemetry to mp. How to use Hobbywing Datalink v2 to configure notch filter?
Arducopter 4.5.7
Hobbywing Datalink v2
Motor hobbywing x9
When correctly configured, the Hobbwing Datalink V2 provides RPM data to the notch filters.
You can configure it correctly by using the latest ArduPilot methodic configurator software and using the Hoverit_X13 vehicle template as a starting point. It uses that exact feature.
y did didn’t you connect tx of cube orange to rx1 of datalink v2. as i went through the old hobbywing datalinkv2 datasheet the connection to the flight controller will be done using tx2 and rx2 of the hobbywing datalink v2 .
Communication_Protocol_of_HW_Data_Link.pdf (465.1 KB)
I’m not transmitting any data from cube to datalink.
ok
thank you that was helpful