Local area network only ASL3 Configuration with a few nodes Help

Archive
61

Great… i suppose this is basically the method i’ve been using in all of my configs and its current state.

1000 = radio@127.0.0.1:4569/1000,NONE
1001 = radio@192.168.10.11:4569/1001,NONE

62

You stated NOT to worry about the node configuration until “later” As i wanted to stay on point and not do anything to mess the process up i wanted a definition on when “later” was…that is all.

63

I’ll state one more and last time, you are trying to mix in random Internet instructions from HamVOIP and guessing at configurations and that’s not going to work - you need to approach your build objective-by-objective… Having IAXRpt working and transmitting out of a USB fob but not the basics of a node setup means whatever configurations you’re doing are not correct.

From a clean configuration and copying NOTHING you’ve done before:

  1. Do a basic setup on each node using asl-menu. You can setup private node numbers using the menu just fine and it skips the ASL authentication parts. Make your nodes half duplex.

  2. Follow the setup for SimpleUSB tuning and make sure that your HT works. You should be able to key, unkey, and hear the telemetry tone. If you want to enable parrot mode for audio testing, temporarily put this right after the line that says 5 = macro:

    88 = cop,55

    Then when you transmit into the node, your audio will be recorded and played back. You will need to key in DTMF *88 each time. Also see my previous guidance on why your DTMF decoding doesn’t work. You can also trigger it from the CLI using rpt cmd 1000 cop 55 0 before each transmission.

  3. After you have a complete half-duplex node setup, conect the two nodes using the rpt.conf entries that Mason has given you. You only need to add the opposite node’s information next to your node’s information. Test your linking and unlinking. You should be able to key up one and hear the other. Use the debugging I’ve provided for better log output.

  4. After you have all of that working, add an IAX context for your IAX-type connections. This should be done in an entirely separate context within iax.conf.

64

OK, then hopefully this makes more sense with the clarifications added to step 2.

65

Thank You for the detail. I will do exactly this. appreciate the guidance.

66

Thank You very much for these steps. I had to get with allscan on the specific usb settings, but the parrot mode test is fully functional for the first time and sounding good.

I’m going to start on the 2nd node setup now and i expect all will be good.

image
image1561×424 48.4 KB

67

I was working on the second node and already having issues. I’m wondering if my hardware may be causing some of the issues.

The node 1000 is a raspberry pi 4B and have it fully working at this moment.

I started on the 2nd one (it is a raspberry pi 3B) and am working on all of the usb tunning. I’m not having any luck with your above *88 or rpt cmd 1001 cop 55 0 at this time.

I’m carefully looking line by line to make sure there was no differences and i found what is circled in this screen shot.

I’m just wondering if this could be some sort of bug with the 3B as I’m duplicating the same actions to get this other one going.

I’m doing all edits from the cli with nano (someone told me not to use the editing feature in asl-menu)
I guess the biggest question will it corrupt something if i manually put that info in the rpt.conf.

Or if you can tell me what normally writes that information maybe i can track it down.

image
image1324×967 53 KB

I’m not getting any output from debug with a *88 from handset or from the command rpt cmd 1001 cop 55 0 from the cli

this line may not even be related to my issue but is the only thing different from my 2nd setup.
I know you mentioned this earlier, but I don’t think i manually entered that and it was just there…

68

Your first node was 1000. Is this node supposed to be 1001? If so, then it looks like you setup this node with the wrong #. You can easily change the node # with asl-menu / node-setup.

69

i know that. i took this screen shot on the first one. My point was…on the working unit its showing this info. On the one i’m working on it does not have this info. Thats all.

70

My apologies. You circled differences that I thought you were concerned about while at the same time commenting about your second node. I made the assumption that you were showing the configuration file that was not working and questioned why your second node was referencing the same node # as your first node (also assuming that your first node was 1000).

Does your 2nd node show the correct node # (1001?) in those same lines?

For your 2nd node, what does work? what doesn’t work?

