Map widget not displayed when using SL Agent in C | Telit Cinterion IoT Developer Community
July 3, 2015 - 4:51pm, 8138 views
(thread coming from mail exchange with a customer Mikel)
SL Agent in C is used on Linux platform.
The location map does not appear in the web interface. I am able to see all the reported locations in the reports section though. Heading information is worng but I have not been able to find the cause yet.
If the location do not show up, that may mean the device did not send at “Boot” the service ID of the location service (during the connection).
1) reboot the device and see if he enumerate correctly.
2) Check that the instantiation of the location service on SL-Agent is done correctly.
3) Worse think. Create a new device on the platform. Start the device after the creation of the device and see if it fix the problem.
How to check that he enumerates correctly and that the instantiation of the location service is correct ?
Device has been rebooted many *****. Results seem to be same in every test. In fact, two different devices have been created and used, with the same results.
I paste below the traces from the C SL Agent and the configuration file used:
*SL Agent traces*
2015-07-06 06:20:08 [INFO] [SL] SL agent framework started with config :: /home/conf/SLconfig_no_addr.xml
[06.07.15 06:20:08] GRIP API: register_iot_apps: cnt: 2
[06.07.15 06:20:08] sla_base_analog_sensor_init
[06.07.15 06:20:08] sla_base_location_init
[06.07.15 06:20:08] sla_base_location_start
[06.07.15 06:20:08] sla_get_service_instance_data: app id: 1
[06.07.15 06:20:08] sla_get_service_instance_data: app id: 1 service instance: 0x6f6c0
[06.07.15 06:20:08] sla_cfg_get_value: uuid: [354869050855147.location] attr: [report_rate]
[06.07.15 06:20:08] sla_base_location_start: set reporting rate to: 60000 ms
[06.07.15 06:20:08] sla_base_analog_sensor_start
[06.07.15 06:20:08] sla_get_service_instance_data: app id: 0
[06.07.15 06:20:08] sla_get_service_instance_data: app id: 0 service instance: 0x6f1b8
[06.07.15 06:20:10] sla_base_location_onEvent: EVENT_LINK_UP
[06.07.15 06:20:10] sla_base_analog_sensor_onEvent: EVENT_LINK_UP
[06.07.15 06:20:10] sla_base_analog_sensor_onEvent: send sensor description
[06.07.15 06:22:09] sla_handle_sensor_timer: send report: val: 20082 *****tamp: 1436163729
[06.07.15 06:22:09] sla_handle_location_report_timer: send location report
[root@owa3x]$ cat /home/conf/SLconfig_no_addr.xml
<!-- SL agent configuration:
- uuid : unique SL agent device ID
uuid = "354869050855147b"
server_addr = "220.127.116.11"
server_port = "17198"
use_tls = "false"
operation_**** = "HIGH_AVAILABILITY"
***_queue_size = "16000"
keep_alive_period = "15"
timeout = "180"
power_saving_recon_period = "60"
power_saving_idle_timeout = "10"
uuid = "354869050855147.analog_sensor"
name = "Temperature at the back of the truck"
type = "Temperature"
key = "Thermometer"
divider = "1"
measure_label = "Last Temperature"
alarms_label = "Last Alarm"
history_label = "Temperature History"
measure_unit_label = "C"
min_threshold_label = "Min Temperature"
***_threshold_label = "*** Temperature"
image = "temp.jpg"
scan_rate = "1000"
report_rate = "120000"
min_threshold = "0"
***_threshold = "23000"
uuid = "354869050855147.location"
name = "GPS"
report_rate = "60000"
Hope this helps.
If all the location reports are visible in the reports section on the server as Laurent described then the problem is not in the device and the device's software but on the server in my opinion. The device is only responsible for sending the reports and if the reports are received by the server everything is fine on the device. I can also see in the device's log that the location report is sent.
So I'd start form asking the server teem for some investigation on their side why there's no map.
As you are using the C version of SLAgent there's one more thing that can matter here and is probably the reason of the above problem. So please check this first.
In the C version you can do much more configuration (also mistakes) than in the Java version.
The issue with the location tab is, that it is visible by default, but if the client application (SLagent) sends
during enumeration a “wrong” user defined UUID, the enumeration tab is disappeared.
For Location service the UUID should be “LocationReport”. In Java versions it is not configurable so there can be no mistake here.