I would like to see additional information displayed in the diagnostics screen. Specifically:
GMT Time
Module Height
Mower cut height
Battery percentage
Battery Amps
Battery Volts
WiFi Status
WiFi Signal Strength
DC Satellites
DC CNR
DC GPS Signal Strength
DC RTK Signal Strength
Rover GPS CNR (per receiver)
Rover GPS Signal Strength (per receiver)
Rover RTK signal Strength (per receiver)
…for each receiver
I like the way you think!
Thank you for your suggestion! We’ve passed your idea along to the relevant department for consideration. We appreciate your feedback!
All this is very useful for diagnosing issues.
What about:
I think the general idea would be to expose ANY and ALL sensor information that can lead to an error message on the diagnostics page. That way it’s easy to tell if the condition is cleared.
…and provide an option for a UDP syslog to the IP address of our choice. Might as well include events in that stream (adjusting the blade, track slip, etc), too.
That’ll mean I can spatially map, and make trends for, well, everything.
Add to the list that it would be a nice add I think to have some additional information in the debug screen around the # shared satellites seen by rover and base. This would help with situations where there is GPS dropout quite a bit since shared satellites are necessary for RTK resolution.
ip address or adresses if multiple connections.
And packetloss to halow and wifi gw
Thanks for adding this.
Definitely improvements are needed
For me. We really need some improvements to the diagnostic screen. These are what I’d like are there others?
1. A soft reset of the image processing stack, ie a way to soft reset the cameras (helping resolve the camera sequencing problem)
2. BMS area, ideally I’d like to see charge current and voltage as well as discharge current, Cell Delta (Max/Min), and cycle count
3. Main IMU, show Roll, Pitch, and Yaw, calibration status, update frequency, potentially IMU temp as it can impact measurements
Agreed. Please don’t forget to up vote at the top of the page.
Thanks for taking the time to share these detailed suggestions—they’re very helpful.
I’ll keep an eye on this thread, and if more users express similar needs, I’ll help consolidate the feedback and pass it along to our product team for consideration.