I have installed ASL3 and as expected, the developers have taken it to a completely new level. Well done guy’s…
I don’t suppose there is any support for outputting fields to a Nextion screen is there? I have had a look and can’t see anything obvious. Such a shame when the likes of PiStar has had it going back years.
A great update none the less…
Great work, all installed, like the template rpt.conf so much better!
I was used to the log (connections, asl etc) views available on supermon, is that dsahboard compatible with ASL3? I’ve had a look around the cockpit dashboard in case they could be found there, but either I missed them or they aren’t.
Thanks for the hard work all.
Ed, MW0KEC
In Supermon should work with ASL3. We provide instructions for enabling astdb. Supermon (and other apps) should use that one in order to not duplicate the traffic.
see
If you’re on the ASL3 Rpi version I’m sure you noticed it has Allmon3.
Important note Supermon and other tools that need access to astdb.txt should use the astdb service we provide rather than installing their own cron, etc.
so after setting up several pots of flaming hot coffee and grabbing several packs of Chesterfields (Len WB2HKK will probably get that joke) I dove in. Initial impression is still that using the Pi installer should not be needed. But that aside here’s what I found:
Password didn’t take every time (re-imaged microSD for the Pi 4 or 5 times today)
The menuing slows stuff down a lot but then editing the .conf files isn’t as straight forward as it was. Still unsure of them, like rpt.conf. It shows a long config with all the crank-handles on stuff then for my node number just shows a couple of lines. What can and what cannot be edited…??
The age old audio “hole” issue I’ve been bugged by for a decade(or more) seems gone. Yay!
Figured out how to make iaxrpt work, there’s a line needed in [iaxrpt] to make it work.
Why are all of the commands commented out? (901, 902, etc)
Finally the one that is keeping me from using it, remote base. Like ASL 2 this seems to not be there. It is in the rpt.conf file but adding remote=ft100 and ioport=/dev/ttyUSB0 make asterisk not respond. I put those lines under my node number (2428 in this case)
in the past with a remote you’d have a line in your node’s settings: functions=functions-remote but which part of rpt.conf would that go in? The part under [2428]?
Some of this I can probably figure out from the source for app_rpt.c if someone could point me at it. I poked around a while and cannot find the source code.
Bottom line: while more complicated to setup (gui, menus, etc) it does seem to control a repeater and the audio problem seems fixed. Nice work.
But the remote base…
GeorgeC W2DB
The short answer is that everything in the template, [node-main](!), applies to ALL of your nodes. The variable settings in your node, [12345](node-main), defines what’s “different” for this node only. If you are looking for a variable, first look to the node. If it’s not there, look in the template.
My suggestion would be to leave the templates alone and add only what’s needed to the node.
Yes, adding “functions=functions-remote” under [2428] would make that change for node 2428.
Have a look at AllStarLink GitHub
Congratulations Dev team, great work!!!
I have a bit of a problem, I burned 2 SD cards using Raspberry pi imager with different Nodes. Why cant I access my node_ip.local or https://my_ip:9090. Site cant be reached " refused to connect. But I can connect using putty.
One more thing, it does not register to allstalink org even thought rpt_http_registration.conf show correctly the Node and passoword. I have to edit iax.conf to make LIVE.
Well I tried the functions thing but the remote does not work. I did find the source code and don’t see the data rate setting anywhere.
So what am I doing incorrectly? In my node stanza I included functions=functions-remote
remote=ft100
ioport=/dev/ttyUSB0
And adding Y on the end of:
[nodes]
2428=radio@127.0.0.1:4571/2428,NONE,Y
So what did I get incorrect?
Adding that remote line makes allstar not work.
GeorgeC
OK, found the data rate info, which appears to be correct. But asterisk is not going into remote mode
ALSO, I add under my node number functions=functions-remote. Still only decodes regular functions like that line isn’t there
node_ip.local is not correct. Should be just the ip address, no .local. But that’s probably just a typo here in the post.
Does port 80 work with an IP address?
Hostname discovery does not work across LAN segments. Is your network flat?
The http registration string is exactly the same as for IAX. Could you put http registration back and type rpt show registrations and let us know what you see?
Tremendous work by the AllStarLink team. Color me amazed.
I am testing by installing on a Debian 12 base in a VirtualBox VM. The manual says the node update service and allmon3 are included in the installer but both of those are absent when I do my install following the instructions in the manual. I’ve done it three times, from scratch, into three new VMs, with the same result.
I can manually install the node update service and then that works. But when I manually install Allmon3 I cannot get it to work right. Sometimes I can get it to show up in a web page, but it doesn’t show icons or any other information.
I guess all I’m pointing out here is that the manual (at Debian 12 Install - AllStarLink Manual) says allmon3 and asl3-update-nodelist are installed as part of the ASL3 package, but that is not my experience so far.
You are correct. The manual “should” say that the allmon3 and asl3-update-nodelist packages are “optional” and may also be installed. I’ll work on updating the manual.
Thank you. Next up I’ll try to install on real hardware instead of a VM. Again, tremendous work by the team! Kudos!
I think what Kyle is referring to is the node limitation created by faulty hardware on the original Raspberry Pi 4 that doesn’t allow proper enumeration of USB connected devices. The latest version of the Raspberry Pi 4 supposedly has that corrected. I don’t believe ASL3 can correct this issue on the “bad” Raspberry Pi 4’s, and they are still likely to have a single USB connected node limitation.
You’re right, it reads that way. I’ll fix the wording.
I have a node running ASL2 with Supermon2 so I thought I would give this a try. It is a RPi4, 4 GB and RA-40. I’m a CLI type so the web base was challenging but it looks nice. I used Freddie’s video to make a cheat sheet / QSG which I am welcome to share.
I wish I could say it works great but… it does not. After the 3rd install I got it working with no obvious errors on the computer.
However, after I ran Allmon3 once, it died. When I reboot, it registers and looks like it is working but Allmon3 still does not work. Having to do a complete install each time I run Allmon3 does not cut it.
When Allmon3 kills ASL3 I see “ASL3_Died” at the Asterisk CLI.
I also get frequent web connect failures at all times.
If there is any other info I can supply let me know.
Roger
WA1NVC
I’m not sure I understand how you’re tying Allmon3 with “ASL3_Died”. However from your Asterisk logs it looks like you have a configuration error with the channel driver for that node number. Can you attach your rpt.conf and simpleusb.conf files. Also the output of tail -n50 /var/log/asterisk/messages would be helpful as well.
Let me try to be more specific. I tried to attach some screenshots and did not succeed.
When I first got ASL3 running, I could see the node had registered, the HB was flashing and the PTT was working. When I tried Allmon3 the first time all seemed to be well.
On the second use of Allmon3, I tried some of the commands like “show node status” or play local ID. At some point, all I got was a flashing large dot and it was obvious Allmon3 was hung. I also noticed the HB had stopped. Being a CLI guy I went to the Asterisk CLI and saw the Channel SimpleUSB error. (ASL3_Died was the label on the picture.)
If I reboot, ASL3 starts working again, there are no messages at the Asterisk CLI, and the node registers and appears to work. When I log into Allmon3, none of the commands work; just the flashing large dot…
i.e. Allmon3 did something to break ASL3 temporarily but it broke Allmon3 permanently.
I hope this is clearer.
BTW, I have no idea why I get these frequent “cannot connect to server” messages and have to go for a second or third try. This is on my local LAN. I’ve never seen this with Allmon or Supermon using the same hardware and network.
I have some other questions and concerns but let’s get this fixed first.
Are there any errors in /var/log/asterisk/messages that say more than what you showed or anything at the end of dmesg. That almost sounds like maybe there’s an undervolt causing the sound fob to lock up?
Well, making functions = functions-remote does not map those functions. It still responds to the standard functions like *3 and *1… but what about remote = ft100, etc. That makes app_rpt stop. What is up with that. How do I enable the remote base stuff? I see it in the source code. But it sure doesn’t work.
GeorgeC W2DB
The remote base code was difficult to non-functional in ASL2. I never heard of anyone getting it working for anything other than Xcat. We’ve not touched the remote base code other than to maybe clean up obvious errors. But no one has tested it. So don’t expect much different of ASL3 in this regard.
On the positive side, ASL3 code has be reorganized to be easier for developers to work on parts of they are interested in. Maybe some developer will take an interest.
