Mistaken wrote:Yah dont ruin a good turbo Whatadsm, I'll have a spare actuator to dissassemble early next week.
BTW did it move to a home position at all when you powered it up? I read that there is a safe mode it goes into when it doesnt pick up a valid signal that moves it to a specified location.
Also i dont think you could go into production with a control unit if it wasnt CAN based, unless you sell the turbo and controller together since it will most likely have to be opened up and modified. So CAN still might be the only route.
Whatadsm...any chance you have access to a CAN controller to see what messages it is pulsing to the ECU?
That is not exactly true. It very common for all mechanical systems which do not have an absolute encoder to home to torque or travel limit or something. That way you have a known home position along with an encoder count. Basic premise... that is totally normal operation even if the unit DID connect.
Ultimately CAN IS the best route, although it will likely be the most difficult.
I am in the middle of doing some CAN disection work on it now. I have some data on it, but will know more later today... just stuck at work now.
blownhemi wrote:Actually, frequency might be the key... if the ST is receiving the PWM with a quick A/D unit, too low a frequency will either charge the sample and hold capacitor in the A/D to the high or the low level. Frequency would have to be magnitudes higher than the A/D samping time to get the mean value of the signal.And if it's using a timer to measure the PWM signal, it could overflow during the period of no voltage level change in the signal, if the frequency is too low. I'd try higher frequencies, I don't think it can hurt the pins. Keep in mind, even if you transmission with the bitrate of CAN, you COULD make CAN bits, but definitely not a CAN frame, with valid fields, and a mathing CRC.
Did you send in a differential signal, or just a normal signal on CAN-hi?
I really hoped something would come of this, although I thought all along that the easier solution for Delphi would have been to have the PWM lines seperate, and easier for Holset not to lead a wire out for those pins.
As a side note, how do you know, which are the power, ground, can-hi and can-lo wires? Is it written on the housing somewhere (sorry, I haven't yet seen this turbo up close and personal) ?
Like I said before I put the correct differential CAN dominant high signal on the bus.
IMHO I'm not going to spend my time trying every PWM frequency to try to get it to work. If it was being sampled through a RC and ADC I'm not sure how it's own can messages wouldn't get in the way... or other messages on the bus for that matter. ?! when would it know to sample? The more I think about it, although I would love for it to be a simple PWM signal I just don't think it is in the cards. It might however be in the firmware and just not brought out to the hardware. Again I am not willing to look at that quite yet until I am sure the CAN won't lead anywhere.
I am also POSITIVE i have it wired correctly. It is talking, and I am sure of it.
Mistaken wrote:There is a wiring diagram floating around a few forums for it. Outside pins are power and ground, inside are CAN Hi and CAN low.
Can't see the picture at work but the CAN lines are NOT in the middle with power and ground on the outside. Can lines are next to each other on one side with power and ground next to each other on the other side.