|
|
Post by VK2IDL on Feb 22, 2021 6:25:43 GMT
CPS Version 2.1 (9.1.152) DRS-300UV F136-480 Dec 24 202
I am constantly having corruption issues with the CPS. The larger the content the worse the problem.
I have quite a bit of experience in programming various DMR Radio models and have a reasonable understanding of the CDR-300 CPS operation and process. The contact list and RX Group list seem to be stable and I don't have any issues there. The problem lies with the Zone/Channel setup.
Starting from the top of the zone list and working downwards, I have 3 Hotspot zones, one FM repeater zone and 17 DMR repeater zones.
The Hotspot zones each have 35 channels to support the talk groups I need.
The FM repeater zone contains 18 FM channels to cover nearby FM repeaters.
The DMR Repeater Zones each contain 15 channels support the desired talk groups.
The problem is that once all the data has been entered, any change to any part of any zone (including just changing a zone name) corrupts part of one or more channels listed in one or more zones. It appears as though the data is stored sequentially without reference to its associated zone. Delete a channel in one zone and channels from other zones start moving about and end up in the wrong zone. Sometimes just the first 2 or 3 fields (name and frequencies) in a channel are corrupted, other times the Group Call and Contact list gets out of alignment and ends up with data from another zone.
The fact that just changing the NAME of a zone can corrupt the content of the zones that follow is horrible, yet Ive seen little in the way of complaints of this on the forums. Maybe no-one else is enter as many zones as I am.
This is a significant fault that prevents me from programming a number of these radios for members of my local amateur radio club.
See the two images below. The left image shows a working zone with channels installed. The right images shows the same zone corrupted after simply changing the name of one of the zones from "Analog" to "FM". Also editing any zone corrupts the content of the data in the zones below it.
|
|
eb3bkw
Junior Member
Posts: 70
|
Post by eb3bkw on Feb 22, 2021 18:49:27 GMT
Yes, it happens to all of us. Try the following:
When the data is corrupted, double click on ZONE / CHANNELS, and see if it solves the problem. Retevis has been notified of the problem, so they can resolve it. I use the MM7 XXX editor (sorry, I don't remember his callsign), it works very well. In my codeplug there are about 1200 channels, working OK.
|
|
|
|
Post by VK2IDL on Feb 22, 2021 23:28:38 GMT
Thanks.
I searched the forum here and the Facebook forum but found no mention of it being reported.
No, Double clicking on Zone/Channels has no affect. |
|
eb3bkw
Junior Member
Posts: 70
|
Post by eb3bkw on Feb 28, 2021 11:02:52 GMT
Use Retevis CPS v2.1.26, (9.1.170) (28/GEN/2021)
Without being perfect, it is much more stable.
|
|
|
|
Post by VK2IDL on Mar 9, 2021 0:17:16 GMT
Already using all the latest CPS and firmware versions. The CPS is OK for just a few channels and zones but anything larger fails.
I'm now using the Python script released by David M0DMP which works perfectly. I can manually edit the JSON file fairly quickly and create whole banks of channels and new zones. You just need to make sure the ID numbers are in sequence. The resulting file uploads perfectly to the CDR300 using the Python script and everything stays in its place. I finally have a relatively stable radio that I can edit easily.
|
|
|
|
Post by willywoe on Mar 11, 2021 16:37:35 GMT
Hi, I have owned this radio since July last year. A lot of people have complained about this issue in the past, myself included. I like yourself spent a lot of time building and refining a large codeplug only to come up against the Zone data issue, amongst many other little niggles. I think the primary goal of Kydera/Retevis is to sell as many units as possible, as they continually seem to tinker around the edges of the firmware and CPS issues and mainly concentrate on things like APRS modes etc. Whilst basic programming issues and operation are ignored. The cobbled together CPS simply fails to do the radio hardware justice. My experience has resulted in a radio which will no longer Transmit with any difference set between the channel TX and RX frequencies, a "BS Failed" error displaying on screen. Repeated re-flashing of the firmware and uploading various codeplugs, has not corrected this issue. As you surmised the data appears to be stored serially, so every write to the radio from the CPS results in ever increasing bizarre behaviours, due probably to remnants of the previous codeplug code being left behind, until eventually a non-recoverable error occurs. Factory flash reset programs are supplied by other manufactures to get around this type of issue, but non is available here. So.................. this radio now sits sulking in it's box. My advise is to keep any codeplug writes to this radio to a minimum, and if it's working at all, don't try to fix it until a corrected CPS and firmware become available, if ever. Otherwise it may end up like mine, unusable. cheers, Bill Attachments:
|
|
