Repository navigation
Replies: 7 comments 25 replies
|
please note: #441 |
|
Dirk, noted, thanks, Roger |
|
Yes, good suggestions. Also we could link to the nmea decoder screen once paused to dive into a message or the ship specifics via MMSI. Perhaps filtering as well. Also planning to add a playback mode using this realtime functionality |
|
Noted the "also" bits above: yes please, I did not want to appear too greedy! |
|
Ok, quite some changes. First of all there is a play/pause button and a filter on MMSI option: 
If you click on the wrench you will go to the decoder tab where the NMEA line is parsed. For individual ships on the map, you will see a Track NMEA option that will take you to the NMEA stream filtered for this ship. It can also be accessed via the context menu: 
Thanks for the suggestions! |
|
Just to be clear you need to run with something like: Or if you configure via the Web GUI switch on decoder and realtime: 
|
|
Thank you Jasper, A quick test shows it looks good but a few strange things happen (could be my interpretation of what should happen). I will test further tomorrow... you just provided my next task (computing-wise) in a timely manner: I have just finished upgrading my ADSB installation to Trixie, and doing final (I hope) testing! regards, |
|
best to install the latest when you start... still fixing some bugs I can spot in the mean time |
|
Will do, a "bug" perhaps for you: I start a filter for a less busy MMSI and collect some data... good so far:
Then I navigate away from the page and go to another browser tab..... when I go back to the AIS-catcher tab I expect those entries and any new ones to be displayed... so I can review them. I get this
all gone and I wait for some more: so I cannot navigate away else the page gets refreshed (emptied of useful data). Not good! Roger |
|
Yes, the collection of NMEA only takes place while on the realtime page. I have tweaked it a bit so the history is not cleared but when you move away and come back you will have a gap in the stream. Also when you minimize the browser, the streaming will stop. I guess the way around this is to open a browser with this page visible. Obviously, we can change, but for now this is by design (and in line how it was) to avoid accidentally having an open streaming connection in the background that takes bandwidth but data not being used. I first want to see if this is conceptually useful before a complete overhaul. Btw if we would consider an active stream at all times, we can also update the map continuously, instead of every 2.5 seconds.... |
|
I gave the tracker and filter functions a good test yesterday. All works well. Just need to be able to enter MMSIs to filter on from the kbd (as mentioned above). Being able to have it work in the background makes it much better. Thanks for adding and fixing. Roger |
|
Thanks for testing! Also the filter option has been added via the filter icon. I will close this discussion. Thanks for raising. 
|
|
Hi @g7ruh, |
|
Hi @Phil353556 Docker...... ooooooo.... NO! Old school here. Just a new install of Trixie and upgraded my AIS stuff manually. I have much more control and less restrictions by doing it the old-school way. I do not need a whole load of stuff I HAVE to learn before I can run the software package: in other words learning how to install and run and maintain <docker | snap | flatpack | etc> and what I read about those methods: they make it easy to install as " an average user ": that is good, but I prefer to have control and not be feature-restricted as some of those tools are. AIS-catcher may not fall into that category, but as a house rule, I don't use them "unless there is no other way", in which case I may well not bother. Life is too short! Not a rant, just how I prefer to work: I understand how my software and OS work by doing it myself. Regards, PS: AIS-catcher and OpenCPN work fine on Trixie |
|
Hello Roger, @jvde-github I don't know the percentage of AIScatcher installation running under docker. Do you have this information ? regards |
|
No, don't store and collect any user details of feeders. |
|
OK |
|
Some overnight thinking....I have added a toggle to keep the streaming running in the background when you move around the tabs. Also can filter on multiple MMSI and option to clean the table. 
|
|
OK, that makes sense. But for an infrequent one, e.g. base station, I need to be able to enter an MMSI I cannot watch for a every 10 minute event and hope to catch it on the scrolling screen. the MMSI box does not allow entry when displayed. Really needs to be an input function as well. |
|
What is the problem to go to the map and right click there? |
|
I see it on the list when click on the item on the map, still prefer an input option rather than trying to find the vessel to display the click options. I may be watching for a particular vessel which is not transmitting or is out of range and want to see when I get data from it. I noted its MMSI (say) a week ago and want to see if it is around or not. |
|
Ok... Will add that to the list for future. Made a small update: can now pause the stream with spacebar and click on the table. Also the realtime icon in the top bar starts to blink if data is streaming as an indicator of bandwidth usage. |
|
Pause and resume work well, the message confirming it. The colour of the messages is good: it is obvious and great feedback to the user that something happened. The blinking indicator is good too. |
|
Good morning, thanks for the new toy!
|
|
You mean backwards in the browser? need to investigate if that is possible. On the right-click, what function specifically do you want to open in a new tab? |
|
Uh oh!
There was an error while loading. Please reload this page.
Jasper,
The NMEA list in the web viewer is a bit hard to read as it scrolls then clears the page and starts at the top again. Useful to check that AIS-catcher is working but that is about all.
Could you just keep adding lines from the top until the page is full and just continue so the messages keep moving down.
Then can you add a pause and restart function (perhaps just mouse click to stop and then again to restart).
That way you can inspect messages and if anything "strange" is noticed, you can pause and cut and paste into a file or even into the decoder function.
Thanks for considering,
Roger
All reactions