pgmfi.org

Hacking up Honda's ECU
It is currently Tue Sep 18, 2018 5:38 pm

All times are UTC - 5 hours [ DST ]





Post new topic Reply to topic  [ 13 posts ] 
Author Message
PostPosted: Sun May 02, 2010 11:28 am 
Offline

Joined: Sun Feb 21, 2010 10:47 am
Posts: 8
i have my serial communication setup only i tried to communicate with the burn1 for example to get the version but no response i want to know what are the commands to communicate? maybe some example code..


Top
 Profile  
Reply with quote  
PostPosted: Thu May 06, 2010 3:21 am 
Offline

Joined: Wed May 20, 2009 3:38 pm
Posts: 112
did u check the port setting in device manger and did u install the right diver


Top
 Profile  
Reply with quote  
PostPosted: Thu May 06, 2010 11:09 am 
Offline
PGMFI Elf

Joined: Tue Jul 27, 2004 2:17 am
Posts: 1413
Location: Phoenix, AZ
Right on the website...
http://www.moates.net/zips/firmware/pro ... %20v19.zip


Top
 Profile  
Reply with quote  
PostPosted: Thu May 06, 2010 6:26 pm 
Offline

Joined: Sun Feb 21, 2010 10:47 am
Posts: 8
i do have that file for protocols only i send data to the burn2 and i get back ????? not the version... on that file it says to send 'V'+'V' so i don't know if i literally send 'V'+'V' or what does it send or even how to send it....i haven't done serial communication before so don't know how the protocol works exactly...if someone can chime in with some example or even some code..would be great help


Top
 Profile  
Reply with quote  
PostPosted: Fri May 07, 2010 1:03 am 
Offline

Joined: Sun Feb 21, 2010 10:47 am
Posts: 8
i do have that file for protocols only i send data to the burn2 and i get back "?????" not the version... on that file it says to send 'V'+'V' so i don't know if i literally send 'V'+'V' or what do I send or even how to send it, i mean i send in a char array containing that "string" or what?....i haven't done serial communication before so don't know how the protocol works exactly...if someone can chime in with some example or even some code..would be great help


Top
 Profile  
Reply with quote  
PostPosted: Fri May 07, 2010 8:31 am 
Offline

Joined: Sat Apr 09, 2005 9:53 am
Posts: 625
just to make it extra confusing... :wink:

RTPComm.Output = Chr(CByte(HextoLong("56"))) & Chr(CByte(HextoLong("56")))

basically output the string "VV" and wait for a response...which should be a 3 byte array; 5, ?, B where ? is the firmware version.


Top
 Profile  
Reply with quote  
PostPosted: Fri May 07, 2010 11:51 am 
Offline
PGMFI Elf

Joined: Tue Jul 27, 2004 2:17 am
Posts: 1413
Location: Phoenix, AZ
The Protocol guide tells you exactly what to send and exactly what to expect back. Like stated, sending 'V'+'V' or 0x5656 retrieves the three byte version of the product.


Top
 Profile  
Reply with quote  
PostPosted: Sat May 08, 2010 9:55 am 
Offline

Joined: Sun Feb 21, 2010 10:47 am
Posts: 8
fastcrxsi90 wrote:
just to make it extra confusing... :wink:

RTPComm.Output = Chr(CByte(HextoLong("56"))) & Chr(CByte(HextoLong("56")))

basically output the string "VV" and wait for a response...which should be a 3 byte array; 5, ?, B where ? is the firmware version.


thanks guys i finally got it, im doing it on c#, fastcrxsi90's post actually helped me didn't confuse me at all lol


Top
 Profile  
Reply with quote  
PostPosted: Mon Sep 27, 2010 6:30 am 
Offline

Joined: Sun Sep 26, 2010 10:55 pm
Posts: 4
It is very good collection of c#, fastcrxsi90's post. I am doing two project in this topic and it is very useful for me. I can't thank you enough, it is very needed tutorial because of it I am very much appreciate to you.


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 04, 2011 5:25 pm 
Offline

Joined: Sat Jul 14, 2007 1:36 pm
Posts: 136
Location: Middlesbrough, UK
If you write a routine to send the command byte and the checksum, the checksum for V (char 0x56) is V (char 0x56).

Thats why it sends VV. Saves you writing a routine for writing commands with checksum and one without [+]


Top
 Profile  
Reply with quote  
PostPosted: Thu Jan 06, 2011 3:40 pm 
Offline

Joined: Sat Apr 09, 2005 9:53 am
Posts: 625
ximon wrote:
If you write a routine to send the command byte and the checksum, the checksum for V (char 0x56) is V (char 0x56).

Thats why it sends VV. Saves you writing a routine for writing commands with checksum and one without [+]


good point...V for version which yields V as the checksum.


Top
 Profile  
Reply with quote  
PostPosted: Thu Jan 06, 2011 7:53 pm 
Offline

Joined: Sat Jul 14, 2007 1:36 pm
Posts: 136
Location: Middlesbrough, UK
fastcrxsi90 wrote:
...V for version which yields V as the checksum.


Yup - it would probably have been clearer if i had mentioned V for version.


Top
 Profile  
Reply with quote  
PostPosted: Fri Jan 07, 2011 11:49 am 
Offline
PGMFI Elf

Joined: Tue Jul 27, 2004 2:17 am
Posts: 1413
Location: Phoenix, AZ
It's mentioned in the Moates Hardware Protocols document linked above.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 13 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  


Powered by phpBB® Forum Software © phpBB Group