Comments (14)
maybe make it togglable? To not constantly monitor serial devices?
from slimevr-server.
oh, i actually want to implement that
from slimevr-server.
How should we identify the tracker?
The serial port itself does not have any standard to identify a device. We don't want to mess with existing serial ports.
I would recommend the following procedure:
- Open a Configuration mode.
- Get all serial ports
- Monitor for new Serial Ports
- Tell the user to connect the trackers
- Handshake,...
The following might to be considered:
- D1 Mini and Most ESP Dev boards use RTS and DTR to Reset or Flash. On some boards they are high on other low. So for DIY the should be able to be changed.
from slimevr-server.
there is a serial command GET INFO
that tracker should reply with info about itself
from slimevr-server.
Well what i wanted to say:
"I'm against sending any Serial Port some characters, without you knowing what it is for."
It can be a old UPS, some other DIY hardware, ...
If we have a other possibility to identify it, like USB native it would be great.
from slimevr-server.
Then we can wait a few seconds until periodical status message.
from slimevr-server.
Improve USB and Serial Interface
from slimevr-server.
Just for clarification, are your ok with this approach?
I would recommend the following procedure:
- Open a Configuration mode.
- Get all serial ports
- Tell the user to connect the trackers
- Monitor for new USB Serial Ports
- Open the new found USB Serial Port
- Wait for a defined String OR send a String (like
GET INFO\n
)
from slimevr-server.
I think that new serial devices should always be monitored and automatically connected. If user is not on the Add new tracker screen, they should get a pop up of sorts.
from slimevr-server.
How often will you connect your tracker to the USB Port to change the configuration?
Once its configured to your network, you will change everything else over the Setting in the Server.
The only reason to connect it to a USB is Charging, WiFi Change, Firmware Update (DIY, not Production)
From looking at the USB Device i have no possibility to know what it is. (i see only a USB to Serial port, with some name)
- If i open it as a serial port, i might reboot a diy 3d printer, or something else.
- If the port is open no other application can access it.
I think the risk of not happy user is too big against the benefit.
from slimevr-server.
That's fair. Let's make it work only on the Add tracker page.
from slimevr-server.
- If i open it as a serial port, i might reboot a diy 3d printer, or something else.
- If the port is open no other application can access it.
That's why I hate cura. That hogs all the com ports and doesn't let go.
My opinion: Exclusive all COMs first -> Make sure that is tracker -> Release the other friends
from slimevr-server.
- Figure out if the connedted device is indeed a SlimeVR tracker
- Make a pop-up that a tracker is connected with suggestion to user to configure it
These two points have been resolved by #312.
from slimevr-server.
@Eirenliel I believe these are all done. Feel free to reopen if not.
from slimevr-server.
Related Issues (20)
- migrate to Okio `Buffer` instead of using `ByteBuffer`
- Android version don't support pico4.
- Acceleration decoding doesn't respect AXES_OFFSET HOT 5
- Don't use neck length when head tracker doesn't have position
- VMC foot bone locations are offset forward
- Disappearance of the lower part of the skeleton when there are only thigh trackers HOT 4
- [Feature Request] Haptic API/OSC/Support
- Stuck on Connecting to the server HOT 13
- Drift compensation should take minutes instead of resets HOT 2
- Add toggle to mirror tracking/VMC HOT 1
- Add option to automatically pause tracking based on HMD/controllers movements
- Support for bend/potentiometer sensors
- Implement combining of multiple tracker types into one for enhanced tracking
- Trackers Over Threshold Visibility for VRChat OSC HOT 2
- Remove slimevr-ui.exe from CI
- Unable to connect a second set of tracker on another PC/Server on the same network. HOT 1
- Closing SlimeVR server closes the browser if it was SlimeVR server that opened the browser HOT 1
- macOS: Java not killed after exiting app HOT 4
- macOS: hid4java incompatible architecture on arm64 HOT 2
- a bug in the recorded BVH file
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from slimevr-server.