arnosub Posted January 24 Report Share Posted January 24 On 1/20/2024 at 10:35 AM, arnosub said: Hi, I would like to retrieve the state of my outputs from my razor pdm on realdash. I configured this: For the moment, I am looking at the status of my HC0 output but I cannot get the information 0,1,2 or 3 on my dash. Normally, this should be byte 1 of frame 1 through research, if this can help someone one day to find the status of the 4 High Current + 8 ADIO of a PDM on realdash, here is what I did successfully on my dash, I visualize the Active and Fault state of each PDM output or input. I used this can stream because the ecu receives these 2 parameters. Then this is transmitted to my dash, attached xml. Quote Link to comment Share on other sites More sharing options...
Laminar Posted January 25 Report Share Posted January 25 On 1/19/2024 at 5:28 PM, fantapants said: i had chosen this one for the hardwire connection over the wireless, assuming it might be more robust and or stable ? if life is gonna be easier with the wireless version ill give that a dig. i think im having troubles getting the ecu side settings to work. apologies for not being very bright with this stuff, can is entirely new to me and i don't learn new things too well lol. Scroll up a bit to my post in this thread about getting comms from a G4X to a MeatPi WiCAN-USB to an Android tablet working: The WiCAN-USB is capable of wifi, bluetooth, or USB comms so you can stay hardwired if you want. Make sure you have the G4X set up to broadcast like I did in my post. Make sure the USB-DUAL CAN baud rate jumper is set to match your G4X configured CAN baud rate. If that doesn't work, maybe swap out the USB-DUAL CAN for the WiCAN-USB, as that's been proven to work. Diplou 1 Quote Link to comment Share on other sites More sharing options...
Jens_l Posted February 18 Report Share Posted February 18 Is there any official link layouts for realdash? Quote Link to comment Share on other sites More sharing options...
Rozsko Posted February 18 Report Share Posted February 18 2 hours ago, Jens_l said: Is there any official link layouts for realdash? I am not aware of any. On the other hand you can find official Link logos and color codes and their usage terms on the website. Quote Link to comment Share on other sites More sharing options...
jdniss Posted April 19 Report Share Posted April 19 Hi @Adamw, Does the 'Onscreen button press' G4+ example from the original post still function the same way in the G4X / G5 firmware? IE: On 6/25/2018 at 6:49 PM, Adamw said: This config also includes an example of how to send an onscreen button press to the ECU I'm having trouble keeping a CAN DI activated after an onscreen key press in the G5 firmware - the CAN state reverts to "Fault" after 2 seconds. I had a look at the help file and noticed the CAN Latching comment - I've tried both Active and Inactive latched states - but any and all configuration still exhibits the same behavior: The CAN DI triggers into an Active after CAN keypress, activates the output, then after 2 seconds reverts to Fault and terminates the output. G5 The same CAN / Virtual AUX config worked under the G4+ before I ported it over, the only differences being the Engine Fan outputs - as the G5 options now binds an output directly to a Virtual AUX rather than a GP Output G4+ Thanks Quote Link to comment Share on other sites More sharing options...
Mot Posted April 20 Report Share Posted April 20 On 8/21/2021 at 12:39 AM, Adamw said: With CAN you can customise what channels you want, you can send data both ways so onscreen buttons can control ecu functions, and you can still tune with the dash connected. Does that mean I can connect a Windows tablet with USB and another device via CAN simultaneously. For example to have monitoring/logging/tuning via USB and at the same time use another device via CAN (Real Dash to send button commands to the ECU)? Quote Link to comment Share on other sites More sharing options...
Adamw Posted April 21 Author Report Share Posted April 21 14 hours ago, Mot said: Does that man I can connect a Windows tablet with USB and another device via CAN simultaneously. Yes. Quote Link to comment Share on other sites More sharing options...
Mot Posted April 21 Report Share Posted April 21 18 hours ago, Mot said: Does that mean I can connect a Windows tablet with USB and another device via CAN simultaneously. For example to have monitoring/logging/tuning via USB and at the same time use another device via CAN (Real Dash to send button commands to the ECU)? 4 hours ago, Adamw said: Yes. How would you realize this while using a GTTLink (NGTT+) and trying to get the CAN information wirelessly (wifi would be preferred) to the Realdash device (tablet/mobile phone). For example when using the MeatPi CAN adapter, that connects to the car via OBD, I would have to purchase a CANPCB (SKU 101-0022) cable from Link and would then have to wire that to the MeatPi? Or do I have that wrong somehow? If so, are there any adapters out there for this kind of application or do I have to pull the MeatPi apart/make my own plug? Another problem I can see with my specific application is the firmware of the ECU because it's a G4+ Plugin which is relatively old and for example doesn't support CAN keypads as far as I remember from reading the forum. Would be pretty annoying to buy/set up all that to then find out my ECU is too old. Firmware I'm running at the moment is 5.5.3.2802 which would need updating to 5.6.8.3671 which seems to be the latest for the G4+ plugins. Any pointers on what to look out for when doing the update? Sorry, lots of questions in this one Diplou 1 Quote Link to comment Share on other sites More sharing options...
Laminar Posted April 22 Report Share Posted April 22 I don't know why MeatPi chose to be so confusing with their product listing, but what they call "WiCAN" is actually two separate products, the WiCAN-OBD and the WiCAN-USB. The WiCAN-USB lets you wire directly into your CANbus, no pulling anything apart. If you scroll up a few posts I linked to where I have everything configured and working. jdniss 1 Quote Link to comment Share on other sites More sharing options...
jdniss Posted April 23 Report Share Posted April 23 On 4/22/2024 at 1:49 AM, Mot said: How would you realize this while using a GTTLink (NGTT+) to the Realdash device wirelessly to the (tablet/mobile phone) For example when using the MeatPi CAN adapter, that connects to the car via OBD An R34 GTT likely doesn't have ODB / ODBII at all - probably a Nissan "Consult" port that utilizes Nissan's own diagnostic protocol. The Consult data would only be available using the factory ECU, or an extension of that - a Nistune for example. To use a GTTLink and RealDash, you'd need a MeatPi WiCAN-USB, that would need to be wired into one of the Link GTT CAN ports - then connect from the the smart phone/tablet (running RealDash) via WiFi to the MeatPi. You could use a CANPCB (SKU 101-0022), but you'd be chopping off the Deutsch connector end, to screw the wires into the MeatPi. 13 hours ago, Laminar said: I don't know why MeatPi chose to be so confusing with their product listing, but what they call "WiCAN" is actually two separate products, the WiCAN-OBD and the WiCAN-USB. The WiCAN-USB lets you wire directly into your CANbus, no pulling anything apart. If you scroll up a few posts I linked to where I have everything configured and working. The developer has finally added RealDash USB Protocol connection information to the GitHub readme now, along with more clarity around connection methods, after one of the members asked for further clarification on the Discord Server. Diplou 1 Quote Link to comment Share on other sites More sharing options...
Adamw Posted April 23 Author Report Share Posted April 23 On 4/19/2024 at 7:11 PM, jdniss said: I'm having trouble keeping a CAN DI activated after an onscreen key press in the G5 firmware - the CAN state reverts to "Fault" after 2 seconds. I had a look at the help file and noticed the CAN Latching comment - I've tried both Active and Inactive latched states - but any and all configuration still exhibits the same behavior: The CAN DI triggers into an Active after CAN keypress, activates the output, then after 2 seconds reverts to Fault and terminates the output. This means the ecu hasnt received a CAN message with the DI status for more than 2 seconds. This is a safety feature so if for example a wire gets broken your CAN-controlled cruise control wont get "stuck on". Default realdash behaviour is it only sends a CAN message when a state changes (ie the button is pressed). The "write interval" option is meant to force realdash to send the message at least once every interval regardless of a state change. So it sounds like your .XML is either missing the write interval attribute or has a formatting issue with it, or there is a bug preventing that from working. You could possibly use the CAN monitor in realdash to see if that message is being transmitted regularly. I assume it shows transmitted messages. Quote Link to comment Share on other sites More sharing options...
Mot Posted April 23 Report Share Posted April 23 @Laminar & @jdniss Thanks for clarification on the MeatPI products. Leaves only the firmware concerns with my GTTLink (NGTT+), which @Adamw can may be comment on? Quote Link to comment Share on other sites More sharing options...
jdniss Posted April 25 Report Share Posted April 25 On 4/23/2024 at 10:07 PM, Adamw said: Default realdash behaviour is it only sends a CAN message when a state changes (ie the button is pressed). The "write interval" option is meant to force realdash to send the message at least once every interval regardless of a state change. So it sounds like your .XML is either missing the write interval attribute or has a formatting issue with it, or there is a bug preventing that from working. Hey @Adamw, Thanks for the info, I worked the issue out - while the 'WriteInterval' was previously included at 1000(ms), this is seemingly too high to prevent the 'Fault' state under G4X / G5: On 4/19/2024 at 5:11 PM, jdniss said: Someone on the Realdash forum suggested lowering this to 100ms, along with the RealDash developer recommending to set the "bit" unit type in the XML as well. The following configuration for RealDash CAN based onscreen "Value On/Off" 'action' button presses, works under G4X / G5 firmware: Thanks Quote Link to comment Share on other sites More sharing options...
Flex Posted June 13 Report Share Posted June 13 Sorry if this has been asked before but I'm looking to wire the can sniffer into the expansion loom on my G4X (Supra link). Any idea which wires I need to wire it up? Quote Link to comment Share on other sites More sharing options...
Juz Posted August 15 Report Share Posted August 15 I have a G4X (WRXLink7-9) and have installed an Eonon UA12S android heatunit which amongst it's connectivity has 2x cables labelled Rx and Tx. I can't find much about what this is precisely but presume Receiving data and Transmitting data, and the Youtube review of the headunit which lead to me buying it implied these were for connecting to the vehicle's steering wheel controls and air con etc. My G4X has the 1st CAN channel in use for the AEM Wideband so I've added a 2nd CAN cable with CAN high, low and ground wires. I presume I'll need to purchase a Seeed Analyser and go via the headunit's USB, however before I do this I wanted to check whether there's an even simpler way using the Rx and Tx cables? Thanks Quote Link to comment Share on other sites More sharing options...
jdniss Posted August 18 Report Share Posted August 18 On 8/15/2024 at 9:02 PM, Juz said: I have a G4X (WRXLink7-9) and have installed an Eonon UA12S android heatunit which amongst it's connectivity has 2x cables labelled Rx and Tx. The only other reference to "RX" and "TX" in the Eonon manual is on the 'D' plug for pins: "CAN Box Tx" and "CAN Box Rx" - though there is no other mention of the pins functionality anywhere in the manual, or on the website.. Whether its referring to a CAN Hi/Lo function, or the naming is just misleading? On 8/15/2024 at 9:02 PM, Juz said: My G4X has the 1st CAN channel in use for the AEM Wideband so I've added a 2nd CAN cable with CAN high, low and ground wires. I presume I'll need to purchase a Seeed Analyser and go via the headunit's USB, however before I do this I wanted to check whether there's an even simpler way using the Rx and Tx cables? Thanks The AEM X Series gauge communicates over CAN at 500kbit/s - both the 'SeeedStudio USB to CAN Analyzer' and something like a MeatPi WiCAN-USB can be reconfigured to receive CAN data at 500kbit/s too - so you could splice either into the existing CAN1 AEM wiring. A MeatPi WiCAN-USB also supports USB, Bluetooth and WiFi connections - so assuming a USB based connection from the 'SeedStudio CAN Analyzer' to the Eonon headunit doesn't work - you could fallback to either Bluetooth or WiFi if you grabbed the WiCAN-USB instead. Quote Link to comment Share on other sites More sharing options...
Juz Posted August 30 Report Share Posted August 30 Thanks for your advice. I too couldn't find any more details about what the CAN inputs on the headunit do, so I figured it was easier to follow the well-trodden path and go with a CAN-USB device. I bought the Seeed Analyser but cannot get it to work. Initially with neither the Android headunit or a PC, but after performing a reset procedure on it I can now get it to send and receive a single frame in the windows software (before resetting it would only send but not receive). I followed the video guide shared earlier in this thread regarding the setup of the ECUs CAN Module in PCLink G5. I have RealDash set to the correct baud but it simply says Not Connected when I view the CAN monitor in RealDash. At this stage I think I may just have to buy the MeatPi WiCAN USB as well now, as I suspect this may be a compatibility issue between the Seeed Analyser and my headunit. Unless you have any other suggestions to try? Quote Link to comment Share on other sites More sharing options...
jdniss Posted August 31 Report Share Posted August 31 Did you do any baud rate configuration on the SeeedStudio Adapter at all @Juz? For memory its default CAN baudrate config ships at 2Mbps out of the box, I had to reconfigure mine with the SeeedStudio Windows application so that I could splice it into the same CAN Port as the AEM UEGO X-Series at 500Kbps. Quote Link to comment Share on other sites More sharing options...
Juz Posted September 1 Report Share Posted September 1 Yes I tried different COM port baudrates on the SeedStudio adapter and RealDash. I'm beginning to wonder whether I might have a faulty adapter as it frequently gets "stuck", and ceases responding to Windows USBCAN 8.00 for a silent & loopback test frame, or fails to save a change of COM port baud rate, and I have to reset it to get it back. On the Link G4X I have 2 CAN buses and had set both baud rates to 500kbps. I have only the AEM Wideband on CAN 1 and the SeeedStudio adapter on CAN 2. I have also tried changing the CAN 2 baud rate to other values with no luck. Quote Link to comment Share on other sites More sharing options...
Adamw Posted September 1 Author Report Share Posted September 1 It should be relatively simple to set up with no configuration of the USB adapter outside of realdash needed at all. I would default the USB adapter by powering up with the default pads shorted. Then power cycle and follow the attached video. Realdash CAN connection.mp4 Quote Link to comment Share on other sites More sharing options...
Juz Posted September 11 Report Share Posted September 11 Definitely have a dud Seeed CAN USB adapter. I bought a MeatPi WiCAN USB instead and it's working great over wifi, links into RealDash and could instantly see data on the CAN monitor, which I was never able to get from the Seeed analyser. Still need to play around with the XML to get the data to display correctly in the dash (using the sample XML file from this thread gives me water temp, revs, gear, AFR, battery volts - but no vehicle speed or boost values coming through), I haven't been able to get it to work over BLE or USB yet but it's a step in the right direction. Quote Link to comment Share on other sites More sharing options...
jdniss Posted September 13 Report Share Posted September 13 On 9/11/2024 at 6:28 PM, Juz said: I haven't been able to get it to work over BLE or USB yet but it's a step in the right direction. @Laminar has some BLE settings on Page 16 - about halfway down The USB settings on MeatPi's GitHub page should work - they did for me: On 9/11/2024 at 6:28 PM, Juz said: Still need to play around with the XML to get the data to display correctly in the dash (using the sample XML file from this thread gives me water temp, revs, gear, AFR, battery volts - but no vehicle speed or boost values coming through) You may need to build a custom CAN Stream to send any additional data through to RealDash - for memory the example is based on something like the "Generic User Stream" that was limited to 30 parameters as it wasn't compounded. I added a rough example of a compound CAN Stream on Page 15 - however it was for a G4+ and would need a couple of tweaks to suit a G4X - but it might be enough to get you started. Happy to attach my current G4X compound CAN Stream and matching RealDash XML, if you want it. Quote Link to comment Share on other sites More sharing options...
kasipong Posted September 20 Report Share Posted September 20 Can use HC05 Bluetooth connect to tablet and use TTL connect to Link Atom? Quote Link to comment Share on other sites More sharing options...
Adamw Posted September 20 Author Report Share Posted September 20 In thoery the serial stream via bluetooth will work, but I would strongly suggest you avoid that option and use one of the realdash recommended CAN devices instead. Several downsides to the HC05: Configuration has to be done by sending with AT commands with a terminal application. Many of the low-cost HC05 are pirated clones and have frustratingly bad code and documentation. You will find they often dont respond as expected to the documented commands, or randomly reset to default etc. Similar to above, the pirated ones often have very flakey reliability of connection, they disconnect often and wont reconnect until rebooted etc. Serial is slower than the CAN option, it is a fixed data set with a limited number of channels. It is missing some common channels such as Lambda. The serial stream is only one way communication, you cant send button presses from the dash to the ecu for example. You will get little help from users here if you have problems as none of us use it so there is little community experience to offer insight. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.