Jump to content

redmist

Members
  • Content Count

    57
  • Joined

  • Last visited

  • Days Won

    1

redmist last won the day on June 9 2019

redmist had the most liked content!

About redmist

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I dropped the Nano and went ESP32 wrover. On board can so only required an external transceiver. Picks up almost all frames. At least it's more consistent than the Nano and more than enough for a good refresh rate on the dash. Because of the "pause" between data sends the ESP will always pick up the first frames, which means the RPM is always refreshed quickly. It's dropping the occasional frame mid to late in the dataset, again not enough to bother a dash refresh. I tried lowering the transmit rate, but all that does is increase the "pause" between "burst" sends. As such it still drops
  2. I'd also like to move away from the Generic Dash to something more customized around my needs. Although I've "fudged" the generic dash such that I can display my gearbox temp, unfortunately the AIM Evo 4 that I'm currently using in the offroad race car requires that protocol. The rally car runs a G4 Storm, which by default does't appear to have a Generic Dash 2 LLC (although I'm sure I could create one). I am however having an issue with either the arduino libraries or the MCP2515 controller. Specifically it's dropping large amounts of frames from the buffer and given a small delay in the p
  3. I've currently got all 6 seven segments and the 8x8 Matrix to work with Link "generic dash" can bus output. There is some work to do with my neopixel library conflicting another of my libraries, and a weird issue with my can bus adapter only picking up frame 0 or 1 when you start to introduce a delay (like writing to the 7 Segs). However given a correction of my frame issue I'm not seeing any problems with refresh from the Nano. Weird thing is the Nano will do several hundred main loops prior to picking yet another frame 0 from the buffer. Although there is a deep imprint of my keyboard in
  4. Thought the Teensy still required a can bus transceiver? If I could attach the teensy straight to my canbus then it would save me a tonne of grief!!! I've a friend that's had issues with Nextion and refresh rates, switched to a cell phone. Seems all the integrated intelligence screens struggle.
  5. Nice job David! Thank you for the pointers to Pauls well presented site. Thankyou Paul for spending the time and effort to detail such. I gather the reason people have migrated from the arduino mega/nano to the teensy (or other platform) is because it's just too slow? I suspect by the time I generate interrupts from the flappy paddles and insert new frames on the canbus I'll simply ask too much from this stupidly cheap device. My dash is currently being benched (chose a mass of 7 segments as they are bright in sunlight for the open race car), have it testing libraries and some basi
  6. So David, do tell? Spill the code! After using a Raspberry pi and a small radio modem to transmit Link CAN Bus data over a serial link I've now started playing with an arduino to simply pull data off the bus and display it on a set of 4 x 7 Segments, an 8x8 matrix (gear display) and neopixel leds (RPM Limits). My coding is Uuuuuugly... but it works... mostly.
  7. G4 Storm, old case, updated for CAN. Generic Dash stream at 20Hz. Only CAN sniffer I have is the PiCAN 2 shield on my Pi 3. Three, frame 14 (0d) interspersed through my log... I've used both C and Python libraries. Given it's a correctly formatted CAN message I doubt it's generated by by PiCAN2 board. I guess I could drop the entire frame given it contains nothing? (don't want to send rubbish over radio). candump.txt
  8. Through my own stupidity, (and lack of 16 fingers) I used the wrong trigger to complete a stream of Link CAN (Generic Dash) data for my radio telemetry program. On triggering a completed set using the last frame as "d" (14), from the correct Link CANID I got an intermittent completion of the link data set (and sent via radio). On further investigation I've noted that it's only sending frame 14 once randomly every 5-10 or so seconds. This frame does not appear on the Generic Dash CAN Data Format. The 7 remaining words (including the 6 that are relevant) are all "00"'s Wondered if it
  9. Cheers Adam, thanks for that. I suspect my USB serial adapter might not be doing RS232 but TTL. That and the fact that Putty is playing games with me.
  10. Have attempted to use the RS232 port with the Link configured to 12hz continuous. There isn't a squeek out of the port until such point in time as I kick up PCLink.
  11. I've an older G4 Storm that I'm benching for radio telemetry. It's simply a trial to enable both my G4+ Xtreme's to transmit radio telemetry, GPS data and alerts to a base. I've got the radio bridge working well, bridging between two USB devices (GPS and radio), and my program logs, truncates and transfers NMEA data to my second device without issue. However on switching to the Storm I've noted that the Continuous modes (12/25 hz, and CRC) don't appear to be continuous. As in without any input from PCLink the USB serial port is silent. I could emulate the PCLink "tuning" call, howev
  12. What turbo are you using and are you still using the stock LIM? Cheers, Currently running a crate core FD engine in an offroad race car.
  13. How sensitive is this "clever digital knock detection device" to noise? Specifically all the knock sensors I've run in the past have been fooled by the noise of shattering rock against the bash plates underneath the engine.
×
×
  • Create New...