+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: Solved ✔ NBT EVO HW4.1 on the bench (/showthread.php?tid=43512)
Pages:
1
2
NBT EVO HW4.1 on the bench - Coding34 - 10-12-2018
Hi,
I have a NBT EVO HW4.1 and i try to flash it on the bench.
For that i have made my own cables for the quadlock (including ETH_A with 1kOHM to 12v) and the OABR cable, and bought a USB to CAN.
When i send the wake-up message 0x12F 37 7C 8A DD D4 05 33 06 and/or 0x130 45 40 22 8F FE the unit wake-up. But i can ping it (169.254.199.99) for 40s only then the unit goes into sleep mode few seconds, then wake-up 40s, then sleep, and again and again. The screen (8.8" Touch screen) remains black and the fan does not start.
So it seems like there is a need for another message to maintain the unit awake.
Has anyone ever had this case and solved it?
Thank you.
RE: NBT EVO HW4.1 on the bench - Vias - 11-12-2018
For EVO use iDrive controller or send this ID 563 00 00 00 00 FF FF 00 63
Good luck!
RE: NBT EVO HW4.1 on the bench - Coding34 - 13-12-2018
I have made some tests and nothing change with the message ID 0x563.
The iDrive contoller is always connected, with or without, nothing change
At the end, i tested with random message and the result is always the same: wake-up 40s, then sleep, wake-up 40s, then sleep, and again and again
What's happen ?
RE: NBT EVO HW4.1 on the bench - FSCmap - 13-12-2018
maybe better get a cas + zgw or fem?
RE: NBT EVO HW4.1 on the bench - BugFix - 13-12-2018
just ZGW + 0x130 + 0x12F + 0x2F4 + 0x2F7 will be good for F series coded EVO
for G series a few to add
RE: NBT EVO HW4.1 on the bench - Vias - 13-12-2018
Well guys, I send only this two massage:
12F 37 7C 8A DD D4 05 33 06
563 00 00 00 00 FF FF 00 63
Only EVO+Laptop+Ethernet Cable+CanSender+Supply Power 12v and it work good for Flash, Code and play with it!
I don't use ID 130 and ID 267 or any other.
What is interval you use, more 100 ms? Are you have resistor 120 om in your CAN sender?
RE: NBT EVO HW4.1 on the bench - BugFix - 13-12-2018
NM2_BODY_CAN
1379 (563h) - NBTevo_Rueko [21] {aktiv bei: KL_30B}
Zykluszeit: ttyp = 640.0 ms (tmin = 608.0 ms, tmax = 672.0 ms)
Aktivbedingung = KL_30
Startbedingung = KL_30_ON; Stopbedingung = KL_30_OFF
RE: NBT EVO HW4.1 on the bench - BugFix - 14-12-2018
(13-12-2018, 22:07 PM)Vias Wrote: Well guys, I send only this two massage:
12F 37 7C 8A DD D4 05 33 06
563 00 00 00 00 FF FF 00 63
Only EVO+Laptop+Ethernet Cable+CanSender+Supply Power 12v and it work good for Flash, Code and play with it!
I don't use ID 130 and ID 267 or any other.
What is interval you use, more 100 ms? Are you have resistor 120 om in your CAN sender?
What you mean about 267 ?
ID267=OP_PENC_OPEL_FRONT (Bedienung Tastgeber Bedienelement Front), ZBE
267 - it is just buttons from i-drive controller
(10-12-2018, 10:38 AM)Coding34 Wrote: For that i have made my own cables for the quadlock (including ETH_A with 1kOHM to 12v) ,Haveto disconnect that fake
RE: NBT EVO HW4.1 on the bench - billyballs - 15-12-2018
BugFix where do you get the info from the CAN bus ?
I mean this:
(14-12-2018, 21:04 PM)BugFix Wrote: ID267=OP_PENC_OPEL_FRONT (Bedienung Tastgeber Bedienelement Front), ZBE
and this:
(13-12-2018, 22:31 PM)BugFix Wrote: NM2_BODY_CAN
1379 (563h) - NBTevo_Rueko [21] {aktiv bei: KL_30B}
Zykluszeit: ttyp = 640.0 ms (tmin = 608.0 ms, tmax = 672.0 ms)
Aktivbedingung = KL_30
Startbedingung = KL_30_ON; Stopbedingung = KL_30_OFF
RE: NBT EVO HW4.1 on the bench - BugFix - 15-12-2018
Google work fine for me