If there's only /tf_static available, it seems that all tf_update dependant widgets will stop rendering unless view_update is sent.

Conceptually visualizers with timestamped data that only need to get the single TF frame at their specific timestamp when they're received don't need to be re-rendered on tf updates anyway, so they should all be switched to updating only when there's new data available or the screen moves. Should be faster too, anyway.

The system for figuring out which tiles should be rendered on screen has some offset issues when moving away from the origin, not rendering all tiles in some cases.

Hello @MoffKalast

Vizanti has been a great tool for the project I'm working on. I have setup the layout the way I want with the widgets I need, but if I open Vizanti on a new browser, the layout goes back to the default one and I have to load my layout file or re-add the widgets.

How can I change the Default Layout to the one I want to use, so it loads automatically the widgets I want when I'm on a new browser?

Here's the layout I'm using now:
robot_config.json

~/ros2_ws/src/vizanti/vizanti_server/vizanti_server# ros2 launch vizanti_server vizanti_server.launch.py
[vizanti_flask_node]: Public directory set as ../public

~# ros2 launch vizanti_server vizanti_server.launch.py
[vizanti_flask_node]: Public directory set as /root/ros2_ws/install/vizanti_server/share/vizanti_server/public/

A possible solution:

from pathlib import Path
def get_public_dir():
    p = Path(__file__).resolve()
    path = p.parents[1] / 'public'
    if path.exists():
        return path #for --symlink-install
    return get_package_share_directory('vizanti_server')+ '/public/'

Currently TF transforms are treated as latest-is-correct for rendering visualizers since only one set of values is cached, but this while easy to implement is not quite correct, especially for delayed laserscans which can then be rotationally out of sync.

The idea is to instead keep a short history of received transforms and their timestamps, then recreating one that matches by interpolating between the two nearest entries.

The ROS 2 node manager should support interacting with the supposed life cycle architecture.

I.e. executing these sort of subprocess commands by proxy:

ros2 lifecycle set /nodename cleanup

ros2 lifecycle set /nodename shutdown

ros2 lifecycle set /nodename destroy

Hi, thanks for the great work!
I would like to use Vizanti under some subfolder like this: http://<host_ip>/vizanti
Possible adding a base URL option or use relative URLs?

Currently all TFs are stored perpetually in the consolidation node, which probably isn't best in cases like node restarts where the graph changes and frames should be cleared. Something like 10 seconds should be a good timeout for non-static frames.

Does this support ROS 2?

Add decay time and adjustable setting for:

• range
• marker array
• laser scan
• point cloud

As discussed in #65 (comment), it would be interesting to have extra display modes for map and distance data.

When adding a new widget or configuring an existing widget in Safari on iOS, tapping on the background to close the setup modals does not work. The only way to get back to the default view is to reload the page, restart the web app or to remove the widget.

Tested under iOS 16.5.1 on an iPhone and iPad.

While the static serve and rosbridge ports are technically adjustable in the launch files, the client side rosbridge port stays hardcoded to 5001. We should instead set the port number when serving HTML templates somehow, so it matches the one where rosbridge is actually running.

