IA-02-3D Deployment: Inverse Architecture Guide | Marvelmind

Installation & Setup

IA-02-3D Deployment: Inverse Architecture Guide | Marvelmind

▶ 10:45
📅 2019-12-21

🔗 Watch on YouTube

For more information, please contact: info@marvelmind.com

Inverse Architecture Configuration: Overview

This comprehensive deployment tutorial walks through setting up Marvelmind's IA-02-3D Starter Set for precise indoor positioning. Learn the key differences between Inverse Architecture (IA) and standard configurations, understand ultrasonic frequency requirements tied to hardware, execute software updates, apply default settings, and master beacon placement methodology. The guide covers manual distance entry procedures for non-Super-Beacon configurations essential for accurate 3D indoor GPS performance.

Transcript

This comprehensive deployment tutorial walks through setting up Marvelmind's IA-02-3D Starter Set for precise indoor positioning. Learn the key differences between Inverse Architecture (IA) and standard configurations, understand ultrasonic frequency requirements tied to hardware, execute software updates, apply default settings, and master beacon placement methodology. The guide covers manual distance entry procedures for non-Super-Beacon configurations essential for accurate 3D indoor GPS performance.

0:00 Hello colleagues. Today we'll be talking about starter set IA 0-3D. So the most important element of an IA architecture to remember and to make it work well is that each of the stationary beacons, they have different ultrasonic frequencies. So in NIA architecture, all the beacons put on the working the same ultrasonic frequency, usually 31 kilohertz. On IA it's opposite: each of them, at least in one submap, must have a different ultrasonic frequency. And out of this is the most important element you need to remember in order not to make a mistake. So if you have a stationary beacon, look at their white label and you will see their frequency. And this frequency is what these sensors can transmit naturally.

0:57 Don't try to make the frequency of this transmitting leaking ultrasonic transmitting beacon. In IA, stationary beacons are transmitting ultrasonic. Don't try to make it inside the dashboard different from their nominal frequency. So if you have, like in my case, 46 kilohertz, okay, I name it available 36 charges. So this was a mistake. I must use 45, 46, 45 is the same band, so I must use 45 kilohertz settings inside the dashboard. So 31 was a mistake in this case. So you need to check each of them and use their the right settings inside the dashboard. Otherwise, the installation of IA is absolutely the same as usual. So the key elements are: update the software for each of their element.

1:57 All stationary beacons, mobile beacon, modem, and the dashboard. Take the software from the software pack. Don't mix up the software. Always use the software only from the same software pack and update the software for each element. This is first. Second, during the update, don't forget to press the default button inside the dashboard so that in the beginning you will have only default settings for each of the element. And the modem as well. You will basically save time because, again, who knows what the settings were before that. So as soon as we have these basics, you will be able to place the beacons inside your room or office or warehouse, wherever you are testing it. Since in IA 0.2, 0.2 is...

2:56 Using the beacons Beacon HW v4.9, they are not able to talk to each other because they use different ultrasonic frequencies. So it means that you must measure the distance between them and enter manually inside their table of distances between all of the beacons, all of the station. Because by this time, a mobile beacon must be activated as well. So as soon as you enter all the distances, you must press their freeze button on the submap view and you freeze this submap. Since this is the basic setup consisting only of one submap, you need to go to their map view and freeze the map. So soon as you freeze both submaps and maps, and before that you populated their...

3:54 Table of distances with their distance between each of the beacons. The system will work. And in five seconds after that, if you start moving the mobile beacon about the beacon, the mobile beacon will track and you will see their tracking inside the dashboard. Usual limitations are the same for all the systems. So the maximum distance between each of their stationary beacons and mobile beacons is less than 30. It must be less than 30 meters because it's defined and limited by ultrasonic signal. Distances between the modem and each of the beacons is limited by radio. And if you have the short antenna, so it's limited antenna. So usually it's around 100 meters. But if you have a full-size larger antenna, so the distance between the modem and the beacons...

4:53 Station beacons, maybe up to 400 meters. But since the Mini-RX has a small tiny actually embedded antenna, usually this distance, even where their full-size antenna on the modem would be, is limited to 100 meters or less if it's open space. If you're talking about their distance through the walls, it totally depends on the walls. If it's really heavy thick, whatever concrete walls or metal walls, it could be really really limited or even nothing. So we are talking about the open space distances. So let me highlight once again: update the software from the same software pack only for each of the elements. Don't forget about their pressing the default buttons. And particularly for IA, remember to use the right frequencies for ultrasonic corresponding to the hardware of each of the beacons. Don't try to make the...

5:52 Ultrasonic frequencies different from their frequencies of the sensors because they are defined by the hardware. You cannot change them, even throw inside the dashboard. You can choose whatever. So as soon as you do it, you have a perfect IA tracking. Another element, of course, which is also valid to all of the systems, is abstraction. So in order to track, these stationary beacons must be visible. Direct line of sight between the stationary beacons and the mobile beacons. Think about these stationary beacons as your satellite. If you don't see the satellite, at least three satellites for 3D, your system will not work. And if you deploy in the 3D system and before you've seen it, but for example during their, you know, progress of testing or operations, this becomes blocked, the system will not work. Once again, it will be not less precise. It will be simply not working at all...

6:52 Because these two satellites won't be seen. At least three must be visible. So this is why the starter set consists of four beacons. So it's three plus one redundant. If one is blocked, the system will try to still recover. And the majority of cases will be able to recover and still track it in 3D. If this one is blocked, OK, still these three will be used to track their mobile data. But if two of them are blocked, then that's it. No. So you don't have enough beacons. By the way, many people asking which is possible to track outside. Yes, it's possible. It does not suit to be within this rectangle. Now it can go up to this. But remember another element inside the submap. It's called so-called limitation of distance. So it's somewhere here inside the settings. And what is saying, it's basically saying how large the submap is. What is the limitation of distance? It means that what is the maximum distance between the first stationary beacon and...

7:50 The mobile beacon. So it may be that if you go outside this, why they usually recommend that this is 6 by 10 meters, and you're driving inside, just in order to avoid basics like limitation of distance or using non-standard update rate or something, it's default in the beginning. So nevertheless, you're going, going, going, going, going, going out. And at some point of time, you will see taking place, taking place and no tracking at all. So you are moving, but there is no tracking. So most probably you simply hit the limitation of distance. So I think by default is like 30 meters. So this, while usually you are not hitting, but if you don't use default settings, so they may be like 10 meters. So it means that there will be no tracking beyond the 10 meters from the stationary beacons, simply not. So you use a default or increase to whatever distance you wish to increase. But also remember, if you have their larger limitation of...

8:49 Distance, so their travel time, the sound travel time will be more, so that rate will be lower. So there is always a trade-off: largest map, lower update rate. It's well, it's not only for IA, but for any kind of nonlinear circuit texturing, rest 2D, 3D. Does matter. So all this about submaps and limitation distance is the same requirement. What I didn't mention, by the way, during their installation, even though it's 3D, you must enter the height for the stationary beacons because the system is not able to calculate the height for the stationary beacons. You'll be able to calculate the height of the mobile beacon, of course, against them, but not for the stationary beacons. So this is why when you install the system, you must enter those heights. Formally speaking, but if you install according to our requirements, and usually our recommendation is told on the same height, if you solve the same height, issue of the stationary beacons then even...

9:48 If you make a mistake and forget to enter the heights of each of the stationary beacons, at least the system will work perfectly. Because there will be a mistake in height, but it will not affect tracking. Okay, it will be showing like minus 2 meters. You must throw it on 0 meters. OK, you made a mistake because this is 0 by default and you didn't enter the height at 2 meters like it would be required because they are installed on 2 meters. But you will be able to notice this quite easily and never lies. The tracking will be still perfect. So also, don't forget to enter the height. I think that's all the most important elements. Always the particularity of the Inverse Architecture. So as usually, if you have any questions, don't forget to send us an email to info@Marvelmind.com and we'll be happy to help you. Thank you.

Key Takeaways

  • IA (Inverse Architecture) uses hardware-defined ultrasonic frequencies that cannot be changed—verify beacon hardware versions during deployment
  • The IA-02-3D Starter Set requires manual entry of distances between stationary beacons for accurate 3D positioning
  • Proper beacon placement strategy is critical for reliable indoor positioning coverage across your deployment area
  • Software updates and default settings configuration are essential first steps before physical beacon placement
  • Understanding IA vs NIA architecture differences ensures correct deployment procedures and system expectations

👥 Relevant For: System Architects & Integration Specialists

System integrators, warehouse managers, and robotics engineers deploying Marvelmind's Inverse Architecture (IA) positioning systems need clear deployment procedures. This tutorial solves the critical setup challenge of correctly configuring ultrasonic frequencies, placing stationary beacons, and entering inter-beacon distances to achieve accurate 3D indoor location tracking.

? FAQ

Q: Why can't I change the ultrasonic frequency of stationary beacons in IA systems?
Ultrasonic frequency in IA beacons is hardware-defined and cannot be arbitrarily changed. You must use the frequency specified for each beacon's hardware version to ensure proper system operation and compatibility.
Q: What's the difference between IA and NIA architecture?
IA (Inverse Architecture) uses stationary beacons with different fixed ultrasonic frequencies, while NIA uses a different approach. IA requires careful frequency management during deployment and manual distance entry for non-Super-Beacon setups.
Q: Do I need Super-Beacons for the IA-02-3D Starter Set?
No. The IA-02-3D includes standard stationary beacons that require manual entry of distances between them. Super-Beacons would auto-calibrate positions, but standard beacons provide a cost-effective solution with manual configuration.
Q: What steps should I follow when deploying the IA-02-3D?
Follow these key steps: update software, configure default settings, physically place stationary beacons according to coverage requirements, then manually measure and enter the distances between each beacon pair into the system.
Q: Can I skip manual distance entry if I'm careful with beacon placement?
No. Manual distance entry is required for accurate system operation. The system needs precise inter-beacon distances to calculate correct 3D positions for tracked objects and robots.

Inverse Architecture System Design

The IA-02-3D Starter Set represents Marvelmind's Inverse Architecture approach to indoor positioning—a fundamentally different deployment model from traditional setups. This tutorial provides essential guidance for system deployers on the critical technical distinctions, particularly regarding ultrasonic frequency management. A key principle in IA systems is that stationary beacons operate at hardware-defined ultrasonic frequencies that cannot be arbitrarily modified, requiring careful attention during configuration. The deployment process encompasses software updates, establishing default system parameters, strategic physical placement of ultrasonic beacons, and critically, manual entry of distances between stationary beacons into the system. Unlike Super-Beacon configurations that auto-calibrate positions, standard IA-02-3D setups require precise manual measurement and input of beacon-to-beacon distances. This tutorial systematically covers each deployment phase, ensuring accurate system initialization for autonomous robots, drones, and warehouse automation equipment requiring reliable indoor location tracking and navigation within the coverage area.

# Topics

IA architecturesetup guidestarter set

📍 Need precise indoor positioning for your project?

Plan Your System →

For more information, please contact: info@marvelmind.com

Scroll to Top