Thank you 
, @geckoVN
Ais-catcher displaying targets older than 20 minutes. Looking at removing from the map targets that are older than 5 minutes. Any ideas? Thanks!
You could aks Jasper himself on github, not sure that this option is currently exposed.
Hi,
The history command as below allows you to extend or shorten the default time.
See “Data Management” section here:
HISTORY integer - History retention (5-43200 sec)
If you are using commnd options to run AIS-catcher, just add an additional command as below to limit the history to 5 minutes (300 seconds).
-N HISTORY 300
If you are running from a config file or auto installation method, you will need to look at the documentation for your install method to see how to add that same HISTORY option.
Regards,
-Dan
1 Like
If the AIS-carcher is installed by installtion script at my Github site, the config file is to be edited
Following command will open config file. To this file add new line -N HISTORY 300
sudo nano /usr/share/aiscatcher/aiscatcher.conf
-d 00000162 ##Dongle serial Number
-v 10
-M DT
-gr TUNER 38.6 RTLAGC off ##Dongle gain
-s 2304k
-p 3 ##Dongle temprature correction, ppm
-o 4
## Map in Browser will be displayed on port number 8100 set in line below
-N 8100 geojson on REALTIME on CDN /usr/share/aiscatcher/webassets
## Replace below 51.50 and -1.00 by actual values at your location
LAT 51.50 LON -1.00 SHARE_LOC ON
## Below replace "my-station" by your station's desired name
-N STATION my-station
## TCP Server listening on port 5012
-S 5012
## Un-comment line below if UDP connection to local apps is required (multiple allowed)
## -u 127.0.0.1 10110
## Un-comment line below if TCP connection to local apps is required
## -P 127.0.0.1 10111
-N FILE /usr/share/aiscatcher/stat.bin BACKUP 60
-N PLUGIN_DIR /usr/share/aiscatcher/my-plugins
## Add below url & port number of sites to be fed
## one site per line, as in examples below (xxxx is port number)
## -u data.aishub.net xxxx
## -u hub.shipxplorer.com xxxx
1 Like
Thanks Dan, since it was installed via abcd567’s I was able to update the config with -N HISTORY 300
Nice script. Thanks!
1 Like
Is anyone feeding ShipXplorer and having issues with station showing as offline most of the time? All other feeds are rock solid.
Mine is reporting often as offline but is still showing ships on the iOS App and nothing in the web browser.
Support has been mute…
Fairly normal for shipxplorer.
I have given up worrying about them.
S
+1
I found them so unreliable, I gave up feeding them.
I spent ages hunting a problem on my site the turned out to be ‘their problem’, I lost my sense of humour.
I contacted tech support several times for different issues, but never once got a reply.
Finally I’d had enough and pulled the plug.
I still feed ShipXplorer (in addition to other aggregating sites), and never bother if any of these aggregating sites are accurately showing the ships received by my receiver.
For me, the most accurate map & ship plot is the map provided by the AIS app installed on my RPi, i.e. the “AIS-catcher”, which is a combination of AIS receiver, decoder and feeder to various sites.
1 Like
Sure - I still have my receiver running, but I couldn’t see the point of feeding a zombi site.
In my location, I was the only station for about 800km in either dirrection, but if their site isn’t working, whether I feed or not, it makes no difference.
They are sister organization of AirNavRadar (aka Radarbox24), and the RB24 feeders have similar complaints abot its web interface too.
If you look at station web map of RB24 and ShipXplorer, these are idendical.
Sad but true.
20 Chr
I’ve stopped feeding from one of my devices.
sudo systemctl stop sxfeeder
sudo systemctl disable sxfeeder
sudo rm /lib/systemd/system/sxfeeder.service
You were feeding them by installing their feeder software package. It seems the problem was with their app.
I dont have such severe problem with them as I have NOT installed their feeder app. I am running AIS decoder sofware named “AIS-catcher” which is capable to directly feed any site by adding a line in it’s config for each site like below. (the xxxxx in each line is a different udp port number assigned by each aggregator site when I signedin with them)
-u 5.9.207.224 xxxxx ##Marine Traffic
-u ais.vesselfinder.com xxxxx ##Vessel Finder
-u hub.shipxplorer.com xxxxx ##ShipXplorer
-u 54.204.25.151 xxxxx ##Pocket Mariner
-u data.aishub.net xxxxx ##AIS Hub
I have 3 RPi’s feeding AIS and ADS-B. 2 of them feeding SX, I had 1 using their feeder software package and another via AIS-catcher installed using your excellant script. Both SX feeds have issues. AIS-catcher is rock solid, so is the feeds to others. The 3rd one is using AIS Dispatcher, also reliable.
I agree.
Unfortunately, the feed from aiscatcher to shipxplorer is woefully unreliable. More red than green.
S.
Also has the advantage the line is just as easy to remove !!
2 Likes