• humble (Merged in #58 )
• noetic

Please enhance the code to display the camera images on web view

The Grid widget can only show grids in the fixed frame right now due to some rendering limitations.

Hi,
we use Vizanti alongside RTABMAP. The map is published on topic /rtabmap/map. The map is not published regularly, but can be triggered with the service. In rviz the map is shown, but it is not in vizanti. Costmaps work perfectly normal. It's strange, because the issue occured about 2-3 weeks ago, when from day to day it stopped working. TFs and other topics are correct, but map is not seen. Do you have any idea what we should change to diagnose what's wrong and how to repair it?

The covariance renderer currently only works properly for circular values, needs to be cross-referenced with the rviz implementation and rewritten:

The tile zoom is set to 19 (max for OSM) by default and would need an input box to set it to anything else.

TODO widgets:

For rviz parity:

• laserscan
• pointcloud 2
• marker (single)
• polygon
• point stamped
• axes
• grid cells?

Other:

• nav2_msgs/msg/ParticleCloud as an additional type for PoseArray, ROS2 only
• string chat
• configurable dial for all numerical types like byte, char, float32, float64, int16, int32, int64, int8, uint16, etc.
• visualizer for odometry ?
• inspecting/publishing to arbitrary topics

Right now they're rendered in the latest known position of the frame, since browser time and ros time aren't synced anyway, but it could at least render them based on time received.

Apparently Apple's ATS blocks fetch and XHR requests over HTTP, which is a bit of a problem if you're working offline without a way to access a root certificate authority. For macOS a known workaround is to modify the Info.plist file to add an exception.

The workaround for iOS mobile devices is something like this: create a self signed SSL cert, reconfigure rosbridge and the flask server to use it, get the key onto the device and install it, set the cert as a trusted root authority. Repeat every time the cert expires.

Hi, guys,

I've been exploring vizanti as a consolidated web interface for my aerial and ground platforms.

I've been having trouble running SITL instances behind a proxy on my cloud server using the ros2-feature branch.
The best I could get so far is a screen with background colors, but nothing else. It looks like I can reach the base html but none of the js stuff is reachable, maybe?

So far, I've tried to use all sorts of values for base_url to try and fix this with no success. I'm wondering if I there might a need to set the js files paths (although I thought that's what url_for did).

Any ideas would be super welcome, I'm at a loss now

Thanks!

Continuation of the discussion started here.
Short description: cost map rendering is broken and not consistent when using RWS or Rosbridge. Coloured costmap renders ok when using RWS but not ok when using Rosbridge, and vice versa.

Top image - RWS, bottom - Rosbridge:

Chrome 122.0.6261.94 (Mac), Non-Coloured

Firefox 123.0 (Ubuntu), Non-Coloured

Firefox 123.0 (Ubuntu), Coloured

Here is the bag I've recorded, I tried to strip non-relevant topics and keep it short to decrease size. I noticed that the robot model is stuck when playing from the bag, but it's consistent between RWS and Rosbridge.

Download rec.bag.7z from Google Drive (123 MB, too large for Github attachment)

Current transport for CompressedImage messages goes through rosbridge, which does not allow for much throughput before TCP socket congestion occurs.

Ideally this should be switched to aiortc for compact webrtc h264 streaming, given that browser support is solid now, or alternatively the web_video_server for slightly faster MJPEG streaming which would still be slow, but probably wouldn't affect other visualizers nearly as much as the current implementation.

#8 (comment)_

Some files are not installed.
Should install all Python scripts, public folder, and launch files.
The server.py is using ../public folder, so its install destination would need to consider this.

Thank you!

Hi,

last time I encontered an issue. I launched some nodes right after booting the system, and they are perfectly fine to set parameters

imu presented above is only one if few examples.

But there are some nodes which are launched after startup by user and they are not able to load parameters

I don't know if I am doing something wrong, but some parameters are not loading and they are important for me. I can changed them with classic ros2 param set but I would prefer to do it through gui. I will be grateful for every hint for fixing this.

Hi, @MoffKalast,

I've playing some more with Vizanti. It's working very well for me!
One thing I've been trying to understand, though. It seems to me the satellite tiles rotation is inverted.

I've been digging to see if I had something weird going with my TFs,, but I'm pretty sure they are correct at this point.
Can you point me to how I would go about inverting the tile rotation?

Thanks!

This is an amazing work, bundle of thanks to the contributers.
Recently I faced an issue and I want to bring it to your attention.

Remote device is running a ros1 system in a virtual network and the intention is to monitor it remotely.

vizanti fails to get the tf data from the remote device and resultantly all tf related topics fail to get subscribed.

BUT

If the vizanti server is launched via ssh then all works fine.