What is the voltage when NOT receiving a signal? -k9dc

Looks like hardware. Like Dave said it's just a logic circuit. There is a drawing on line of a home brewed version 2 board, BUT it will only give you an idea of the operation.. since version 3 uses

Version 3. Purchased 2016. & I have tried running a jumper to ground from the COS pin with the jumper in the low position. No change. Can not light the COS light

At this point, much more not working then working. Unit has been in service same radio, same location & power supply etc for almost 3 years I have added a ground from the body of the node (connected

+Pin voltage from the radio has no change between working and not working. roughly 4 - 4.1 volts when recieving a signal.

Very rare that it would be intermittent like this. Next time it acts up, I would check all your GROUND between the radio and the board. Often if there is a bad ground, the voltage potential can be too

I agree it's not port forwarding... I would take the cos line and remove it from the db9. Solder a wire to the cos pin on the db9 and connect it to the cos signal from the radio. I would use a

Port forwarding (or lack of) isn't going to affect the hardware. I think you may need to be a little clearer on what is going on with the COR. With just the same radio, what does

Ralph, did u change service providers and did u do the port forwarding through the new isp?

I have an issue. If the node is powered down for extended time, I can turn it and the radio on & all works normal. After running for some time (sometimes for a couple of hours sometime a couple of

Mick, DaveC used to do that with early generations of his embedded node, years ago when flash was very expensive. But with improvements in high availability (reliable) flash, he no longer does that.

Hello Group, While I am thinking about updating my node software, I am also thinking of upgrading my hardware. With the new Raspberry Pi4 that has 4 gigs of ram, I am wondering .

David Cameron - IRLP wrote: I thought this would be fun to calculate, kinda back-of-envelope but with citations... Raspi power consumption depends slightly on what model you're using and how hard

David Cameron - IRLP wrote: HAH! That's kinda hilarious, but you could still do... SOXVER=$(sox --version) 2>/dev/null case "$SOXVER" in   "") sox --options-for-versionless-sox ;;   *v14.*) sox

Yes, but the old version if sox doesn't have a version flag.... It really is not an easy fix either way. Dave

David Cameron - IRLP wrote: You don't technically care about the *OS Version* though, do you? You care about the *SOX version*, so perhaps you would prefer to do something safer like... SOXVER=$(sox

I forwarded your email to him. When he replies, I'll get him take picture of screen and ship it to you. I thought too that would be a strange change to make. Don

Yes, you either need to reboot, or wait 24 hours since the last update. If you're in North America it should happen sometime overnight.

Is there anything I need to do such as reboot? So far no change on 3024,3212. Jim WH7CD created with care by Cold Duck

I have made a new update to wavplay to cover the "old" style embedded nodes that run slackware. The problem is now I am using an OS detection routine to determine (hopefully) which version of sox