forum.pistar.uk

Problem solved with version 4.2.1 everything seems to work correctly. The Nextion monitor also returns to display the information that had previously disappeared.

Inviato dal mio SM-G955F utilizzando Tapatalk

Tried version 4.3.0 but encountered the same problem as 4.2.0 (while 4.1.8 works correctly). After preparing the SD and reloading the configuration it seems to work well, but after completing all the updates and applying it in the configuration without actually changing anything the MMDVM modem is n...

It would be a good idea to be able to add this option for everyone without having to add it manually and be managed directly from the panel. Nowadays many YSF reflectors are multistreaming and use DG-IDs for management. Furthermore, for radio links it is a sort of back to home on these. reflectors w...

After the latest updates a strange thing happens on version 4.2.0 (which does not happen with 4.1.8) and that is after having entered the configuration to make some changes to the configuration then by giving apply the MMDVM card is no longer seen by MMDVMHost and even by issuing the sudo pistar-fin...

Actually everything is working properly now thanks for everything.

After new tests and attempts we realized that the problem comes from the start of the dgidgateway which conflicts with ysfgateway so we tried to change the communication port in the dgidgateway configuration file so that it no longer communicates with ysfgateway and in this way it seems everything w...

@reboot sleep 180 && sudo systemctl restart ysfgateway.service If this turns out to JUST require YSFGateway to wait longer before startup, you can edit /lib/systemd/system/ysfgateway.timer and set the timer to a longer value. I tested this solution but it has no effect. For now the only way...

I will also do this test, however from the logs it seems that MMDVMHost works regularly in the log I see all the steps and by doing a test on the ports I see the passage from the MMDVM port towards YSFGATEWAY but I do not get any response from the gateway when it blocks it no longer accepts anything...

Unfortunately the problem has not yet been resolved, we are waiting for it to be resolved. While waiting for the solution, we made a change to the Pi-Star startup by forcing a restart of YSFGateway after 180 seconds from system startup by adding this line in the crontab: @reboot sleep 180 &&...

I tried but it doesn't work, the problem remains.

For now the only solution is to work around the problem with the temporary solution that has been identified.