___ ( _`\ | (_) ) | _ <' | (_) ) (____/'
### ## ## ##### ## ## ## ## ######
#### ## ##### ## ## #####
## ## ##### ## ## ## ## ## ## #####
### ## ## ## ## ## ####
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: Rather an example of how NOT to do it. We received a home-assembled ECU with a BT-serial (not RS232 but logiclevel serial "fbus") module inside ECU: an unsupported setup (connected wrong so it did not work and prevented VT communications; Disconnecting BT-RS232 => VT communication started to work immediately). * Bluetooth inside a metal case will not work. (see "Faraday cage") * First serial port: when VT is connected PC TX => ECU RX cannot be driven by the BT module, so BT module must be disconnected (this happens when DSUB9 connector is disconnected) ** but the module was connected inside the case to the ISP header, preventing the ST232 chip to drive main processor RX properly. ---- See BroadcastDatastreamAim for '''AIM only (not triggerframe)''', this way ECU => BT module one-way communication should work. '''Second RS232 is preferred''' * It can also '''Possible Solutions:''' * Should we '''provide a BT-RS232 module''' so that it can transmit from outside the metal case ? * or... Should we '''connect 2nd serial TX => BT Module''' (inside the ECU) for AIM comm ? ** might work with ECU endplate removed Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.