BCD436HP/BCD536HP: Two issues

[LEH]

First and most frustrating right now, I just lost about three hours of work. I wanted to save my profile under a different name, so I clicked the 'save as' option and my Sentinel (2.0) froze. No dialog to enter an new file name, nothing. I had to go to task manager to kill the process. This is not the first time this has happened though other times it has not entailed such a significant loss of work.

Second, the reason I was making so many changes is some how my favorites list information got totally scrambled. I had entered a new trunked system in my area and was adding some additional systems in preparation for a trip next month. I noticed that systems I had previously entered for that state were missing.

Further checking I discovered I had things like Texas systems under New Jersey, North Carolina under Maryland, and numerous other glitches.

I wanted to save the old files so I could do a comparison with the files on my traveling computer. Hoping to get an idea when the scramble took place.

One thing that could be an issue though I tend to doubt it is I use both Sentinel and ProScan. I do all my programming with Sentinel then read the scanner to ProScan so I can use their print my FL option (with a bit of editing). I do not make changes with ProScan, if I did, I could easily understand how this might occur.

Though not a problem I am seeking help with. Today has not been a great day. I thought I had posted the second problem earlier today and now I cannot find it.

 

[hiegtx]

First and most frustrating right now, I just lost about three hours of work. I wanted to save my profile under a different name, so I clicked the 'save as' option and my Sentinel (2.0) froze. No dialog to enter an new file name, nothing. I had to go to task manager to kill the process. This is not the first time this has happened though other times it has not entailed such a significant loss of work.

Second, the reason I was making so many changes is some how my favorites list information got totally scrambled. I had entered a new trunked system in my area and was adding some additional systems in preparation for a trip next month. I noticed that systems I had previously entered for that state were missing.

Further checking I discovered I had things like Texas systems under New Jersey, North Carolina under Maryland, and numerous other glitches.

I wanted to save the old files so I could do a comparison with the files on my traveling computer. Hoping to get an idea when the scramble took place.

One thing that could be an issue though I tend to doubt it is I use both Sentinel and ProScan. I do all my programming with Sentinel then read the scanner to ProScan so I can use their print my FL option (with a bit of editing). I do not make changes with ProScan, if I did, I could easily understand how this might occur.

Though not a problem I am seeking help with. Today has not been a great day. I thought I had posted the second problem earlier today and now I cannot find it.

I ran into something similar when NXDN first became available. Initially, at first release, neither Sentinel nor ProScan supported the NXDN format. However, I entered one of my systems of interest (SWRCC) manually through the keyboard. I also saw comments in one of the initial threads that you could use Notepad++ to edit & modify a favorites list. I used that to tweak my initial NXDN systems, and add to them.

Later, as ProScan was updated to handle NXDN, I read the scanner into it, then began to flesh out my new systems. However, after I wrote that back to the scanner, and later 'read' the programming into Sentinel, I noticed the same jumbling of data- systems in the wrong Favorites list, scrambled data, I think the basic cause was that Sentinel does not use the Favorites list name for the individual files. Instead, they are numbered. And, apparently, reading the radio back into Sentinel, including the new NXDN systems created either in the scanner manually, or in ProScan, caused the Sentinel files to be overwritten with the new information, but Sentinel still retained the same 'names' for each Favorites list file number, even though those had been updated in ProScan. Fortunately, I had not written the updated information to all three of my x36HP scanners, and was able to read the correct info back into Sentinel. I ended up having to park the NXDN file in a temp directory whenever I was writing to or reading from the scanners, until Sentinel was upgraded. I finally was then able to sync them up correctly.

 

[captaincraig44]

Sounds similar to something I posted about, but got no response to. See this: https://forums.radioreference.com/u...0-sentinel-shuffling-systems-between-fls.html

 

[TailGator911]

I do the same, program with Sentinel and read to ProScan and utilize the ProScan virtual control option, and I have not had that happen to me (knock on wood) but I will now surely check my info a little more closely. Not sure what caused it, but thanks for the heads up. Hope you figure it out and post your findings here.

JD
kf4anc

 

[LEH]

Sounds similar to something I posted about, but got no response to. See this: https://forums.radioreference.com/u...0-sentinel-shuffling-systems-between-fls.html

Craig do you have any NXDN systems/frequencies in your SDS100? Another post mentioned this occurred right after he did the NXDN upgrade. I have some NXDN frequencies (railroad conventional) in my 436.

If you don't then we can partially rule out NXDN as the culprit. Though we might want to consider if you have the NXDN upgrade in your SDS100 that it might have something to do with the scrambling.

I am just looking for the LCD (Lowest Common Denominator) between the three problems cited here.

Thanks guys for the input, every bit helps. Now to finish reprogramming my 436 and validating the FL files contain what I entered.

 

[captaincraig44]

I do have NXDN systems programmed. All have been programmed with the Sentinel version that supported NXDN and DMR. I figured it was something to do with having 140+ favorite lists or possibly having Sentinel and ProScan open simultaneously, even if just using one to actively read/write to the radio. Honesty, I've only used Sentinel once or twice since this happened because I don't want to have to go through and check every FL for errors and have to try to reconstruct them.
CM

Sent from my Pixel XL using Tapatalk