I think I found a workaround to an issue where the Manhattan finds a signal in a blind scan and writes channels to memory and after the blind scan ends, one gets a "no signal" upon trying to pull up one of the channels for a particular freq/sr. I believe it's a flaw with the ALI chip since this same situation also sometimes happens on my Openbox S10.
I found that going to the TP list and hitting the red "edit" button and changing the frequency might do the trick. On one unpublished signal, I found the Manhattan would get a lock if I changed the frequency to 1 MHz below the frequency the Manhattan found in its blind scan. I then manually re-scanned the mux using the new frequency value and the channels were written to memory and they displayed just fine when selecting that channel from the channel list.
I have only practiced it on one trouble mux so I don't know how reliable this workaround is, but it's a nice thing to have in the knowledge base if you encounter the situation of getting a "no signal" on a 24/7 service after the blind scan found it and wrote it to memory.
I found that going to the TP list and hitting the red "edit" button and changing the frequency might do the trick. On one unpublished signal, I found the Manhattan would get a lock if I changed the frequency to 1 MHz below the frequency the Manhattan found in its blind scan. I then manually re-scanned the mux using the new frequency value and the channels were written to memory and they displayed just fine when selecting that channel from the channel list.
I have only practiced it on one trouble mux so I don't know how reliable this workaround is, but it's a nice thing to have in the knowledge base if you encounter the situation of getting a "no signal" on a 24/7 service after the blind scan found it and wrote it to memory.