Hi Andy,
I'm still using the tail -f way, as the only information I need to parse is the RIC. Most counties use one RIC per station (except Lincolnshire which use some bizarre combinations). Most fire alerters have no screen to relay incident details, they just go beep (I asked a friend of mine ...
Search found 56 matches
- Mon Apr 14, 2025 9:26 am
- Forum: POCSAG Specific Support
- Topic: Using cron to trigger a POCSAG message
- Replies: 8
- Views: 80443
- Mon Mar 31, 2025 2:15 pm
- Forum: POCSAG Specific Support
- Topic: Sub Codes A-D
- Replies: 0
- Views: 6370
Sub Codes A-D
Hi all,
Does anybody have any idea if it is possible to send messages via RemoteCommand locally to different subcodes?
It would appear that pistar and dapnet default to D.
I have a 602r ripoff, and it would be nice to send to different sub codes, particularly to set the "urgent" flag for a given ...
Does anybody have any idea if it is possible to send messages via RemoteCommand locally to different subcodes?
It would appear that pistar and dapnet default to D.
I have a 602r ripoff, and it would be nice to send to different sub codes, particularly to set the "urgent" flag for a given ...
- Sat Jan 25, 2025 9:15 am
- Forum: POCSAG Specific Support
- Topic: Using cron to trigger a POCSAG message
- Replies: 8
- Views: 80443
Re: Using cron to trigger a POCSAG message
I'm not using Pi-Star commercially, it is for my own personal use., using amateur frequencies on a low power MMDVM pi-hat. I just want to know when my local fire station gets a turnout so I can tune my RX to the right frequency.
it was more of a "proof of concept" idea to see whether or not it was ...
it was more of a "proof of concept" idea to see whether or not it was ...
- Sun Jan 05, 2025 8:17 am
- Forum: POCSAG Specific Support
- Topic: Using cron to trigger a POCSAG message
- Replies: 8
- Views: 80443
Re: Using cron to trigger a POCSAG message
Thanks for the reply, suggestion duly noted!
I've currently found a way around it - I pipe my rtl_fm output to a text file and then use :
tail -F /home/pi-star/output.txt | grep --line-buffered '141209' | while read ; do sudo RemoteCommand 7642 page 1743171 "FIRE CALL DMK" ; done
The biggest ...
I've currently found a way around it - I pipe my rtl_fm output to a text file and then use :
tail -F /home/pi-star/output.txt | grep --line-buffered '141209' | while read ; do sudo RemoteCommand 7642 page 1743171 "FIRE CALL DMK" ; done
The biggest ...
- Fri Dec 20, 2024 11:43 am
- Forum: POCSAG Specific Support
- Topic: Using cron to trigger a POCSAG message
- Replies: 8
- Views: 80443
Using cron to trigger a POCSAG message
Hi All,
This is probably more of a general Linux question, but seeing as it is a pistar box, here goes!
I would like to be able to monitor a text file at regular intervals (cron?), and if a given value is present within the file to then trigger a local message (I can do that bit already ...
This is probably more of a general Linux question, but seeing as it is a pistar box, here goes!
I would like to be able to monitor a text file at regular intervals (cron?), and if a given value is present within the file to then trigger a local message (I can do that bit already ...
- Thu Feb 22, 2024 11:18 am
- Forum: MMDVM_HS Hat(s)
- Topic: Cannot get the control attributes
- Replies: 7
- Views: 13711
Re: Cannot get the control attributes
With 4.3.0 I have the problem every single time I reboot!
I've set up a cron job to deal with it.
@reboot sleep 35 && rpi-rw
@reboot sleep 40 && sudo rm /dev/ttyAMA0
@reboot sleep 45 && sudo mknod /dev/ttyAMA0 c 204 64
@reboot sleep 50 && sudo chown root:dialout /dev/ttyAMA0
@reboot sleep 55 ...
I've set up a cron job to deal with it.
@reboot sleep 35 && rpi-rw
@reboot sleep 40 && sudo rm /dev/ttyAMA0
@reboot sleep 45 && sudo mknod /dev/ttyAMA0 c 204 64
@reboot sleep 50 && sudo chown root:dialout /dev/ttyAMA0
@reboot sleep 55 ...
- Mon Feb 19, 2024 11:07 am
- Forum: Pi-Star General Support
- Topic: v4.2.0 Dashboard Failing
- Replies: 8
- Views: 7074
Re: v4.2.0 Dashboard Failing
If you could, that would be good.
I've left it "as is" for the time being, as now the dashboard is showing no DMR or YSF services running, and none of the pi-star logs are accessible. I think the services thing may be related to the paralell port permissions thing that I saw on here in a different ...
I've left it "as is" for the time being, as now the dashboard is showing no DMR or YSF services running, and none of the pi-star logs are accessible. I think the services thing may be related to the paralell port permissions thing that I saw on here in a different ...
- Sun Feb 18, 2024 6:04 pm
- Forum: Pi-Star General Support
- Topic: v4.2.0 Dashboard Failing
- Replies: 8
- Views: 7074
Re: v4.2.0 Dashboard Failing
PS,
If you want to dive in via SSH and have a poke around, I can always supply IP and password if you DM me
J
If you want to dive in via SSH and have a poke around, I can always supply IP and password if you DM me
J
- Sun Feb 18, 2024 6:02 pm
- Forum: Pi-Star General Support
- Topic: v4.2.0 Dashboard Failing
- Replies: 8
- Views: 7074
Re: v4.2.0 Dashboard Failing
I've just upgraded to v4.3.0 (fresh install on 32GB SD) with full updates and FS expanded and have run in to the same problem.
I wonder if it is due to a capacity issue? I've tried to make a backup copy of the mmdvmhost logfile in /var/log/pi-star folder, and get the error that there is no free ...
I wonder if it is due to a capacity issue? I've tried to make a backup copy of the mmdvmhost logfile in /var/log/pi-star folder, and get the error that there is no free ...
- Sun Feb 18, 2024 12:02 pm
- Forum: Pi-Star General Support
- Topic: v4.2.0 Dashboard Failing
- Replies: 8
- Views: 7074
Re: v4.2.0 Dashboard Failing
Hi Andy,
The dashboard is stuck at 22.27h on 17/02
I can read the MMDVM log for 17/02 in it's entirety, but reading the log dated 18/02 gives an error. Below is the output for the latter half o 2024-02-17 22:26:51.319 YSF, received network data from MW0HMV to DG-ID 0 at FCS235-89
M: 2024-02-17 22 ...
The dashboard is stuck at 22.27h on 17/02
I can read the MMDVM log for 17/02 in it's entirety, but reading the log dated 18/02 gives an error. Below is the output for the latter half o 2024-02-17 22:26:51.319 YSF, received network data from MW0HMV to DG-ID 0 at FCS235-89
M: 2024-02-17 22 ...