Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Realistic Radio Values #587

Open
JurgenvRooyen opened this issue Mar 10, 2022 · 2 comments
Open

[Feature Request] Realistic Radio Values #587

JurgenvRooyen opened this issue Mar 10, 2022 · 2 comments

Comments

@JurgenvRooyen
Copy link
Collaborator

It would be nice to have the option for DCS to use more realistic values depending on the radio in use. For instance the Tx power for an AN/ARC-182 should be higher (and the Rx sensitivity lower) than the AN/ARC-164.

I think it would be easy enough to pre-calculate the partial Friis (to match the current path loss method), and have a stored list of radios present in flyable modules.

However, I think there is a problem with identifying which specific radio is transmitting. Matching radios based on modulation and frequency isn't suitable due to different radios in the same aircraft covering the same frequencies and modulations. I believe some new field would have to be inserted into UDPVoicePacket class for this to be workable.

@JurgenvRooyen JurgenvRooyen changed the title Feature Request: Realistic Radio Values [Feature Request] Realistic Radio Values Mar 10, 2022
@ciribob
Copy link
Owner

ciribob commented Mar 18, 2022

This was actually something I meant to implement at the beginning of the project - but I struggled to find the relevant information for each radio - settling on the ANARC 164 - as the datasheet was available. https://tsc-60.cellmail.com/tsc-60/TSC-118/rtn_ncs_products_arc164_pdf.pdf

It would be a breaking change of the UDP packet - but something I'm definitely open too. I'd probably send through the partial friis with the packet, or the power of the transmitter. This means that if clients arent in sync it'll still work, as all the information the client needs is in the packet itself

@JurgenvRooyen
Copy link
Collaborator Author

I had a quick mess around at a prototype to test ways implement it over the last week, and to try to source some datasheet or info for Tx power/Rx sensitivity. I ended up with this.

I haven't had the opportunity to test it, but I think it gets across what I imagine it might look like. I ended up thinking its probably possible to allow server owners to specify their own values for radios via a config file, and letting the server communicate custom values (if present) when a client connects similar to how the SyncedServerSettings are resolved.

As for values from datasheets, I was able to find data for about ~1/2 the radios. All the sources are commented in the RadioTypes class, sources that are suspect are labelled as requiring better sources (though I've used the values). If anyone does use these values (or this ends up as a PR), it'd be worth sanity checking the Rx sensitivity values as I'm not 100% the conversions I made were accurate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants