@Jonathan Sulger wrote:
I have been testing cnArcher with cnMaestro.
It is working like expected but I have a few issues.
1. I have to agree that when moving to DHCP it is very problematic. Giving cnMaestro a public IP helps but cnArcher will just stall if it is not able to talk to the subscribers module once it has an IP that is not default. Is there any way to continue onboarding through cnMaestro without having a connection to the subscribers module?
It looks as if the only way to continue the process would be to fully setup the customers connection and use their wireless to continue the installation. I am sure that many companies probably dont allow access from the customers connection to subscribers module private address which would prevent using the customers wireless in that case.
You have two options. First options is that you can let cnArcher automatically configure the Wi-Fi connection. It will set a static IP in the 169.254.1.x network when it wants to talk to the SM, and it will switch to DHCP when it wants to talk to cnMaestro. When it switches to DHCP, it expects that the phone will be assigned a DHCP IP address by the network, and that it will be able to talk to cnMaestro using that IP. If either of those assumptions are wrong, it will get stuck when it tries to switch to DHCP.
The second option is for you to manage the connectivity manually. To do this, you should click on "Skip Wi-Fi Setup" link at the bottom of the screen when you get to the Wi-Fi setup screen during the initial setup. Currently, after the initial setup is complete, this option is no longer available, but with the next update, you can go back to "Settings" and set it up. In this mode, the app will not try to set a static IP or change to DHCP. It will just try to contact 169.254.1.1 to talk to the SM, and to cnMaestro server when it is ready to onboard. You are responsible for making sure this connectivity exists. In this mode, you could even turn off Wi-Fi and switch over to 4G once you see that the app is trying to contact cnMaestro, assuming cnMaestro is reachable over 4G.
If your network is such that the installer cannot access cnMaestro, either through the SM or by swithing over to 4G, you have no option but to disable cnMaestro in the app settings.
2. I have setup some variables that get passed on and updated to the Site Contact and Site Location fields which are working great. I would also like to include lattitude and longitude that are passed on and updated from the techs phone rather than manually adding it. Is there a variable that I can add into the template to grab these automatically?
The lattitude and longitude are automatically populated by the app on the SM based on the phone's GPS location. When the SM is onboarded into cnMaestro, cnMaestro will automatically retrieve the lat/long from the SM. So for SMs installed using cnArcher, it should show up at the right coordinates on the map in cnMaestro. You don't have to do anything extra.
3. It would be nice to have a QRCode for initial setup that could be scanned in order to set initial configuration in cnArcher like cnMaestro url, channel size and selected frequencies etc...
This functionality will be part of the next v1.1 beta update (within couple of weeks). You will be able to export the configuration as a JSON file, convert it to QR code using any online QR code generator, and send it to your installer, and they will be able to scan the QR code in to import the configuration. Longer term, we also plan to add a feature in cnMaestro so the installers can download the app settings from cnMaestro.
4. It would also be nice to be able to reset a work order to its original defaults in case the wrong one was used or it could possibly be used as a template for multiple installs without having to rescan the QRCode.
How about we allow you to clone a work order to create a new one? You can also clone a completed work order to repeat the same.
5. When running the link test is there a way to add the effeciency information also such as downlink/uplink effeciency percent and actual/missed fragment count?
We can add it, but will you really use the information? Would you tell your installer to look at this information and do something different if some threshold is not met? Or is this just for archiving the baseline?
This looks very promissing and it would be nice to roll this out to the Service Techs but definitly need to resolve #1 before it would be possible. I like the templates that help provide constistency and help remove manual programming errors.
For #1, if the answer above does not solve the issue, let me know how the app can access cnMaestro and we will try to enable that. For example, if cnMaestro is accessable only when the phone is connected to the corporate WLAN, we can split the install into seperate phases: align, link test and configure the SM on site, come back to office amd connect to corporate WLAN and onboard the SMs.