Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
588shutdown [2007/11/30 21:45] n5na |
588shutdown [2007/12/11 15:59] n5na |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Omni VII Model 588 Rig / Transmit Shutdown ====== | ====== Omni VII Model 588 Rig / Transmit Shutdown ====== | ||
| - | **From the Ten-Tec Reflector - November 30, 2007** | + | **From the Ten-Tec Omni VII Yahoo! Group - November 30, 2007** |
| The Rig shutdown requiring manual off/on to reset it, only occurs from an over current situation that is deemed to be on the verge of | The Rig shutdown requiring manual off/on to reset it, only occurs from an over current situation that is deemed to be on the verge of | ||
| Line 19: | Line 19: | ||
| Serially, the time out is 3 minutes if a subsequent transmit command hasn't been received. Via Ethernet this is 1 minute. | Serially, the time out is 3 minutes if a subsequent transmit command hasn't been received. Via Ethernet this is 1 minute. | ||
| - | The timeouts are firmware, but in the firmware there are handshakes between two threads and if one fails then transmit will be terminated by the other earlier than the timeouts. One thread is an non-maskable interrupt. So unless the HW is actually failing, the firmware should be able to shut it down now. Unless some unknown bug exists. :( | + | The timeouts are firmware, but in the firmware there are handshakes between two threads and if one fails then transmit will be terminated by the other earlier than the timeouts. One thread is an non-maskable interrupt. So unless the HW is actually failing, the firmware should be able to shut it down now. Unless some unknown bug exists. :-( |
| 73, de KI4JPL\\ | 73, de KI4JPL\\ | ||
| John Henry | John Henry | ||
