jvde-github / ais-catcher-for-android Goto Github PK

Jasper,

Several, I suspect interrelated issues:

1. The app does not close when you select the square icon in middle bottom of screen. An app 'force stop' is needed.

Start app with sample rate = 288K Tuner = 49

2. when connect to rtl_tcp app works as expected until press 'Stop' on app

After stop pressed, rtl_tcp gives the following:

then a bit later the following with a ctl-C to stop it. rtl_tcp does not exit but then returns to listening... Select 'Start' on app and all starts going again until select 'Stop' and the same thing happens

A second ctl-C will end rtl_tcp as expected.

Is AIS-catcher not terminating the link to rtl_tcp correctly? It was all working fine on the previous version and I only saw the "11+, now..." messages at high sample rates, which you confirmed is an overload condition.

EDITED to add:

I recall that pressing the square icon would close the screen and leave an orange dot on the app icon as it was still open and processing: there is no such indicator on this version

regards
Roger

Is there any hope to see HackRF support?

Can I get data from Ais-catcher on my Pi (static IP or dyndns) to Ais-сatcher-for-Android (dynamic IP) ?
What settings should be done at both ends?
Thanks!

Jasper,

I have the following on my Pi screen while runninl rtl_tcp. I saw it yesterday, briefly too. Is it indicating a problem? Is it a sample overload type issue as I am using 2304 rate?

Use the device argument 'rtl_tcp=172.27.0.45:12345' in OsmoSDR (gr-osmosdr) source
to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...).
client accepted! 172.27.0.57 43310
Allocating 15 zero-copy buffers
set freq correction 0
set gain mode 1
set gain 240
set sample rate 2304000
set freq 162000000
ll+, now 1
ll+, now 2
ll+, now 3
ll+, now 4
ll+, now 5
ll+, now 6
ll+, now 7
ll+, now 8
ll+, now 9
ll+, now 10
ll+, now 11
ll+, now 12
ll+, now 13
ll+, now 14
ll-, now 0
ll+, now 1
ll+, now 2
ll-, now 0
ll+, now 1
ll+, now 2
ll+, now 3
ll+, now 4

Jasper.

I have been testing all the interfaces but I cannot get rtl_tcp to work.

Can you give me a few points as to setup on the Pi and phone, not sure I have done it right or if the is a problem. Most likely the former!

Roger

When the source codes have a major update, could you please update the apk on Google Drive？Thank you.😄

Jasper,

Before the most recent version (with the TCP bug), when using AIS-catcher and accessing the web client, ending the web client would close the web page and the AIS-catcher icon would have an orange dot on it, indicating it was still running in the background.

In the current version, there is no orange dot on closing the web client.

AIS-catcher still runs in the background and processes data and when icon pressed screen comes back with correct display.

If stop feed, the program still runs in the background, the Running Time counter increments, even though there is no feed (tested using rtl_tcp).

I think that the previous version did end, but I might be wrong.

A force stop for the app ends the program and on startup the Running Time counter is reset.

I would expect the following to happen:

Assume AIS-catcher is running with the web client displaying a page:

End web client, should end it (it does) and leaves AIS-catcher still running (it does). It should indicate that the app is running in the background (orange dot), it does not do that.

Select AIS-catcher icon and it displays current data (it was running in background): expected result.

Stop processing by pressing Stop: AIS-catcher disconnects from feed (expected). Running Time increments (if it is 'app running time', that is correct).

Press the square symbol in middle bottom of screen, AIS-catcher appears to close. It still has the Running Timer running. I would expect the app to end and stop completely if not processing data. On restart app, it should be a new session with Running Time reset.

If 'force stop' app, it does end and reset Running Time counter on restart.

Is the current behaviour intended?

Roger

I have a no name rtl dongle.
When I start I get 20 to 60 Messages, and than it stops.
Even when I start the app again, or reattach the dongle, I only 0 to 2 new messages.
With the same setting, dongle and antenna, with windows 10 and SDRangel I get a continous stream of NMEA messages
Any idea what is wrong?

Sorry, but I am just tried to pick up the app in Play Store by searching "ais catcher". But no success so far. Finding apps like MarineTraffic, RTL SDR AIS Driver and other.

Moin,
I installed your latest version, but it say's 0.21, and not 0.22.
Wrong apk or wrong number?
Greetings

Jasper

I have loaded the ap and tested with an RTL-SDR dongle. Rather than use another app to view the data, is it possible to have the web server functionality from AIS-catcher added to the Android version?

If so, will it be possible to use the device GPS to provide location data for the web server map?

It would make it a "one stop shop" for AIS-catcher when mobile.

Thanks

Roger G7RUH

I'm getting boat positions in OpenCPN now.
I think a full tutorial is needed though 😄

For now, the problem is with duration. The RTL-SDR driver is started manually and it throws:

onStart
RtlSdr: found 1 device opening options
HackRF: found 0 device opening options
Only 1 option available, no need to ask user. Opening rtl-sdr /dev/bus/usb/001/003
Queueing
Arguments SdrTcpArguments{gain=24, samplerateHz=1024000, frequencyHz=91800000, address='0.0.0.0', port=14423, ppm=0}
Starting service with device rtl-sdr /dev/bus/usb/001/003
Opening fd 48
Set sampling rate to 1024000
Tuner gain set to 2.400000 dB
SdrTcp: Listening on [0.0.0.0:14423](http://0.0.0.0:14423/)
SdrTcp: Waiting for client...
Device was open. Closing the prompt activity.
The rtl-tcp implementation is running and is ready to accept clients
Acquired wake lock. Will keep the screen on.
Starting was successful!

SdrTcp: TCP server succesfully started and listening for clients!
SdrTcp: Client has connected.
set freq correction 0
set gain mode 0
set sample rate 240000
SdrTcp: commandListener failed to receive command
SdrTcp: Command listener thread exiting
SdrTcp: Waiting for command thread to die
SdrTcp: TCP server shutting down.
SdrTcp: Closing sdrtcp due to main thread finishing
SdrTcp: Closing from state 0
SdrTcp: Server thread shut down
rtlsdr_read_async finished successfully
SdrTcp: Requested sdrtcp stop but already stopped
Successfully closed service
Wake lock released
Closing service

Starting was successful! is the last message before launching AIS-catcher.
I don't know what commandListener is, but it seems that it's missing at some point and it closes.

Jasper,

A small thing, in the Edge section, the link to the web page is spelt incorrectly.

"I created aischatcher.org and started sharing data..."

Roger

Hi,
Your project seems great!
I have a RTL-SDR receiver and live near the sea, I successfully got 11 messages (type: other) and set up a connection (UDP, 127.0.0.1:10110) on opencpn free (android) but I don't see any boat on the map.

Would you please share the full process to link your catcher and opencpn?

Thank you