- Basic matters
- Application-wide issues
- Camera image issues
- Camera image is not displayed
- There is a problem with the connection between the camera and the edge server.
- VideoStreaming module is still starting
- VideoStreaming module is stopped
- VideoStreaming module and camera cannot communicate
- AzureEventGridonIotEdge is having an error
- Streaming IP settings are incorrect
- Streaming parameter settings are incorrect
- Camera image stopped
- Camera video is delayed
- The camera image appears shaky (moving forward and backward)
- Vertical noise or green lines appear in the camera image
- Display a message that streaming is unavailable
- Else
- Camera image is not displayed
- Object recognition Issues
- Map issue
- Sensor data issues
- Anemometer data is not displayed
- True wind direction and true wind speed data are not displayed
- Latitude and longitude data are not displayed
- Heading data is not displayed
- Ship speed data is not displayed
- Compass ring is not moving in compass animation display
- The C icon (course) is grayed out in the compass animation display
- The T icon (true wind direction) is grayed out in the compass animation display
- The R icon (relative wind direction) is grayed out in the compass animation display
- Image recording function issue
- Setting details
- Troubleshooting Microsoft Azure
Basic matters
In the event of a problem, please record the details of the incident as a basic matter.
-
Record a snapshot of a problem.
-
Record the environment at the time of trouble.
（Date and time of occurrence, operating method, software version, etc.）
Also, use the following method to collect logs from the edge server.
How to collect logs
-
Log in to the Edge Server.
-
Run the terminal application.
The current directory is /home/iotadmin.
-
Create a directory to collect logs and move to that directory.
Exp:
mkdir Logfile
cd Logfile
-
Create a log file with the following command.
sudo iotedge support-bundle –since 1d
-
'1d' in the above command means to collect logs from one day ago.
For example, if you want to collect logs from 4 days ago, specify 4d.
-
A zip format log file will be created, so get that file.
Application-wide issues
Command application does not start
Command application version is old
If the version of the Command application on the iPad is outdated, there may be a problem communicating with the edge server and you may not be able to start it. Check the current version, and if the version is old, update the Command application to the latest version.
Unable to display map, camera’s video, sensor data, etc.
ServiceApi module is stopped
If the ServiceApi module in the edge server is stopped, restart the module to recover. The steps are as follows.
-
Launch AdminUi from the edge server’s browser.
URI : http://[ Edge server IP address ]:5002/home
（Login is needed. Login user name is jrcs_admin）
-
Display the Maintenance Menu page and press the Restart button of the
ServiceApi module.
Camera image issues
Camera image is not displayed
There is a problem with the connection between the camera and the edge server.
Please check the connection between the edge server and each camera.
-
Check that the PoE hub (Netgear PoE switch) for the camera is activated.
-
Check that the camera’s LAN cable is connected to the PoE hub.
-
Check that the LAN cable of the edge server is connected to the PoE hub.
①
③
②
VideoStreaming module is still starting
Immediately after starting the edge server, each module may still be starting. Please wait about 1 minute and check the camera image display again.
VideoStreaming module is stopped
If the VideoStreaming module in the edge server is stopped, restart the module to recover. Please refer to section 2.2.1 for the procedure.
VideoStreaming module and camera cannot communicate
Please restart the camera.
Please disconnect and reconnect the cable② in Section 3.1.1.
AzureEventGridonIotEdge is having an error
To restore the state of Docker in the edge server to a normal state, rebuild Docker using the procedure in section 9.2.1.
Streaming IP settings are incorrect
-
Launch the Command application on your iPad and log in as an administrator role.
-
Press the settings button at the bottom of the dashboard to open the settings screen.
-
Confirm that the settings for the ‘Streaming endpoint’ are as follows.
http://[ Edge server IP address ]
Streaming parameter settings are incorrect
-
Launch the Command application on your iPad and log in as an administrator role.
-
Press the settings button at the bottom of the dashboard to open the settings screen.
-
Make sure that both the Ffmpeg option and Ffplay option settings have the following values.
Setting valule： -fflags nobuffer -flags low_delay -analyzeduration 0 -probesize 32
Camera video is delayed
Bounding Box delay settings are incorrect
If the Bounding Box is displayed faster than the camera image, the Bounding Box delay setting is incorrect. Please change the Bounding Box delay setting value using the following method.
-
Launch the Command application on your iPad and log in as an administrator role.
-
Press the settings button at the bottom of the dashboard to open the settings screen.
-
Increase the value of Bounding Box Delay (ms) larger than the current value and adjust it to a value that displays the detected object in the camera image and the bounding box overlapping.
The camera image appears shaky (moving forward and backward)
Wi-Fi communication load is high
The iPad’s Wi-Fi connection is poor, so please reconnect Wi-Fi.
-
Close the Command application.
-
Turn off the iPad’s Wi-Fi connection.
-
Turn on the iPad’s Wi-Fi connection
-
Launch the Command application and check the status of the camera image.
If the above does not solve the problem, try moving closer to the Wi-Fi access point. Also, if the communication band is 2.5GHz, please reconnect to 5GHz.
Vertical noise or green lines appear in the camera image
Wi-Fi communication load is high
The iPad’s Wi-Fi connection is poor, so please reconnect Wi-Fi.
-
Close the Command application.
-
Turn off the iPad’s Wi-Fi connection.
-
Turn on the iPad’s Wi-Fi connection
-
Launch the Command application and check the status of the camera image.
If the above does not solve the problem, try moving closer to the Wi-Fi access point. Also, if the communication band is 2.5GHz, please reconnect to 5GHz.
Display a message that streaming is unavailable
VideoStreaming module is stopped
If the VideoStreaming module in the edge server is stopped, restart the module to recover. Please refer to section 2.2.1 for the procedure.
Object recognition Issues
AIS data not displayed
VDR and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving AIS data and the LAN cable connection status of the edge server.
Map issue
Map not displayed
Map API settings are incorrect
-
Launch the Command application on your iPad and log in as an administrator role.
-
Press the settings button at the bottom of the dashboard to open the settings screen.
-
Confirm that the settings for the Custom map API are as follows.
（In case of using Free Map Server）
Custom map API： http://[ Edge server IP address ]:8181/
WMS Server： no check
Use Carmenta Server: no check
（In case of using Geomod Map Server）
Custom map API： http://[ Edge server IP address ]:8686/
WMS Server： check
Use Carmenta Server: no check
（In case of using Carmenta Map Server）
Custom map API： http://[ Edge server IP address ]:8989/
WMS Server： check
Use Carmenta Server: check
Own ship icon is not displayed on the map
Own ship is far away from the center of the map and I can’t see it.
Click the arrow icon at the bottom right of the map view to center your ship’s position on the map.
Own ship icon always faces north
Sensor data issues
Anemometer data is not displayed
Anemometer receiver and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving wind direction and wind speed data, and the connection status of the LAN cable of the edge server.
Please refer to Section 4.2.1 for the confirmation location.
True wind direction and true wind speed data are not displayed
Please check whether the anemometer used on the own ship is compatible with true wind direction and true wind speed. Some devices only output relative wind direction and relative wind speed.
Latitude and longitude data are not displayed
GNSS receiver and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving GNSS data and the LAN cable connection status of the edge server.
Please refer to Section 4.2.1 for the confirmation location.
Heading data is not displayed
GYRO sensor receiver and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving GYRO (heading) data and the LAN cable connection status of the edge server.
Please refer to Section 4.2.1 for the confirmation location.
Ship speed data is not displayed
GNSS receiver and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving GNSS data and the LAN cable connection status of the edge server.
Please refer to Section 4.2.1 for the confirmation location.
Compass ring is not moving in compass animation display
The C icon (course) is grayed out in the compass animation display
The T icon (true wind direction) is grayed out in the compass animation display
Anemometer receiver and edge server cannot communicate
Please check the connection status of the LAN cable of the VDR receiving wind direction and wind speed data, and the connection status of the LAN cable of the edge server.
Please refer to Section 4.2.1 for the confirmation location.
The R icon (relative wind direction) is grayed out in the compass animation display
Image recording function issue
Recording fails
The disk size for saving recorded data is full
Delete past recorded data displayed in ‘Past Recordings’ on the recording screen of the Command application to secure disk space for recording.
Alternatively, increase the storage disk size for recorded data set on the edge server using the following method.
-
Launch AdminUi from the browser of edge server.
URI : http://[ Edge server IP address ] 5002/home
（Login is needed. Login user name is jrcs_admin）
-
Display the Recorder Menu page, increase the disk size set in the System Settings item, and press the Submit button.
Setting details
Command application settings
| Item | Value | Remarks |
|---|---|---|
SEQ Logging |
OFF |
Send Command application logs to the edge server. Set ON when an investigation is required. If so, also set ON Verbose Logging. |
Verbose Logging |
ON |
|
Simulation Mode |
OFF |
By setting it to ON, the following pseudo data will be used. (Video, GNSS, AIS, Gyro, Anemometer, ML output) When set to ON, the items (*1) will be displayed. |
Main Display Camera |
OFF |
When turned on, the camera view will be displayed when the application starts. |
GigECamera |
ON |
This setting should always be ON. |
Enable Test Video |
OFF |
When set to ON, recorded video data is used instead of camera footage. Generally please set it to OFF. |
Video Player |
Webrtc |
Choose Webrtc. |
Port Video URL(*1) |
FORE1 |
Video data for simulation. (Use only Simulation Mode) |
Center Video URL(*1) |
FORE2 |
〃 |
Starboard Video URL(*1) |
FORE3 |
〃 |
Port Video ID |
FORE1 |
Don’t to change. |
Center Video ID |
FORE2 |
〃 |
Starboard Video ID |
FORE3 |
〃 |
Set GigECamera Settings |
OFF |
unused. (*2) All relevant settings regarding camera configuration are unavailable. |
GigECamera(*2) |
CenterCamID |
Camera ID name. (unused) |
DisplayRange(*2) |
Higher |
Display range level. (unused) |
Min(*2) |
18000 |
Minimum setting value of display range. (unused) |
Max(*2) |
65000 |
Maximum setting value of display range. (unused) |
OffsetX(*2) |
0 |
Cutting start position of camera image (1920x1080). If you want to cut in the center, the OffsetX value is 480. (not use) |
OffsetY(*2) |
0 |
Cutting start position of camera image (1920x1080). If you want to cut in the center, the OffsetY value is 390. (unused) |
Gain Auto(*2) |
ON |
Camera gain setting. (not use) |
Exposure Auto(*2) |
ON |
Camera exposure setting. (unused) |
Exposure Auto Algorithm(*2) |
Pixel Median |
Camera exposure algorithm setting. (unused) |
Target Brightness(*2) |
128 |
Camera image brightness(0 to 256). (unused) |
HDR Tuning(*2) |
OFF |
When set to ON, the camera’s HDR function is enabled. When set to ON, the settings for item *3 will be displayed. (unused) |
HDR Output(*2) |
HDR |
Choose HDR. (unused) |
HDR Exposure Time(*2, *3) |
30000 |
Exposure time of HDR. (unused) |
HDR Analog Gain(*2, *3) |
30 |
Gain value of HDR. (unused) |
API Preset |
Blank |
Selecting this will reflect the endpoint settings for reference.(*4) |
Default Endpoint(*4) |
XXX is Edge server IP address |
|
Identity(*4) |
(port 5500) |
〃 |
ServiceApi(*4) |
(port 5001) |
〃 |
Streaming(*4) |
(port 4430) |
〃 |
Custom Map AP(*4)I |
Depends on the map server you install |
|
WMS Server |
OFF |
ON when map server is installed |
Use Carmenta Server |
OFF |
ON when installing Carmenta map server |
SEQ Endpoint |
XXX is Edge server IP address |
|
AIS Camera Cache Refresh |
1 min |
Time to continue displaying even if AIS data is no longer received. |
Ffmpeg Options |
-fflags nobuffer -flags low_delay -analyzeduration 0 -probesize 32 |
|
Ffplay Options |
-fflags nobuffer -flags low_delay -analyzeduration 0 -probesize 32 |
|
Camera Count |
3 |
Number of install cameras |
Bounding Box Delay(ms) |
0 |
Adjust the timing of camera image display and BBOX display. |
ML Fusion Distance(nm) |
0.1 |
Setting the distance to fuse ML detection and AIS data. (unused) |
ML Distance in Meters? |
OFF |
When turned on, the distance to the recognized object is displayed in meters. |
Show CPA Data |
ON |
When turned on, CPA data will be displayed. |
Enable panoramic view |
OFF |
When turned on, you can switch cameras by swiping. |
Additional Debug Info |
OFF |
Display debug data in bounding box. |
Memory usage info |
OFF |
Shows memory usage on screen. |
Always Restart Streams |
OFF |
Restart Video Streaming module periodically. (unused) |
Troubleshooting Microsoft Azure
Azure IoT HUB issues
Unable to deploy to edge server
Updating the IoT Edge runtime may help. In that case, please update the runtime using the following command.
sudo apt-get update
apt list -a aziot-edge
sudo apt-get install aziot-edge Defenseer-iot-micro-agent-edge
sudo iotedge config apply
Then restart the edge server.
If the above methods do not resolve the issue, there may be other issues. If the time difference between your Edge server and Azure is more than 5 minutes, restarting the Edge Agent may not work. If all the modules in the edge server disappear and you cannot deploy due to an error in the Azure portal, use the following method to deal with it.
Run the command below
sudo systemctl stop aziot-edged
sudo rm /var/lib/aziot/edged/*
sudo rm /var/run/iotedge/*
sudo systemctl start aziot-edged
AzureEventGridonIoTEdge issues
When deploying a template, an error occurs with AzureEventGridonIoTEdge
Follow the steps below to clear the iotedge container in the edge server.
sudo iotedge system stop
sudo docker container prune
sudo docker image prune
sudo iotedge system restart
After executing the above command, deploy the template again.