Jump to content

tineira

Members
  • Posts

    26
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

tineira's Achievements

  1. Yes, it is the same and only log with this issue, it happens every time, days apart from each attempt.
  2. When I try to download a particular log file (only happens with that log) there is a division by zero error. is there anything you want to be able to debug this? I don't care too much about that log, but it might help to find and correct a bug. thanks,
  3. Shit! Thanks, I missed the "STD Bosch NTC" and thought that 0280130017 was the standard one. The strange thing is that then the 0 261 230 340 sensor should use the "STD Bosch NTC" and not the "Bosch NTC 0 261 230 340" calibration?
  4. Hi, First of all, all of the datasheets I found online for this sensor have the same calibration as what is implemented in Link software, but I think that maybe that info is incorrect or I could have a fake sensor. I bought the sensor from a reputable source I think. Ok, from my testing the correct Calibration for this sensor is the standard bosch calibration (0 280 130 017). With the engine off for a few hours and also checking the thermostat housing with a thermocouple, if I choose the "0 261 230 340" calibration the reading is off by 10°c compared with the thermocouple and the IAT: If I select the "0 280 130 017" calibration, all readings are the same: Also checking the ECT while cruising on the highway, the temperature drops until the thermostat opening temperature and matches with the "0 280 130 017" calibration. An at last, at 90°C (measured with the thermocuple on the thermostat housing) the calibration matches the "0 280 130 017" calibration. Does anyone use this sensor that could help me corroborate this?
  5. I tried that, the only thing that is bugging me is that on the X parameter, the min value and max value are integers, so the scale can not be adjusted too much. I could multiply lat/long by 100 or something like that, but are like unnecessary steps.
  6. I know this is a long shot but I'm sending GPS data from CAN and using Math channels to calculate Lat and Long with 7 digit precision, and altitude data. It would be great to be able to choose this parameters as Latitude and Longitude on the GPS Plot as I think that they are using the default fields by default. Better yet, would be to be able to store this math channels on the Latitude and Longitude parameters.
  7. Thanks for your reply and explanation.
  8. Feature request: be able to save files on a human readable format. I always try to track my changes on Git or other source control software. It would be nice to be able to track changes on configuration / tune , but as the .pclx is a binary file it does not makes sense to track changes that way. If you could choose to save/load files as .pclx or a text based version, it would make tracking / reverting changes much simpler.
  9. Is there any difference between the "Shield / Gnd" and "Gnd Out" pins? Can I use both for grounding sensors and grounding shields? Thanks
  10. Thanks, having the polling ratio for these values should be helpful. The same info for log marker would be great.
  11. How long should the Fault Code Clear Switch be active for it to clear the check engine light? I have tried up to 500 ms and it does not always work, but it would be nice to have a definitive answer on this. I'm using a CAN DI as the input.
  12. hey @k fuku I managed to pass data splitting the signed 32 bit value. The problem is if the value is negative, strange things might happen. so I ended up sending the absolute value of the latitude and longitude and splitting each value in three parts a 15 bit number, a 16 bit number and the missing bit I use to send a DI for negative values. Then I created a math channel that reconstructs the value. I'm sending the can messages from an arduino, so this is how I build the message.
  13. Hi, As a fun project I'm trying to use an Arduino Giga with a touch screen as a dash, additional sensor input and a Keypad. I already can read then CAN messages from the ECU to display, also I can send analog and digital sensor information back to the ECU. My idea is to use this device also as a CAN Keypad, I could use the digital inputs as on off switches, but was wondering what is the difference between this and what a Keypad could do? Is there any documentation on the CAN structure used by keypads? maybe I could emulate an existing one. Thanks,
×
×
  • Create New...