Menu
▾
▴
dgtnix-devel
|
From: Random P. <net...@gm...> - 2011-04-14 10:12:42
|
I started a new post, due to to message being over 40k and no one could read the topic in the archive. A status update, I am currently writing some software that simulates the DGT eBoard to help me write drivers for an ipad/iphone. So far the board is detected and clock are detected a long with the clock version. I have been using the DGT low level driver and dgtnix for working my way through this, I currently do not have a DGT eBoard and still am looking for someone with a DGT eBoard and the DGT XL clock to capture data. I would recommend http://sourceforge.net/projects/usbsnoop/ here is a simple guide http://www.jespersaur.com/drupal/book/export/html/21 Anyways, I thought I was correctly sending data to set Mode 23, but after I have been getting no where I went a wrote a quick simple app the uses the windows driver to use all the API functions and output data. I then did a call to _DGTDLL_ClockMode which always returns 0, and should return 23. Here is the data I am sending 0 1 2 3 4 5 6 7 8 9 8D 00 0A 0A 0A 09 0A 1E 0A 00 // clock version 8D 00 0A 0A 10 01 20 00 23 00 // ready for display 8D 00 0A 0A 10 0A 20 00 17 00 // Mode 23 8D 00 0A 0A 10 0A 0A 64 0A 00 // Mode 23 This is just going by what is in the low level driver. I am not really sure when Mode 23 is set on a normal game. If anyone has any documentation on the board to PC protocol that would be helpful also. |
|
From: Jan K. <ja...@dg...> - 2011-04-14 10:22:12
|
Hi Random, All info on our board protocol is on our DGT website, see: http://digitalgametechnology.com/site/index.php/Table/Developers/ and http://digitalgametechnology.com/site/index.php/Developers/View-category.html Mode 23 is a mode on the clock to show all information that is sent by a program, e.g. a chess program, to the clock via the clock messages. The other 22 modes are game clock settings (see the manual of the DGT XL) and can only be read out from the board. What other information are you missing? The board driver not returning 23 might be a bug in the driver, I should check that. With kind regards, Met vriendelijke groet, Jan Krabbenbos Software Development Phone: +31(0) 53-4305195 Fax: +31(0)53-4329365 http://www.dgtprojects.com visit address: Hengelosestraat 66, 7514 AJ Enscheded, The Netherlands mail address: PO Box 1295, 7500 BG Enschede, The Netherlands >-----Original Message----- >From: Random Persons [mailto:net...@gm...] >Sent: donderdag 14 april 2011 12:13 >To: dgt...@li... >Subject: [Dgtnix-devel] Sim Info > >I started a new post, due to to message being over 40k and no one >could read the topic in the archive. > >A status update, I am currently writing some software that simulates >the DGT eBoard to help me write drivers for an ipad/iphone. > >So far the board is detected and clock are detected a long with the >clock version. I have been using the DGT low level driver and dgtnix >for working my way through this, I currently do not have a DGT eBoard >and still am looking for someone with a DGT eBoard and the DGT XL >clock to capture data. > >I would recommend http://sourceforge.net/projects/usbsnoop/ > >here is a simple guide > >http://www.jespersaur.com/drupal/book/export/html/21 > > >Anyways, I thought I was correctly sending data to set Mode 23, but >after I have been getting no where I went a wrote a quick simple app >the uses the windows driver to use all the API functions and output >data. >I then did a call to _DGTDLL_ClockMode which always returns 0, and >should return 23. > >Here is the data I am sending > > 0 1 2 3 4 5 6 7 8 9 >8D 00 0A 0A 0A 09 0A 1E 0A 00 // clock version >8D 00 0A 0A 10 01 20 00 23 00 // ready for display >8D 00 0A 0A 10 0A 20 00 17 00 // Mode 23 >8D 00 0A 0A 10 0A 0A 64 0A 00 // Mode 23 > >This is just going by what is in the low level driver. I am not really >sure when Mode 23 is set on a normal game. > >If anyone has any documentation on the board to PC protocol that would >be helpful also. > >------------------------------------------------------------------------ >------ >Benefiting from Server Virtualization: Beyond Initial Workload >Consolidation -- Increasing the use of server virtualization is a top >priority.Virtualization can reduce costs, simplify management, and >improve >application availability and disaster protection. Learn more about >boosting >the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev >_______________________________________________ >Dgtnix-devel mailing list >Dgt...@li... >https://lists.sourceforge.net/lists/listinfo/dgtnix-devel |
|
From: Random P. <net...@gm...> - 2011-04-14 11:16:34
|
Well, I would say I am missing when exactly Mode 23 is sent to the PC. Clock version info has a request, and I send the Mode 23 after I send the clock version. Here is some of the low level driver code I used it to check my Mode 23 to make sure it was being sent correctly. http://ideone.com/q1WF3 There are three ack Messages in DGT_BWTIME this is from the low level driver 0x81 // Ready for disps 0x88 // Start/Stop button pressed 0x8a // Clock Mode then there is the other one SETNRUN (Clock Mode = 23) where it sets the clockMode to 23 I am guess you send this BWTime when a DGT_CMD_CLOCK_SETNRUN is sent from the computer. On Thu, Apr 14, 2011 at 5:21 AM, Jan Krabbenbos <ja...@dg...> wrote: > Hi Random, > > All info on our board protocol is on our DGT website, see: > http://digitalgametechnology.com/site/index.php/Table/Developers/ and > http://digitalgametechnology.com/site/index.php/Developers/View-category.html > > Mode 23 is a mode on the clock to show all information that is sent by a program, e.g. a chess program, to the clock via the clock messages. The other 22 modes are game clock settings (see the manual of the DGT XL) and can only be read out from the board. > > What other information are you missing? > > The board driver not returning 23 might be a bug in the driver, I should check that. > > With kind regards, > Met vriendelijke groet, > > Jan Krabbenbos > Software Development > > > Phone: +31(0) 53-4305195 > Fax: +31(0)53-4329365 > http://www.dgtprojects.com > > visit address: Hengelosestraat 66, 7514 AJ Enscheded, The Netherlands > mail address: PO Box 1295, 7500 BG Enschede, The Netherlands > > > > >>-----Original Message----- >>From: Random Persons [mailto:net...@gm...] >>Sent: donderdag 14 april 2011 12:13 >>To: dgt...@li... >>Subject: [Dgtnix-devel] Sim Info >> >>I started a new post, due to to message being over 40k and no one >>could read the topic in the archive. >> >>A status update, I am currently writing some software that simulates >>the DGT eBoard to help me write drivers for an ipad/iphone. >> >>So far the board is detected and clock are detected a long with the >>clock version. I have been using the DGT low level driver and dgtnix >>for working my way through this, I currently do not have a DGT eBoard >>and still am looking for someone with a DGT eBoard and the DGT XL >>clock to capture data. >> >>I would recommend http://sourceforge.net/projects/usbsnoop/ >> >>here is a simple guide >> >>http://www.jespersaur.com/drupal/book/export/html/21 >> >> >>Anyways, I thought I was correctly sending data to set Mode 23, but >>after I have been getting no where I went a wrote a quick simple app >>the uses the windows driver to use all the API functions and output >>data. >>I then did a call to _DGTDLL_ClockMode which always returns 0, and >>should return 23. >> >>Here is the data I am sending >> >> 0 1 2 3 4 5 6 7 8 9 >>8D 00 0A 0A 0A 09 0A 1E 0A 00 // clock version >>8D 00 0A 0A 10 01 20 00 23 00 // ready for display >>8D 00 0A 0A 10 0A 20 00 17 00 // Mode 23 >>8D 00 0A 0A 10 0A 0A 64 0A 00 // Mode 23 >> >>This is just going by what is in the low level driver. I am not really >>sure when Mode 23 is set on a normal game. >> >>If anyone has any documentation on the board to PC protocol that would >>be helpful also. >> >>------------------------------------------------------------------------ >>------ >>Benefiting from Server Virtualization: Beyond Initial Workload >>Consolidation -- Increasing the use of server virtualization is a top >>priority.Virtualization can reduce costs, simplify management, and >>improve >>application availability and disaster protection. Learn more about >>boosting >>the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev >>_______________________________________________ >>Dgtnix-devel mailing list >>Dgt...@li... >>https://lists.sourceforge.net/lists/listinfo/dgtnix-devel > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Dgtnix-devel mailing list > Dgt...@li... > https://lists.sourceforge.net/lists/listinfo/dgtnix-devel > |
|
From: Jan K. <ja...@dg...> - 2011-04-14 13:28:16
|
The mode 23 is sent from the clock to the computer (via the board) at the moment it is set by a person selecting this mode on the clock. This also goes for the start/stop button. The SETNRUN command is given by the computer to the clock (via the board) to set a time on the clock and to tell the clock which side should run. This only works on the clock in mode 23. If you want to show a message on the clock DGT_CMD_CLOCK_MESSAGE command (as described in the low level driver) must be used to display and a DGT_CMD_END_CLOCK_MESSAGE to return back to the time display. This results in the ready for disps acknowledgement, if I'm correct. To my knowledge the board does not store the clock acknowledgments, the driver has to do this. With kind regards, Met vriendelijke groet, Jan Krabbenbos Software Development Phone: +31(0) 53-4305195 Fax: +31(0)53-4329365 http://www.dgtprojects.com visit address: Hengelosestraat 66, 7514 AJ Enscheded, The Netherlands mail address: PO Box 1295, 7500 BG Enschede, The Netherlands >-----Original Message----- >From: Random Persons [mailto:net...@gm...] >Sent: donderdag 14 april 2011 13:16 >To: Main discussion place for dgtnix relative topics >Subject: Re: [Dgtnix-devel] Sim Info > >Well, I would say I am missing when exactly Mode 23 is sent to the PC. >Clock version info has a request, and I send the Mode 23 after I send >the clock version. > >Here is some of the low level driver code I used it to check my Mode >23 to make sure it was being sent correctly. > >http://ideone.com/q1WF3 > >There are three ack Messages in DGT_BWTIME this is from the low level >driver >0x81 // Ready for disps >0x88 // Start/Stop button pressed >0x8a // Clock Mode > >then there is the other one >SETNRUN (Clock Mode = 23) where it sets the clockMode to 23 I am guess >you send this BWTime when a DGT_CMD_CLOCK_SETNRUN is sent from the >computer. > > > |
|
From: Random P. <net...@gm...> - 2011-04-14 16:00:07
|
Oh Okay, I was thinking there might be an order it had to go in maybe the clock sent other packets first before Mode 23. I loaded up ollydbg and IDA and was able to find the functions in DGTEBDLL.dll that BWTIME:Decode, the low level driver protocol seems to bit a bit different. I was able to get the driver to say it was in Mode 23 when calling _DGTDLL_ClockMode, yet still no messages from Arena about blacks movements being sent to the clock. On Thu, Apr 14, 2011 at 8:27 AM, Jan Krabbenbos <ja...@dg...> wrote: > The mode 23 is sent from the clock to the computer (via the board) at the moment it is set by a person selecting this mode on the clock. This also goes for the start/stop button. > > The SETNRUN command is given by the computer to the clock (via the board) to set a time on the clock and to tell the clock which side should run. This only works on the clock in mode 23. > > If you want to show a message on the clock DGT_CMD_CLOCK_MESSAGE command (as described in the low level driver) must be used to display and a DGT_CMD_END_CLOCK_MESSAGE to return back to the time display. This results in the ready for disps acknowledgement, if I'm correct. > > To my knowledge the board does not store the clock acknowledgments, the driver has to do this. > > With kind regards, > Met vriendelijke groet, > > Jan Krabbenbos > Software Development > > Phone: +31(0) 53-4305195 > Fax: +31(0)53-4329365 > http://www.dgtprojects.com > > visit address: Hengelosestraat 66, 7514 AJ Enscheded, The Netherlands > mail address: PO Box 1295, 7500 BG Enschede, The Netherlands > > >>-----Original Message----- >>From: Random Persons [mailto:net...@gm...] >>Sent: donderdag 14 april 2011 13:16 >>To: Main discussion place for dgtnix relative topics >>Subject: Re: [Dgtnix-devel] Sim Info >> >>Well, I would say I am missing when exactly Mode 23 is sent to the PC. >>Clock version info has a request, and I send the Mode 23 after I send >>the clock version. >> >>Here is some of the low level driver code I used it to check my Mode >>23 to make sure it was being sent correctly. >> >>http://ideone.com/q1WF3 >> >>There are three ack Messages in DGT_BWTIME this is from the low level >>driver >>0x81 // Ready for disps >>0x88 // Start/Stop button pressed >>0x8a // Clock Mode >> >>then there is the other one >>SETNRUN (Clock Mode = 23) where it sets the clockMode to 23 I am guess >>you send this BWTime when a DGT_CMD_CLOCK_SETNRUN is sent from the >>computer. >> >> >> > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Dgtnix-devel mailing list > Dgt...@li... > https://lists.sourceforge.net/lists/listinfo/dgtnix-devel > |
Thanks for helping keep SourceForge clean.
X