How I enabled/coded a factory alarm on my R1250GS

i have the alarm fitted - factory install - never use it. more hassle and no real deterrent. Spend the 50 euros/pounds/dollars on an additional lock for your mighty steed
 
I'm struggling to get E-sys to connect. Being an early 2017 R1200GS it has the OBD2 socket, which is just a CAN Bus link (just 5 pins populated). The ICOM Next connects fine using ISTA+, reads the bike status, perform diagnostics, etc. Using iTool Radar its showing the connection as IP address as 169.254.254.42. Wireshark network diagnostics shows all the comms between ISTA+ (using ports 6801, 6802, 50093, 50094, 54688,...) and the ICOM Next are fine, no errors. I start E-Sys (configured for motorcycle), connecting to target vehicle: K001* with ICOM/D-CAN set to`169.254.254.42:52140. I get nothing in response. Wireshark diagnostics displays the message to 169.254.254.42:52140 in red, indicating that the TCP message from E-sys was not acknowledged by ICOM. Also using "netstat -a" it registers the SYNC request 169.254.254.42:52140, but the port 52140 never achieves the states of "listening" or "established". This with my basic network understanding is that the ICOM Next has not opened the port to listen for connection requests. Any advice on how to get E-sys talking to an ICOM Next box gratefully accepted. :confused: Alternatively is there anyone with E-Sys configured that can do some flashing on a R1200GS to accept a TFT display? Beer tokens available for inconvenience.
 
Last edited:
Just wanted to post a thanks for the guide for this.
I had some experience coding from having a Mini, BMW etc. so this was a nice reminder of what's possible with coding.

I've just sorted the alarm on my 1250, the only niggle was the PSdZData I was using with e-sys was older than what's installed on the bike - so if you're having issues with the final coding to some modules an updated PSdZData should sort it out.
 
Could someone share the pdf file with me? I would really appreciate it.
 


Back
Top Bottom