Change Release Notes
ARCx v2026.10.04.01 expands what it means to control a robot from anywhere. Your Browser Just Became Part of the Robot.
This release introduces browser-based microphone and speaker support, adds password protection for ARCx projects, improves audio-device handling, and brings ARCx navigation data closer to established robotics standards.
Your web browser isn't just displaying ARCx anymore.
Now it can become part of the robot.
Use Your Browser as the Robot's Microphone
ARCx can now use the microphone connected to your web browser as an audio input.
That means the computer, tablet, or other device you're using to access ARCx can provide microphone audio directly to the ARCx audio system.
New browser audio controls let you claim the browser microphone when you need it, giving Robot Skills another flexible source of live audio.
This opens up some very interesting possibilities for:
- Remote robot operation
- Speech recognition
- Telepresence
- Remote conversations
- Browser-based control stations
No microphone connected directly to the robot computer?
No problem.
Your Browser Can Be the Speaker Too
It works both ways.
ARCx can now route audio output through the browser you're controlling it from.
That means speech, sounds, and other ARCx audio can be played through the device sitting in front of you instead of requiring speakers connected directly to the robot.
Combined with browser microphone support, ARCx now has another powerful option for creating remote and distributed robot experiences.
Your browser can listen.
Your browser can speak.
And ARCx sits in the middle connecting everything together.
Password-Protected ARCx Projects
ARCx projects can now provide a proper password prompt when working with password-protected project files.
A new password interface handles entering and confirming project passwords while opening or saving projects.
This improves both security and usability while reducing the chance of accidentally entering a different password during confirmation.
Sometimes the robot project contains things you'd rather not leave lying around unlocked.
Now ARCx handles that a little more elegantly.
Navigation Moves Closer to ROS Standards
ARCx's Navigation and Mapping Service continues to evolve.
Pose and scan reporting have been updated to use conventions more closely aligned with ROS and modern robotics software.
Navigation values now use:
- Radians for angles
- Metres for distances
The navigation API has also been updated with clearer terminology such as Yaw, Angle, and Range. Existing members have been marked obsolete where appropriate to help maintain compatibility while Robot Skills transition to the new API.
For developers building navigation, SLAM, lidar, and autonomous movement Robot Skills, this creates a much cleaner foundation for exchanging robotics data.
Faster Navigation Data Handling
The Navigation and Mapping Service has also received improvements to the way it manages incoming scan points and pose updates.
ARCx now handles large amounts of navigation data more efficiently while prioritizing recent information for subscribers.
That's important because navigation sensors can generate a lot of data very quickly.
Your robot doesn't need to know where it was.
It needs to know where it is.
Smarter Audio Device Handling
Audio devices have a tendency to disappear at exactly the wrong time.
Headsets get unplugged.
USB microphones reconnect.
Bluetooth devices wander off.
ARCx now does a better job remembering your preferred input and output devices even when they're temporarily unavailable.
When the hardware comes back, ARCx has a better understanding of which device you actually wanted to use.
Better Speech Synchronization
The audio system now exposes additional information about playback progress and text-to-speech activity.
ARCx can track how much audio has been played and provide additional events around speech output.
This lays the groundwork for better synchronization between a robot's voice and its physical actions.
Imagine coordinating:
speech + mouth movement + gestures + animation + lights
...all from the same audio timeline.
That's where this starts getting interesting.
New Getting Started Documentation
We've also expanded the ARCx documentation with new guides designed to make it easier to get started with the platform and understand how Robot Skills are updated.
As ARCx grows, we're continuing to improve not just what the platform can do, but how quickly someone can go from installing it to making a robot actually do something.
Updated Core Components
Several internal components and dependencies have also been updated, including the SDL3-CS integration and supporting project configuration.
These updates keep ARCx's cross-platform foundation moving forward as more hardware, audio, AI, navigation, and user-interface capabilities are added.
ARCx v2026.10.04.01 is another step toward robots that aren't tied to one computer, one microphone, one speaker, or one way of interacting with the world.
Open ARCx in a browser.
Use that browser's microphone.
Use its speakers.
Control the robot.
And keep building from there.
Download ARCx
Install ARCx on the computer that runs your robot — from a first prototype to a commercial product or an industrial cell. Available for Windows 64-bit, Linux 64-bit and Linux ARM64 for Raspberry Pi (Ubuntu 24.04 LTS 64-bit).
Linux
Ubuntu, Debian & friends
64-bit (x64) (zip)
Raspberry Pi
Single board computers
Linux ARM64 (zip)
Requires Ubuntu 24.04 LTS (64-bit)
ARCx is always evolving. Follow along in the community for updates.
Follow ARCx development Download ARC today
Upgrade to ARC Pro
ARC Pro is your passport to a world of endless possibilities in robot programming, waiting for you to explore.
Here are couple of attempts and the logs:
Interesting - the connection is closing due to a timeout. We wanted to see the log in hopes that it was an ARCx issue. However, that error suggests the Wi-Fi signal is weak, and it disconnected. You mention ARC works, and that's on the same computer with the same wifi configuration?
Lastly, we'd be curious if the ezb camera cable is loose and disconnected?
Anything that you can think of would be useful.
Those are attempts - would you say the first message is the disconnection? Because you mentioned the camera disconnects and won't reconnect, we'd ideally need to see the original disconnect log, not reconnection attempts. Hope that makes sense.
Ok hang on doing one thing at a time.
If I disconnect from ARC and connect to ARCX I have the disconnection issues. The frame freezes and I have to go reboot the EZB most of the time to try the camera again. Once rebooted I connect to camera again and get 45 secs of low frame rate then disconnect. One time the EZB disconnected after the camera stopped.
2 ) I checked the camera cable and it is not loose.
Update: I rebooted my whole network, router etc. based on what you might be suggesting, and reconnected. I now have a camera from ARCX staying on. But the frame rate is very low 4 -11 FPS. It doesn't seemed to do that with ARC. I'll do some more tests today to see if getting closer to the EZB fixes the frame rate. It's weird because I've not had this issue with ARC.
Logs can be viewed in the Debug Log view window.
You can find the framerate in ARC in the Tracking tab
...brought ALAN into the office and now he is 10 feet away vs 40 feet away in the shop. With ARCX I get a steady 14 fps. But I did find this setting and placed it on 0 instead of 200 and now both frame rates match in both ARCS :
Sorry this turned out to be a nothing burger, but I learned quite a few things today!
Hmm that's cool. wonder why that setting exists for the ezb camera? think that should be fixed!!