I am not sure if it is an R1 issue or ASL3 issue, however on my node which connected as half duplex to Yaesu FT-8100 using R1-2023, PTT is not getting triggered even though status shows up as Keyed and R1 tx light turns on. I am able to copy my voice on other nodes perfectly but do not receive anything on my handheld from the node radio (except for a brief click).
I looked into PTT setting which is set to ground, I also explored usbradio.conf but couldn't get it to work either and it behaved in a similar fashion.
Manual for FT-8100 shows data pin connections for 9600bps and 1200bps, so if it is a physical connection and that is the solution, I can swap the wires between those 2 pins. Manual link is provided and data pin connections are on page 21 Data Jack Pin Connections - Yaesu FT-8100R User Manual [Page 21] | ManualsLib
If anyone has had any experience with this please do let me know.
I am not familure with the R! but I would say check the 'input to the device and see if you are getting expected.
If inverted, you can invert the logic in the simpleusb/usbradio config file.
But as you are talking about data connection, what exactly is the purpose of this rig on ASL
Is it a freq agile remote base ?
You really do not need a data connection unless for that purpose.
I have selected carrierfrom = usbinvert and CTCSS is set off in simpleusb.conf. When carrier is not inverted it starts txing spuriously. I am operating it as a half-duplex node.
R1-2023 is the URI that I am using to connect the radio to node PC. I have had it successfully connect using the relevant cables to Motorola GM338. To connect FT-8100 to it, I am using the specific cable thta plugs into the URI and the radios port. R1-2023 image
RX is great, as in when I tx on my handheld, the node radio FT-8100 receives the audio and sends it across very clearly to all connected nodes.
The issue is that audio originated at the other end does not get out of the URI to the node radio. I have tested that the URI is working by swapping node radio with another GM338 and that works as expected.
The 9600/1200 is a guess and I was hoping maybe someone who understands this might be able to shed a light on whether it is relevant in my case. The manual tells us about the baud rate but that is in relation to a Terminal Node Controller (TNC).
What else could I possibly check or where should I probe my multimeter prongs in to get useful information.
Could you better explain this.
As written, it says to me the the TXr is outputting stray signals, which by themselves can be parasitic and collecting on your wires.
Perhaps you meant sporadically
The data connection is not used or required by ASL 'UNLESS' you are setting up a frequency agile remote base and would use the serial port for tuning.
(CAT commands)
Either way, I would not connect them until you have audio and logic correct.
You need to verify logic of cos and ptt.
check the lines while disconnect from the URI to see what is actually used by the radio,
then adjust per software settings in documentation.
You say you are using a R1 URI,
It should have provided some documentation on proper set-up of it's logic to radio.
And stated the logic output for the USB interface.
Once you know that, you can adjust the parameters in ASL to match.
Is there documentation on the web ?
Just as not all radio's are not the same, Not all URI's are the same. It is not plug and play.
Thank you! I will check each pin to see whats up with it and share here.
R1 documentation has provided instructions and I have implemented them accordingly however it is possible that this yaesu model is not the same as other models and possibly uses different pin configuration.
As for the data connection, it is basically using the data port for connecting URI and radio and as you said it, it might not necessarily be using the data pin but just the gnd, cos, ptt pins for operation without having to connect a direct line into the pcb. There is just 1 port on the back of the radio.
The "sporadic" (TU) tx happens only when usbinvert is changed to usb.
Thanks again! I'll post my findings as soon as I am done testing.
After a lot of probing and testing, I have some data which might help with exact pinpointing of the issue.
carrierfrom = usbinvert
ctcssfrom = no
ptt ground
COS is working fine. It is around 60mV at idle and when i transmit from handheld, it goes up to 2.7V when connected to URI. When disconnected from URI it is 60mV to 4.5V.
PTT voltage is at 4.8V idle but goes down to 0V when I transmit from handheld with echo on or flash tone.
Still, RX is perfect. TX is not registering anything and PTT is not trigerring. Echo doesn't even show PTT keyed but URI light is working fine i.e. red on expected tx blue on expected rx (not sure if ptt shows keyed in echo normally).
PTT triggers for a few milliseconds like a short tailsquelch or roger tone. I tried inverting logic to usb instead of usbinvert and it would constantly remain on PTT. I also tried PTT open and it would also remain in PTT mode.
Do let me know if there is something else that needs tweaking, whether in software or hardware.
Your PTT line may need a buffer transistor.
From your description, if I am reading it well, kinda says that more current is being drawn to activate the ptt that the uri can supply.
0v active is normal for a PTT line. But there are exceptions.
You should be able to short the ptt line to ground on the radio, with the uri disconnected, to verify the line works in this manor.
You will not necessarily measure a voltage on the radio ptt line if you are checking the raw logic.
Not familiar with the radio myself.
Hi @Mike! Thank you, and yes when i short the pin to ground, radio transmits. I thought maybe while PTT is triggered in this way, the audio from node echo or other connected station would pass through however node radio stops tx when uri red light for tx gets on.
URI has a red wire for 12V (probably for auto on ignition connection, which i have connected to my 13.8V power supply). I tried both with and without that, but issue remains the same although COS active level voltage changes.
What kind of buffer would you suggest? Any guidance would be greatly appreciated.
Thank you @N8EI, I checked and there was no connection however I had also reached out to BH7NOR who makes these and he told me that it is by design as it is isolated by a photocoupler.
Before he answered, I had read your response and checked that there was no continuity between data port jacket on pc side and data port jacket on radio side.
I connected both data port outer sides and got some activity on both RX and TX, however TX would break in between transmission on echo. I put radio to low power and it became somewhat better before stopping echo altogether. Asterisk would restart as well.
I also made a direct CM108 fob with a 2N2222a transistor (thank you @Mike) for it and connected it which also gave me echo response but as soon as someone on another connected node would tx, there would be a short tx burst and then nothing else (also no more echo).
The same fob on a Kenwood TM-V7 worked perfectly although the R1 would not work with that radio as well.
Settings were confirmed to be correct as per BH7NOR's instructions.
