Whatever!!!!!!!!! Gearhead-EFI Edition

[Six_Shooter]

LOL.

No, welding. Needed to pre-heat the intake.

I used an IR overhead shop heater last time, but when I plugged it in a couple weeks ago to finish welding this thing, magic smoke came out of the control box. So the owner and I had thought about buying a cheap oven to do the preheat and cool down, but it would have been bulky and heavy to move.

I was talking to a welder friend of mine who suggested a bar-b-que for the job. A Kijiji ad later I had this Bar-b-que to use.

It worked very well for the purpose.

[Six_Shooter]

Some more playing around:

Serial IR receiver to control my HTPC, eventually.





I know it works, I have tested it using WINLirc, as the main input program, but need to configure some stuff to work with the PC and XBMC.

Once I have everything configured and working, then I'll put this on a proper circuit board, and install it in the tower. I will make a second one as well for my GF's HTPC, once I build her one.

I'm also going to test to see if I can get it to work with a USB to serial converter I have, so I can use parts I already have in my possession. The HTPC in the picture has a serial port, though it's not on the back panel, like they used be, which in this case is a good thing, but I have MoBos that don't have native serial support, and would require an add-on card for serial!

[RobertISaar]

quote from VL400 on the delcohacking boards:

The 808 is a custom MCU and does not offer the same options. You have these choices with register 4004...
; SS0 SS1 BAUD RATE
; 1 1 256
; 0 1 1024
; 1 0 8192
; 0 0 32768
I have tried 32k baud (12P has selectable baud rate since v1.02) but its very unreliable - being a non-standard baud rate the divisors dont get close enough and you run errors.

wonder if he wasn't using a FT232 chip?

according to FTDI:

The FT232R supports all standard baud rates and non-standard baud rates from 183 Baud up to 3 Mbaud. Achievable non-standard baud rates are calculated as follows -
Baud Rate = 3000000 / (n + x)
where n can be any integer between 2 and 16,384 and x can be a sub-integer of the value 0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75, or 0.875.
When n = 1, x = 0, i.e. baud rate divisors with values between 1 and 2 are not possible.

3,000,000 / 32,768 = 91.552734375

the closest we can achieve is therefore 91.5. that's an error of .0576%.... that's well within tolerance.

now i'm kind of curious to see if this all actually works. logging at 4X normal speed would probably be largely pointless, but i wouldn't complain about ~44Hz full stream datalogging.

[Six_Shooter]

I wouldn't mind a faster logging stream.
I know I've missed events because of the sampling rate being so slow.

Never mind going to the 160 baud stream....

[RobertISaar]

i'm making it a point to never touch another 160 baud system....

imagine 32.768Kbaud using mode 3 commands... a good 30 to 40Hz can be achieved with very few items being logged at 8192. you would probably be logging faster than the ECM grabs A/D values or goes through minor loops...

[Six_Shooter]

Don't tease me...

[1project2many]

And you can remove data that you don't want and replace it with multiple sends of data you do want.