Panasonic Toughpad

[Martta Borromeo]

Werecently updated a toughpad to windows 10 and installed Collector. When we have WiFi or mobile data connection Collector is able to find our location easily but once we leave that there is no location. The toughpad used to work fine with ArcPad so has a working GPS unit. Has anyone successfully updated a toughpad to Windows 10 successfully? If so do you have any tips?

In Windows 10 Collector no longer has direct access to the Toughpad's GPS receiver's data stream. You need to install 3rd-party software (e.g., GPSComplete) to feed the GPS's data stream to the Windows Locator Service, thereby making it visible to Collector. When you have a network connection, then Collector is showing the location that the network is reporting to the Windows Locator Service.

We were successful in testing the eval version, so we went ahead and purchased the full version. For us, when we installed the Sensor Driver the correct parameters were COM3 and 4800 baud, if that helps.

Do you mind giving more details about the intel management center software that you refer to? If you are trying to access the machine from the browser (Intel AMT WebUI), you need to type: address:16993.

Hi Miguel, i installed mesh commander locally (on the toughpad) and i set up a wireless profile using the mesh commander, now it works but ONLY when windows is running if i select as action to boot into bios (from another pc) it loses connectivity.

in a few words remote desktop and all works only when windows are on and is using the windows wireless profile, if i restart i cant see anything until it boots in windows (i cant boot into bios or anything by using kvm using mesh commander)

I have used many computers with AMT before but they all had wired lan and either i configured the ip in bios or it was shared ip with OS never used with wireless card before, and yes this windows pad has intel cards and everything AMT (processor motherboatd etc)

For business environments, Intel released the software Intel Endpoint Management Assistant (EMA), it allows the OOB connections. Only systems with AMT version 11.8.79 or higher are supported. The client machine needs to run Windows Server 2019 or 2022, it is necessary to create a database with SQL 2017 or higher.

So there isnt a way to go into bios or mount remote storage when pc isnt running windows? whats the point then ? i have successfully done that with pc's running even older amt version such as 9.1 there must be some other way otherwise there is no point i could use anydesk only then.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

We have several of the Trimble Panasonic toughpad tablets and this week we had an issue started popping up on the screen yesterday when trying to export designs to a Earthworks machine. In the tablet under Data Management in Siteworks, when exporting to machine, a pop up screen asks if we still want to export since the site has not been calibrated. See pic below. This is happening with all the projects on the tablet not just certain ones. I checked the Trimble SCS900 Data folder in each job and do see there is a CAL file in each one. This particular tablet has not had any problems prior to this in the 3 years that we have had it.

There must be a missing DC file in the project folder. Siteworks will look for the DC (not the CAL) file in the project folder, and if that's missing then you'll get the message you show. So take a look and see if there's a DC in your project folder and if not, then something got buggered and the DC got moved or removed, or there never was one in the first place.

Are these new projects that worked one day and not the next? Is WorksManager being used to sync the projects? If so, is a DC or site calibration established in the WorksManager project, or the TBC project connected to WM?

If you are using the same DC or site calibration across multiple projects (for example if you just use Delaware State Plane as your coordinate system) you can copy a DC from another project. But if you did a local site calibration, then you'll need to "find" that missing DC file and get it back into the Project folder.

Thanks Steve for getting back. That seem to fix it but not sure why it was not in there. When our survey crew does a calibration it creates both a DC and CAL file which I then add to the works project. We do local site calibration so it is always in the correct state plane coordinates

could you please elaborate why the exporter would require the DC file in addition to the CAL. Initially, if you setup the job and choose a coordinate system from the library, the DC is created. Once you do a site calibration on the tablet it creates the CAL, which has the same information as the DC, plus the calibration information. At that point the DC gets irrelevant for SCS900/Siteworks and could be removed. If the exporter now needs the DC as well it somewhat is questionable if the site calibration is properly transferred to the machine files. And if yes, why does it need the DC at all, the CAL has all the necessary information.

The exporter (or Siteworks on the whole for that matter) does not "require" the CAL at all, it only needs and cares about the DC. Once the DC is created the CAL could be removed. The CAL only resides on the actual data collector that performed the site calibration if one was done. So if you have a fleet of data collectors on a project only the one that did the site calibration would actually have the CAL file on it.

Siteworks uses the DC as it (and SCS900) always has, as its coordinate system source of truth. The CAL file is produced only when a site calibration is performed, and is a way to preserve the point pairs that were used in the calibration itself. The CAL can then be brought into TBC to check the point pairs or adjust the site calibration if desired. You're correct that the CAL and DC have the exact same information in the upper part of the file, and the only difference is the CAL adds the point pairs used when the site calibration was measured. Since, once the site calibration is done, Siteworks doesn't really care about the point pairs, there's no need for the CAL file within Siteworks anymore.

3a8082e126