IMHO, you should use asl-menu / “Node Settings” for the basic configuration (e.g. creating the initial node, SimpleUSB tuning, changing the duplex type, … and if needed any node # changes).

If you need to make additional changes (e.g. adding the references to your other “local” nodes) then you can use the asl-menu / “Expert Configuration Menu” options or your favorite editor.

71

Yes Sir, the 2nd node now shows the same lines and with the correct node (1001)

So at this moment. I’ve configured this second node with the exact same steps as the working node(1000) I’m starting to think i may have some sort of hardware issue but not sure yet.

while in the usb tune i can send tx test tones and while viewing rx signals i’m seeing the signal reach the node. My cos signal on my uri100 is lighting up on tx from the handheld which is expected.

I’m not getting any debug output during a tx or anything obvious.

I can connect the 2 nodes together with the rpt cmd NODE ilink 3 NODE with no errors.
the only issue right now with node 1001 is it will not parrot. neither with the cli command or with dtmf command…

72

With the exception of the type of Raspberry Pi, are you using the same hardware for your two nodes (radios, URIs, etc) ?

73

Yes Sir, other than the Pi the rest is identical. I am going through each line of code in the relevant files and am finding absolutely no variances between them.

Still have a bit to go but if i can’t find the issue I’ll have to quit with this pi 3. I have some micro pc’s i bought but waiting on the dell display port cable to arrive to get started on that.

I’m going to swap radio’s and Uri’s on the working system also but might have to wait until tomorrow to try that.

I’m also going to swap power supplies as i’ve seen strange things happen with these cheaper pi power supplies not providing enough power to the usb port causing unexplained issues before on other projects not related to radios.

Aggravating for sure! lol

“Added later”

can someone tell me why this is red? is this a bad thing or just doesn’t matter.

image
image831×508 15 KB

Had a little progress but still issues. at least now the node is receiving the dtmf and echo commands but just not playing back. I’m getting this in the debug:

-- Hungup 'DAHDI/pseudo-1391453219'
-- Hungup 'DAHDI/pseudo-2074623548'
-- Hungup 'DAHDI/pseudo-767724991'
-- Hungup 'DAHDI/pseudo-1517159927'
-- Hungup 'DAHDI/pseudo-584903805'
-- Hungup 'DAHDI/pseudo-1828417569'

[2024-11-28 01:28:18.802] WARNING[893]: app_rpt.c:5752 rpt_master: rpt_thread re started on node 1001
[2024-11-28 01:28:18.802] WARNING[1814]: channel.c:751 __ast_channel_alloc_ap: C hannel allocation failed: Refusing due to active shutdown
[2024-11-28 01:28:18.802] ERROR[1814]: chan_simpleusb.c:2664 simpleusb_request: Channel 1001: Unable to create new usb channel
[2024-11-28 01:28:18.802] ERROR[1814]: app_rpt/rpt_bridging.c:231 __rpt_request: Failed to request SimpleUSB/1001
[2024-11-28 01:28:18.802] WARNING[1814]: app_rpt.c:2845 disable_rpt: Disabled br oken repeater 1001

74

Thanks all for the help.

I’ve had some good luck on these configs. I’m still dealing with some issues but will continue after I get a replacement for this Pi 3B.

I have a few Dell Wyse micro’s I’m going to work on next so i can get rid of the raspberry Pi’s. Hopefully that will resolve the remaining issues

I also have a configured i386 laptop with asl3 running on it. I might try and throw that into the mix and see how it goes.

Happy Thanksgiving.

75

Just a quick update. I ditched that particular Pi3B. Grabbed an old laptop that was doing nothing and installed ASL3 on it.

Within 30 minutes i had it configured and working exactly how i was hoping it would work. Excellent comms between the 2 nodes currently.

Next will be a headless radio setup connected to this 2-node network so i’m looking forward to that.

Bad hardware in an unfamiliar environment is the worse.

Thanks again for all of the input. Greatly appreciated.

2 Likes