开云体育

I recently powered up my trusty old SO2R box. It lite up the TX1 red LED which is normal, but both Green LED's were on !?! If I flipped the RX selection switch from 1 to 2, the Green LED's both went out, but I heard relays close in some of my gear as if PTT had been asserted. I tried reloading Firmware. That worked fine but that did not help with the problem. It appears that the TX and RX LED's are driven off the uP. Can I simply replace it and do a Firmware update using the Pgm Jumper? All voltages look OK inside -- 73, Mike, N1JEZ "A closed mouth gathers no feet" -- 73, Mike, N1JEZ "A closed mouth gathers no feet"

My trusty old (10+ years?) SO2R box just started sending CW at <1 wpm. No matter what I did with N1MM's or the box's internal speed control, no change in CW speed. There are 3 different DIP ICs of which there are two of two types. I swapped both "pairs" and reseated the single DIP. I then reloaded the firmware and, voila, it's back to working perfectly again! I guess corrosion had built up on the pins over the years (it is humid in SE Texas) or a nearby lightning surge had scrambled something. Anyway, the bottom line is that if you see this behavior in your trusty SO2R Box, it may not be catastrophic. These things are built like tanks in my experience. Good luck, Bob K5WA

I'm making the move (back) to a linux desktop after many years away. I've got solutions for many of my issues but finding a way to control my SO2R mini is one of the remaining tasks. I've looked at the OTRSP command set and it seems simple enough, but I'm not having any luck getting the commands to the box. If I need to send something like "RX1" to the device, is that expected to be ASCII or Hex encoded? I've attempted to just echo some commands to the serial device with no luck. Bringing up a terminal program attached to the port at n81 9600 baud doesn't do anything either. I know I have the correct port from the output of dmesg and watching the connect/disconnect messages. Any input would be appreciated! My ultimate goal was to get it working with my elgato streamdeck, which should be simple enough if I can figure out this issue. -Steve N1JFU

I obtained a spare (backup) SO2R Box+ and comparing it to my original unit I notice that the audio is say a good 6db lower when listening to radio 1 when plugged into either channel 1 or channel 2. This is only with the radio plugged into either DIN, 12Vdc and audio out plugged in and of course flipping the rx switch. Any things I should check or buy for replacing? Paul was there a chip that was universally replaced in the original buy? I think the vintage of both units is the same. Seems like I remember something about a green or white device that should be replaced (updated)? Tnx, Mike W9RE

Paul, on Nov 11 I ran into this situation: I was setting up vm (dvr voice messages) on two K4Ds on Saturday. Using TRLinux and a YCCC SO2R Box + (this right probably only applies to two or three stations). VM were set up and I was testing what would stop a vm if I got a response on a radio. Normally an Alt-R would do this and it did fine. So I am remembering how if you hit the PTT (foot switch) with a K4D that will stop a vm. Well I tried that. What happened had me puzzled for 1/2 an hour. I lost audio on both radios. I was in Test Mode and when I hit M1 on either radio the radio would swing wildly in/out of transmit but I could not hear any audio (monitor was turned up) and still no rx audio. I tried rebooting the radios with the same thing happening. Finally after a while I found that the PTT was held low by my SO2R Box to both radios. Rebooting the SO2R Box fixed the problem. Now tonight Nov 14 I had this happen: I was in a little bit of a hurry tonight getting things turned on and then ran into a big problem. Whenever I would key a radio they would go into transmit and not come out. I ran into this thing last week before the SSB Sprint and corrected it by rebooting the SO2R box but this time it didn't work. I guess I will have to reflash my SO2R box W6FB replied: I had this issue with my SO2R+ box a few weeks ago. I believe it was caused by killing power on the box instead of flipping the front panel power switch to off. The solution was to bring up the SO2R Utility and reset the box, which resets the eeprom to default values. It worked until the next time I powered it off by killing the main +12V supply. I again reset the EEPROM with the utility and it has worked fine ever since. I learned my lesson, I now power it on and off with the front power switch, then when it is off, power off the main 12V supply. 73! Jack,W6FB So before I reflash is there anything I should look for using the utility so I can pinpoint what happened? I have always just killed power and I have not used the switch on the SO2R Box. Thanks, Mike W9RE .