GWR Greg Posted September 9, 2018 Share Posted September 9, 2018 I have just run a read all CV's for a Zimo MX645 decoder. It correctly identified the decoder and cvs to 253 as expected but from the next CV, 260 onwards it read the CV but the "status/string" column show "could not verify". Anyone know what is going on? Link to comment Share on other sites More sharing options...
96RAF Posted September 9, 2018 Share Posted September 9, 2018 Does the decoder support CVs above 260? Have you set the full CV range 1-1024 or is it more restricted.Usually the ‘could not verify’ pops up after a bad write attempt or of you tell it No after a bad read, whereupon it puts up that flag and goes on to the next CV read. If you say Yes it will try to read the same CV again and may again fail.Rob Link to comment Share on other sites More sharing options...
GWR Greg Posted September 9, 2018 Author Share Posted September 9, 2018 Yes and yes. The read has been allowed to run unhindered, so no intervention from me. Link to comment Share on other sites More sharing options...
96RAF Posted September 10, 2018 Share Posted September 10, 2018 Fresh out of further suggestions Greg, sorry.The decoder is obviously in the RM database but maybe not fully defined.Report it in from RM to see if HRMS has any advice about why it happens.Rob Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.