Radarcape:CapeFinder: Difference between revisions
imported>Beastadmin No edit summary |
No edit summary |
||
(29 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{#seo: | {{#seo: | ||
|title=Find your | |title=Find your Radarcapes with CapeFinder | ||
|titlemode=replace | |titlemode=replace | ||
|keywords=radarcape,capefinder,installation,guide,help,support | |keywords=radarcape,capefinder,installation,guide,help,support | ||
|description=How to find the Radarcape in your local network using | |description=How to find the Radarcape in your local network using CapeFiner | ||
}} | }} | ||
Line 14: | Line 14: | ||
__TOC__ | __TOC__ | ||
== | ==About CapeFinder== | ||
[[File:CapeFinder1.png|300px|thumb|right|CapeFinder on Windows]] | |||
CapeFinder is a small tool for detecting Jetvision Receivers in your local network environment. It shows additional information including IP-Address, Hostname, Software-Version and MAC-Address. You can easily access your Receivers webpage or copy its current IP-Address. See 'features' for more. | |||
Do you have some great ideas or would like to have additional functionality? Feel free to contact me at [email protected]. | |||
==How to use== | |||
Download the latest version and run it. | |||
Hint: You need to allow network access to make CapeFinder able to do its work. | |||
==Features== | |||
CapeFinder automatically detects your network configuration and finds connected Radarcapes. | |||
Standard controls: | |||
* Double click IP-Address: open selected Radarcape in default browser. (via its current IP-Address) | |||
* Double click hostname: does the same but uses the hostname. '''Requires a working DNS-Server'''. | |||
* Ctrl+C: copy selected Radarcapes' IP-Address to clipboard. | |||
* Click column names: sort all entries. Click twice to sort in reverse order. | |||
Advanced controls: | |||
* F5: manually trigger the automatic scanning. | |||
* F6: re-scan local network adapters. Use that if you connect a new adapter during runtime. | |||
* F7: manually check for update | |||
* Double click console message: copy all messages to clipboard. | |||
==Requirements== | |||
* Radarcapes must run on firmware version 161030 or newer. | |||
* Your firewall has to allow CapeFinder network access. Add an exception if necessary. | |||
==Technical Limitations== | |||
Note: If you do not know what this is about you probably can just proceed to downloads. | |||
* Only radarcapes within the same subnets as your PC can be found. | |||
* CapeFinder does not support IPv6 for now. | |||
* All involved network knots have to allow multicast messages. That includes for example Router, WLAN-Repeater, Access-Points, Network-Bridges and VPN-Connections. | |||
==Known Issues== | |||
Opening the device webpage via DNS does not work | |||
* that happens when you do not have an DNS-Server in your network or it does not work properly. Use the IP method instead. | |||
'n/a' or emtpy MAC-Address | |||
* some older software combinations (Linux and RC-Firmware) do not support gathering the MAC yet. This should be gone after updating both. | |||
Uptime or Temperature fields are empty | |||
* some devices or software configurations do not support these two values yet. You could try to update your device. | |||
==Downloads== | |||
[https://jetvision.de/resources/CapeFinder-2.0.0.0-win32.exe CapeFinder 2.0.0.0 - Windows (32bit)] | |||
[https://jetvision.de/resources/CapeFinder-2.0.0.0-win64.exe CapeFinder 2.0.0.0 - Windows (64bit)] | |||
==Changelog== | |||
<b>2.0.0.0</b> | |||
CORE: improved device detection | |||
CORE: support for the new Air!Squitter, check it out on [https://airsquitter.com airsquitter.com] | |||
CORE: support for 'Uptime' and 'Temperature' | |||
GUI: DPI awareness, device counter, auto-width of table and window, remembering of position and sizes | |||
<b>1.0.0.0</b> | |||
initial release |
Latest revision as of 15:31, 12 February 2024
Required computer skills to execute these tasks: Beginner |
About CapeFinder
CapeFinder is a small tool for detecting Jetvision Receivers in your local network environment. It shows additional information including IP-Address, Hostname, Software-Version and MAC-Address. You can easily access your Receivers webpage or copy its current IP-Address. See 'features' for more.
Do you have some great ideas or would like to have additional functionality? Feel free to contact me at [email protected].
How to use
Download the latest version and run it.
Hint: You need to allow network access to make CapeFinder able to do its work.
Features
CapeFinder automatically detects your network configuration and finds connected Radarcapes.
Standard controls:
- Double click IP-Address: open selected Radarcape in default browser. (via its current IP-Address)
- Double click hostname: does the same but uses the hostname. Requires a working DNS-Server.
- Ctrl+C: copy selected Radarcapes' IP-Address to clipboard.
- Click column names: sort all entries. Click twice to sort in reverse order.
Advanced controls:
- F5: manually trigger the automatic scanning.
- F6: re-scan local network adapters. Use that if you connect a new adapter during runtime.
- F7: manually check for update
- Double click console message: copy all messages to clipboard.
Requirements
- Radarcapes must run on firmware version 161030 or newer.
- Your firewall has to allow CapeFinder network access. Add an exception if necessary.
Technical Limitations
Note: If you do not know what this is about you probably can just proceed to downloads.
- Only radarcapes within the same subnets as your PC can be found.
- CapeFinder does not support IPv6 for now.
- All involved network knots have to allow multicast messages. That includes for example Router, WLAN-Repeater, Access-Points, Network-Bridges and VPN-Connections.
Known Issues
Opening the device webpage via DNS does not work
- that happens when you do not have an DNS-Server in your network or it does not work properly. Use the IP method instead.
'n/a' or emtpy MAC-Address
- some older software combinations (Linux and RC-Firmware) do not support gathering the MAC yet. This should be gone after updating both.
Uptime or Temperature fields are empty
- some devices or software configurations do not support these two values yet. You could try to update your device.
Downloads
CapeFinder 2.0.0.0 - Windows (32bit)
CapeFinder 2.0.0.0 - Windows (64bit)
Changelog
2.0.0.0
CORE: improved device detection
CORE: support for the new Air!Squitter, check it out on airsquitter.com
CORE: support for 'Uptime' and 'Temperature'
GUI: DPI awareness, device counter, auto-width of table and window, remembering of position and sizes
1.0.0.0
initial release