We've had other GPRM users with Derby Magic timers be able to get them working together, so it has been possible.
Late last season Derby Magic did make a change to their timers, upping the baud rate to 19200, instead of the 9600 baud that it had been before. So, that would be the first thing that should be checked. GPRM V13 included an update that added in support for high baud rates to the custom serial timer interface. So, if you have one of their 19200 baud timers, you do need to run GPRM V13 or above.
As there are a lot of things that can go wrong trying to get timers and software to talk to each other, I do suggest going through the Troubleshooting section of the software's help file. There are tests there, like the "Paperclip Test" that can help narrow down the problem. Often going through that guide will resolve a communications problem.
If you are still not able to get the communications working, you can contact me directly at
[email protected] with specific details of the problem and include a copy of the communications log file (DocumentsLisano EnterprisesGrandPrix Race ManagerHardwareDebug.log) as well as the full version number of GPRM that you are running.
Vitamin K said:
Wow, that's a major failing on Derby Magic's part, IMO. GPRM is pretty much the gold standard for PWD software. If I were selling a track and timer kit, I'd devote a major chunk of my time to making it GPRM compatible.
We've approached them more than once over the years about partnering together, but unfortunately they are not interested in doing so. Otherwise, we would specifically support their timers and ensure a close compatibility.
