There is a message for the headlight status (0x625 on the can bus) Not quite the same but usable. The light sensor may also be in that message.Am hoping to find a message on the canbus indicating the condition of the cars light sensor so I can dim the display whenever the LEAFs built-in instrumentation is dimmed. Worse case, I can add a cadmium sulphide cell to one of the spare analog inputs,
No, it's just odd shaped due to the shape of the enclosure: I will make them all shorter. I think I will also hollow the feet out down to the optimal distance for each corner so it will sit flat as it arrives, but you can cut off the hollow, thin-walled, section to set the right height for each. They will all have to be different lengths for it to sit with all four feet on the dash. I added rubber feet to the corner of rev1, and when I push three feet flat on the dash, the fourth is ~3/16 above - the surface back there has twist in addition to the curvature.garygid wrote:Are you missing a "leg" on the left side of the front surface
of your rendering of your v2 enclosure?
Thanks - I'll check it out. Headlight status should work but I'll see if there are other options. One of the displays I added was one that just displays which canbus messages changed so you can easily see cause and effect for the various sensors.turbo2ltr wrote:There is a message for the headlight status (0x625 on the can bus) Not quite the same but usable. The light sensor may also be in that message.Am hoping to find a message on the canbus indicating the condition of the cars light sensor so I can dim the display whenever the LEAFs built-in instrumentation is dimmed. Worse case, I can add a cadmium sulphide cell to one of the spare analog inputs,
I debated that.. Aesthetically, I like sharp clean lines. Maybe I soften it a bit but with a smaller radiusgarygid wrote:commects:
1. wall between the displays, you might want to round the sharp edge.
A little, but easier then accessing the programming port on the gid-o-meter. I will probably leave the programming USB cable plugged in to the mbed when actively debugging/programming. There is room there but I agree may be tough if you have thick fingers.garygid wrote: 2. access to the mini/micro USB connection on the Mbed board for
re-programming or logging to the PC - seems difficult.
Yes, I like having the logger USB connection in the back and the cabled USB port is bulky (at least mine is). The only place I could fit the cabled connector was on the right side wall and then it interferes with the programming USB connection. I could have rotated the mbed orientation and cut a hole for programming on the left side leaving the space on the right for a cabled USB datalogger port, but once I realized I could swing the bottom of the PCB out to make the PCB mount work I decided to go that route (didn't want a hole left over once I was done programming). Even pulled forward, there is still more clearance on the bottom than on the top. I am working on a 3d mechanical model of the board and the LCDs to ensure there are no collisions. You may be right that I will have to adjust to ensure the LCDs or center wall don't block the programming port. It's is tight in there.garygid wrote: 3. it appears that the only reason to have the circuit board forward so far is
to keep most of technology USB connector inside.
garygid wrote: 4. more coming