Database version mismatch

Post Reply
fahdbt94
Posts: 21
Joined: Fri Nov 10, 2017 6:03 am

Database version mismatch

Post by fahdbt94 »

I recently added a few new sensors to the SDU database,
followed it up by compiling the rules,
Converting the DB and uploading to the Loop controllers and the CPU.

what happened afterwards is very strange, when I open the communications window
the bootstrap and code versions are all matched up (5.20) but the database version is at a mismatch. (see attached pic)
the SDU version is 1.00 and the panel version is 0.00.

I'm also getting a CPU database out of sync alarm, i'm guessing its due to this version mismatch.

Thoughts?
Attachments
loop 3-4 database mismatch.rar
(46.32 KiB) Downloaded 412 times
thevezman
Posts: 2
Joined: Mon Feb 12, 2018 12:42 pm
Location: San Francisco, CA

Re: Database version mismatch

Post by thevezman »

If the SDU Versions do not match down the board, you'll get all kinds of issues. Revision numbers do not matter between CPU and loop cards, but Versions do. Open the database with the revision that every other card has, and download to the cards that are out of sync.
fahdbt94
Posts: 21
Joined: Fri Nov 10, 2017 6:03 am

Re: Database version mismatch

Post by fahdbt94 »

when you say 'download to the cards' you mean the loop controllers right?
like instead of downloading 'ALL' i should do this individually for ever card and then the CPU?
Jorgegronemeyer
Posts: 1
Joined: Tue Feb 20, 2018 9:07 pm

Re: Database version mismatch

Post by Jorgegronemeyer »

you must upload mapping in te loop with mismatch , fix the changes with the expected and actual database, and download the database to all cards, including Loop controllers and CPU
sorry for my english :C
fahdbt94
Posts: 21
Joined: Fri Nov 10, 2017 6:03 am

Re: Database version mismatch

Post by fahdbt94 »

Your english is fine, no worries.

But addressing the problem at hand, I have done exactly that, but the database version is still at 0.00.
Anything else I can do?
Post Reply