Garrett 712120 VNT Hella 6NW 008 412 actuator.
Garrett 712120 VNT Hella 6NW 008 412 actuator.
(08-18-2009, 09:13 AM)tomnik I am looking for the pin destination of the Garrett (Hella) electronic actuator for the VTGs.
I thought I saw it some when but can not find it.
(08-18-2009, 09:13 AM)tomnik I am looking for the pin destination of the Garrett (Hella) electronic actuator for the VTGs.
I thought I saw it some when but can not find it.
Thanks.
Let me know the frequency of the PWM signal when you have it.
12 V?
I work on getting a "black box" with boost pressure input and PWM output. First step is to controll the N75 valve of the TDIs connected to vac and a vac actuator on the VTG. Maybe I can alternatively connect the electronic actuator also to the PWM signal.
We will see.
Tom
(09-01-2009, 09:01 AM)winmutt VTG or VNT? What model is this for? John what PDF is that from?
(09-01-2009, 09:01 AM)winmutt VTG or VNT? What model is this for? John what PDF is that from?
Thanks,
meanwhile I get the parts build to operate the vac valve N75 from Audi/VW for the vac actuator. Hopefully the PWM signal can also control the electronic actuator in the future with some minor modification in case the N75 solution is not satisfying me.
Time will tell..
Tom
(09-01-2009, 09:28 AM)Tymbrymi I might have a chance to verify the frequency today. Time will tell!
(09-01-2009, 09:28 AM)Tymbrymi I might have a chance to verify the frequency today. Time will tell!
I haven't had a chance to double check it on hardware, but I did fine a camera picture I took of the portable scope that has the period on it. The period is 7.1ms which works out to 140-141Hz. Vanes full open and fully closed don't respond to 0% and 100%, it goes from something like 10%-95% so that a short to ground or 12V won't cause any problems (it'll go to vanes fully open).
So pin 1 is the signal? I am going to get a working sample of the arduino code for controlling PWM motors and give this puppy a spin! Thanks for breaking the code man, this was an INVALUABLE post.
(09-03-2009, 01:18 PM)winmutt So pin 1 is the signal? I am going to get a working sample of the arduino code for controlling PWM motors and give this puppy a spin! Thanks for breaking the code man, this was an INVALUABLE post.
(09-03-2009, 01:18 PM)winmutt So pin 1 is the signal? I am going to get a working sample of the arduino code for controlling PWM motors and give this puppy a spin! Thanks for breaking the code man, this was an INVALUABLE post.
I've renamed this thread appropriately to deal with the GT Hella actuator specifically.
Tymbrini, were you able to scope it and confirm the frequency? A printout of the wave would be tits. As Iposted in the arduino thread, the closest I get to 140hz is 125hz with the internal timing. Now I can bit bang the outputs in code however any interrupts would have to be carefully timed to maintain the frequency, this greatly limits the amount of reading I can do. A read out or that picture of the wave would be a good start. If your up for it see if you can get the motor to respond to 125hz. If we can get it to run on 125hz then that frees up the board for all kinds of interrupts.
Winmutt, it's Tymbrymi with a "y" and an "m"
Unfortunately, I didn't get a chance to get it working last night. Work kept me late and I bought an iPhone so I ended up playing with my cool toy
My old phone's camera was crappy on a good day, but I will take a picture of the waveform created by the function generator. I'll also post info on when the actuator actually starts to move since there is some dead band around the edges.
That Arduino's PWM module is freaky and a PITA. G'luck with getting that to work at the 140Hz frequency. I will check it at 125Hz for you though!
(09-04-2009, 12:29 PM)winmutt Well like I said I can bit bang it, its just that 140hz is very odd for a PWM I would think, its not a factor of binary.
Quote:If I'm reading the datasheet properly, those are the max frequencies when using those specific clock sources. Look at page 120 of the datasheet, and use "Fast PWM mode". You'll use the 16Mhz clock frequency divided by 8 as the clock source to the timer (TCCR1B = xxxxx010). This determines the frequency of the "ticks" (500ns). Since it is a 16-bit counter, you can have up to 65,535 ticks in the period. 7.1ms / 500ns = 14,200 ticks, which will give you the 140Hz frequency. Use the fast PWM mode where you put "top" in ICR1 (WGM13:0 = 14), and load the 14,200 into ICR1. In order to change the duty cycle you will load a number into OCR1x between 0 and 14,200. The percentage of 14,200 you enter will be the duty factor.
Did that make any sense? The datasheet is still pretty confusing to me...
(09-04-2009, 12:29 PM)winmutt Well like I said I can bit bang it, its just that 140hz is very odd for a PWM I would think, its not a factor of binary.
Quote:If I'm reading the datasheet properly, those are the max frequencies when using those specific clock sources. Look at page 120 of the datasheet, and use "Fast PWM mode". You'll use the 16Mhz clock frequency divided by 8 as the clock source to the timer (TCCR1B = xxxxx010). This determines the frequency of the "ticks" (500ns). Since it is a 16-bit counter, you can have up to 65,535 ticks in the period. 7.1ms / 500ns = 14,200 ticks, which will give you the 140Hz frequency. Use the fast PWM mode where you put "top" in ICR1 (WGM13:0 = 14), and load the 14,200 into ICR1. In order to change the duty cycle you will load a number into OCR1x between 0 and 14,200. The percentage of 14,200 you enter will be the duty factor.
Did that make any sense? The datasheet is still pretty confusing to me...
(09-04-2009, 11:30 AM)Tymbrymi Winmutt, it's Tymbrymi with a "y" and an "m"
the 140Hz frequency. I will check it at 125Hz for you though!
#include <avr/interrupt.h>
int vntPin = 9; // LED connected to digital pin 9
int vanePos = 0 ;
int cnt = 0;
int dir = 0;
void setup() {
//graph
Serial.begin(57600);
//140hz 7.1ms ==
TCCR1A = _BV(COM0A0) | _BV(WGM01);
TCCR1B = _BV(CS02) | _BV(CS00);
OCR1A = 222;
}
void loop() {
if (cnt % 1000==0) {
if (dir==1) {
if(vanePos < 255) {
vanePos +=25.5;
if (vanePos>255)vanePos=255;
}
else {
dir=0;
}
}
else {
if(vanePos >0) {
vanePos -=25.5;
if (vanePos<0) vanePos=0;
}
else {
dir=1;
}
}
analogWrite(vntPin, vanePos);
}
Serial.println(analogRead(0));
delay(5);
cnt+=5;
}
Things are looking good. This is my first version of running code. If the frequency is right then it *should* continuously open and close the vanes in 10% increments.. Current I have pin 9 (pwm out pin on the arduino) hooked up to analog in pin 0 which allowed me to read the PWM signal and verify at least that the duty cycle is cycling properly.
#include <avr/interrupt.h>
int vntPin = 9; // LED connected to digital pin 9
int vanePos = 0 ;
int cnt = 0;
int dir = 0;
void setup() {
//graph
Serial.begin(57600);
//140hz 7.1ms ==
TCCR1A = _BV(COM0A0) | _BV(WGM01);
TCCR1B = _BV(CS02) | _BV(CS00);
OCR1A = 222;
}
void loop() {
if (cnt % 1000==0) {
if (dir==1) {
if(vanePos < 255) {
vanePos +=25.5;
if (vanePos>255)vanePos=255;
}
else {
dir=0;
}
}
else {
if(vanePos >0) {
vanePos -=25.5;
if (vanePos<0) vanePos=0;
}
else {
dir=1;
}
}
analogWrite(vntPin, vanePos);
}
Serial.println(analogRead(0));
delay(5);
cnt+=5;
}
Enjoy!!
http://www.youtube.com/watch?v=KTqXGK3ZsWk
Pictures... http://picasaweb.google.com/Tymbrymi2/GarretActuator captions with pinouts coming soon.
Winmutt, totally forgot 125Hz.
Still no scope *but* I did find a plug on a '9 6vw that fits. Its not water proof like it should be properly. Today I will call Hella USA and see if they can provide me with any more information about this actuator.
(09-08-2009, 02:21 PM)winmutt Hella's website has been down since Sat. I put in a call and got a vm box. We'll see if I get a call back.
(09-08-2009, 02:21 PM)winmutt Hella's website has been down since Sat. I put in a call and got a vm box. We'll see if I get a call back.
Hella's website is back up today. I sent an email and called the guy listed as the tech contact for the actuators division. With any luck I'll get a call back. Still no scope......
[edit]
Left a note on a neigbors mailbox last night, he had some ham gear up so I figured there might be a good chance he had a scope. Has one he hasnt used in 20yrs and is all but letting me have it.
Quote:I have been informed by Product Management that this item is proprietary to a manufacture and no information can be given out because of contractual agreements.
Time to talk to Garrett.
Response from Hella.
Quote:I have been informed by Product Management that this item is proprietary to a manufacture and no information can be given out because of contractual agreements.
Something interesting on how Holset controls theirs, maybe it will be helpful.
From: http://www.holset.co.uk/pics-related/3_1...tion10.exe
Some movement on this again. Lance has sent me his old actuator. I am still looking for a scope, one popped up on CL cheap enough but I am flat broke. Also I got a response on the arduino forums, I had a few more questions but might finally be on the right track.
(09-05-2009, 10:14 PM)Tymbrymi Enjoy!!Is that 10v at 100% duty cycle?
http://www.youtube.com/watch?v=KTqXGK3ZsWk
Pictures... http://picasaweb.google.com/Tymbrymi2/GarretActuator captions with pinouts coming soon.
Winmutt, totally forgot 125Hz.
(09-05-2009, 10:14 PM)Tymbrymi Enjoy!!Is that 10v at 100% duty cycle?
http://www.youtube.com/watch?v=KTqXGK3ZsWk
Pictures... http://picasaweb.google.com/Tymbrymi2/GarretActuator captions with pinouts coming soon.
Winmutt, totally forgot 125Hz.
(10-22-2009, 11:22 PM)winmutt Is that 10v at 100% duty cycle?
(10-22-2009, 11:22 PM)winmutt Is that 10v at 100% duty cycle?
Kind of. Arduino only makes 5volts for the PWM signal . Any chance of you testing with 5v? Still no luck getting a scope down here. I tested last night on two controllers no luck.
(10-23-2009, 01:41 PM)winmutt Kind of. Arduino only makes 5volts for the PWM signal . Any chance of you testing with 5v? Still no luck getting a scope down here. I tested last night on two controllers no luck.
(10-23-2009, 01:41 PM)winmutt Kind of. Arduino only makes 5volts for the PWM signal . Any chance of you testing with 5v? Still no luck getting a scope down here. I tested last night on two controllers no luck.
WOW! You guys have made some serious progress since I was last on here. Guess I can scrap my actuator mods that I started designing before the summer and never finished (involving directly controlling the motor in the actuator and using a TPS sensor for feedback)...
I left my turbo in the shed at my moms house and it flooded over the summer while I was out of state, so its completely rusted ...I'll be looking for a new turbo soon, and can hopefully get this project done, finally.
winmutt: if you feel like driving up to athens any time, u can use my old HP 120B scope, it'll do a few KHz, not the latest tech but it works... old heavy and full of vacuum tubes
(10-27-2009, 08:42 AM)winmutt Well I can tell you that 12volt + will fry the board :~( Good thing I have 2!
(10-27-2009, 11:36 PM)300SD81 Guess I can scrap my actuator mods that I started designing before the summer and never finished (involving directly controlling the motor in the actuator and using a TPS sensor for feedback)...
(10-27-2009, 08:42 AM)winmutt Well I can tell you that 12volt + will fry the board :~( Good thing I have 2!
(10-27-2009, 11:36 PM)300SD81 Guess I can scrap my actuator mods that I started designing before the summer and never finished (involving directly controlling the motor in the actuator and using a TPS sensor for feedback)...
(10-28-2009, 09:48 AM)Tymbrymi(10-27-2009, 11:36 PM)300SD81 Guess I can scrap my actuator mods that I started designing before the summer and never finished (involving directly controlling the motor in the actuator and using a TPS sensor for feedback)...
Wasn't that for the big Holset turbo? We still don't have the CAN messages for that.
(10-27-2009, 08:42 AM)winmutt Well I can tell you that 12volt + will fry the board :~( Good thing I have 2!
(10-28-2009, 09:48 AM)Tymbrymi(10-27-2009, 11:36 PM)300SD81 Guess I can scrap my actuator mods that I started designing before the summer and never finished (involving directly controlling the motor in the actuator and using a TPS sensor for feedback)...
Wasn't that for the big Holset turbo? We still don't have the CAN messages for that.
(10-27-2009, 08:42 AM)winmutt Well I can tell you that 12volt + will fry the board :~( Good thing I have 2!
Made this up while I was bored in class.. Maybe this time I'll actually get something installed in the car before I change my mind and scrap the project again. I'm using an ethernet interface this time so I can easily test with a laptop rather than constantly reprogramming micros.. Still have the USB boost gauge I made a long time ago, so I can even use the laptop as a controller for a little while. Ordered the parts already, so if I do't get distracted by something again, I should have it built in a week or 2, but somehow I always do..
My prof looked at me like I was crazy when he saw my screen today
EDIT:
Started writing the code for this thing, has anyone confirmed if the actuator cares about the PWM frequency or not? Is it actually sampling the frequency, or just the average analog voltage? The lowest I can get my PWM on the uC is 3+KHz unless I lower the clock speed (64Mhz/4/16 = 1MHz timer frequency, but it the timer for PWM is only 8 bits). Might try feeding it an analog voltage this weekend, and if that dosen't work, I'll just bit-bang the pwm...
+12v PWM fried one of the controllers (bloated a resistor) and the TTL of 5v does nothing. Either my frequency is still off or its more than 5v. In the video Tymbrymi is using 10v. I'll be interested to see how things go. BTW long time no see, you back at school? I can send you the fried controller if you want to fix it and test with.
(10-29-2009, 12:38 PM)winmutt +12v PWM fried one of the controllers (bloated a resistor) and the TTL of 5v does nothing. Either my frequency is still off or its more than 5v. In the video Tymbrymi is using 10v.Seems weird that something in a car would use something other than 12v or 5v..
(10-29-2009, 12:38 PM)winmutt I'll be interested to see how things go. BTW long time no see, you back at school? I can send you the fried controller if you want to fix it and test with.Yep, back at school for a few months now, barely had time to drive the car lately, but I have a little time off for now. My controller should still be good, don't think any water got into it when it flooded, buy my turbos siezed Might be fixable if I completely disassemble it, but its rusted solid..
(10-29-2009, 12:38 PM)winmutt +12v PWM fried one of the controllers (bloated a resistor) and the TTL of 5v does nothing. Either my frequency is still off or its more than 5v. In the video Tymbrymi is using 10v.Seems weird that something in a car would use something other than 12v or 5v..
(10-29-2009, 12:38 PM)winmutt I'll be interested to see how things go. BTW long time no see, you back at school? I can send you the fried controller if you want to fix it and test with.Yep, back at school for a few months now, barely had time to drive the car lately, but I have a little time off for now. My controller should still be good, don't think any water got into it when it flooded, buy my turbos siezed Might be fixable if I completely disassemble it, but its rusted solid..
(10-29-2009, 12:21 AM)300SD81 Started writing the code for this thing, has anyone confirmed if the actuator cares about the PWM frequency or not? Is it actually sampling the frequency, or just the average analog voltage?
(10-29-2009, 12:21 AM)300SD81 The lowest I can get my PWM on the uC is 3+KHz unless I lower the clock speed (64Mhz/4/16 = 1MHz timer frequency, but it the timer for PWM is only 8 bits). Might try feeding it an analog voltage this weekend, and if that dosen't work, I'll just bit-bang the pwm...
(10-29-2009, 02:06 PM)300SD81 Did you get any voltage readings off the original car when you had it on a scope?
(10-29-2009, 12:38 PM)winmutt +12v PWM fried one of the controllers (bloated a resistor) and the TTL of 5v does nothing.
(10-29-2009, 12:21 AM)300SD81 Started writing the code for this thing, has anyone confirmed if the actuator cares about the PWM frequency or not? Is it actually sampling the frequency, or just the average analog voltage?
(10-29-2009, 12:21 AM)300SD81 The lowest I can get my PWM on the uC is 3+KHz unless I lower the clock speed (64Mhz/4/16 = 1MHz timer frequency, but it the timer for PWM is only 8 bits). Might try feeding it an analog voltage this weekend, and if that dosen't work, I'll just bit-bang the pwm...
(10-29-2009, 02:06 PM)300SD81 Did you get any voltage readings off the original car when you had it on a scope?
(10-29-2009, 12:38 PM)winmutt +12v PWM fried one of the controllers (bloated a resistor) and the TTL of 5v does nothing.
(10-29-2009, 02:12 PM)Tymbrymi Unfortunately, it DOES care about the frequency. Not sure what its range is, but I remember it didn't work at just any old frequency. I don't think it'll work on an analog voltage either.
You could always get a better PIC That definitely sucks though. It's annoying to have to bit-bang stuff when you have a hardware peripheral that should be able to do it.
Yep! But they're on my old phone, which I won't be able to get to till tonight. I'll try and post them if I get the chance.
#include <p18cxxx.h>
#include "enc28j60.h"
#include "typedefs.h"
void init(void);
void pwm_init(void);
void isr_high(void);
void isr_low(void);
volatile BYTE pwm_duty_cycle = 128;
#define PWM_HIGH_STATE 0
#define PWM_LOW_STATE 1
/**************** INTERRUPTS ****************/
#pragma code high_vector=0x08
void interrupt_at_high_vector(void) {
_asm GOTO isr_high _endasm
}
#pragma code
#pragma code low_vector=0x18
void interrupt_at_low_vector(void) {
_asm GOTO isr_low _endasm
}
#pragma code
#pragma interrupt isr_high
void isr_high(void) {
/**High Priority ISR**/
/**Timer0 Overflow**/
//TMR0L = 32;
static BYTE pwm_num_ovrflw = 0;
TMR0L = 40;
if (pwm_num_ovrflw == pwm_duty_cycle) {
// PWM Pin Low
PORTCbits.RC5 = PWM_LOW_STATE;
}else if (pwm_num_ovrflw == 0xFF) {
pwm_num_ovrflw = 0;
// PWM Pin High
PORTCbits.RC5 = PWM_HIGH_STATE;
}
pwm_num_ovrflw++;
//Clear Interrupt Flag
INTCONbits.TMR0IF = 0;
}
#pragma interruptlow isr_low
void isr_low(void) {
/**Low Priority ISR**/
}
/************** END INTERRUPTS **************/
void main (void) {
init();
while (1) {
_asm NOP _endasm
}
}
void init (void) {
//Set Oscillator to 64MHz
OSCCONbits.IRCF0 = 1;
OSCCONbits.IRCF1 = 1;
OSCCONbits.IRCF2 = 1;
//Set Pin 12 Output High (Pin 12 is the power source for the level shifter)
TRISBbits.TRISB5 = 0;
PORTBbits.RB5 = 1;
//Enable Interrupt Priority
RCONbits.IPEN = 1;
//Disable All Individual Interrupts
INTCON = 0;
INTCON3 = 0;
//Set All Peripherial Interrupts = Disabled & Low Priority
PIE1 = 0;
IPR1 = 0;
PIE2 = 0;
IPR2 = 0;
//Global High/Low Priority Interrupt Enable
INTCONbits.GIEH = 1;
INTCONbits.GIEL = 1;
// Initialize the Ethernet Module
//enc_init();
// Start PWM Output
pwm_init();
}
void pwm_init (void) {
/*
Timer0 PWM Setup
Increment at 8MHz (0.125us)
Overflow every 27.9017858us (35840Hz) (for 256 step PWM)
= Increment 223.214286x Before Overflow
-> Start Timer at 255-223 = 32
*/
// Pin 5 as Output
TRISCbits.TRISC5 = 0;
// PWM Low
PORTCbits.RC5 = PWM_LOW_STATE;
//Disable Timer0
T0CONbits.TMR0ON = 0;
// 8-Bit Timer
T0CONbits.T08BIT = 1;
// Use Instruction Clock
T0CONbits.T0CS = 0;
// 1:2 Prescaler, 8MHz
T0CONbits.PSA = 0;
T0CONbits.T0PS0 = 0;
T0CONbits.T0PS1 = 0;
T0CONbits.T0PS2 = 0;
// Enable Timer0 Overflow Interrupt
INTCONbits.TMR0IF = 0;
INTCONbits.TMR0IE = 1;
//Enable Timer
T0CONbits.TMR0ON = 1;
}
(10-29-2009, 02:12 PM)Tymbrymi Unfortunately, it DOES care about the frequency. Not sure what its range is, but I remember it didn't work at just any old frequency. I don't think it'll work on an analog voltage either.
You could always get a better PIC That definitely sucks though. It's annoying to have to bit-bang stuff when you have a hardware peripheral that should be able to do it.
Yep! But they're on my old phone, which I won't be able to get to till tonight. I'll try and post them if I get the chance.
#include <p18cxxx.h>
#include "enc28j60.h"
#include "typedefs.h"
void init(void);
void pwm_init(void);
void isr_high(void);
void isr_low(void);
volatile BYTE pwm_duty_cycle = 128;
#define PWM_HIGH_STATE 0
#define PWM_LOW_STATE 1
/**************** INTERRUPTS ****************/
#pragma code high_vector=0x08
void interrupt_at_high_vector(void) {
_asm GOTO isr_high _endasm
}
#pragma code
#pragma code low_vector=0x18
void interrupt_at_low_vector(void) {
_asm GOTO isr_low _endasm
}
#pragma code
#pragma interrupt isr_high
void isr_high(void) {
/**High Priority ISR**/
/**Timer0 Overflow**/
//TMR0L = 32;
static BYTE pwm_num_ovrflw = 0;
TMR0L = 40;
if (pwm_num_ovrflw == pwm_duty_cycle) {
// PWM Pin Low
PORTCbits.RC5 = PWM_LOW_STATE;
}else if (pwm_num_ovrflw == 0xFF) {
pwm_num_ovrflw = 0;
// PWM Pin High
PORTCbits.RC5 = PWM_HIGH_STATE;
}
pwm_num_ovrflw++;
//Clear Interrupt Flag
INTCONbits.TMR0IF = 0;
}
#pragma interruptlow isr_low
void isr_low(void) {
/**Low Priority ISR**/
}
/************** END INTERRUPTS **************/
void main (void) {
init();
while (1) {
_asm NOP _endasm
}
}
void init (void) {
//Set Oscillator to 64MHz
OSCCONbits.IRCF0 = 1;
OSCCONbits.IRCF1 = 1;
OSCCONbits.IRCF2 = 1;
//Set Pin 12 Output High (Pin 12 is the power source for the level shifter)
TRISBbits.TRISB5 = 0;
PORTBbits.RB5 = 1;
//Enable Interrupt Priority
RCONbits.IPEN = 1;
//Disable All Individual Interrupts
INTCON = 0;
INTCON3 = 0;
//Set All Peripherial Interrupts = Disabled & Low Priority
PIE1 = 0;
IPR1 = 0;
PIE2 = 0;
IPR2 = 0;
//Global High/Low Priority Interrupt Enable
INTCONbits.GIEH = 1;
INTCONbits.GIEL = 1;
// Initialize the Ethernet Module
//enc_init();
// Start PWM Output
pwm_init();
}
void pwm_init (void) {
/*
Timer0 PWM Setup
Increment at 8MHz (0.125us)
Overflow every 27.9017858us (35840Hz) (for 256 step PWM)
= Increment 223.214286x Before Overflow
-> Start Timer at 255-223 = 32
*/
// Pin 5 as Output
TRISCbits.TRISC5 = 0;
// PWM Low
PORTCbits.RC5 = PWM_LOW_STATE;
//Disable Timer0
T0CONbits.TMR0ON = 0;
// 8-Bit Timer
T0CONbits.T08BIT = 1;
// Use Instruction Clock
T0CONbits.T0CS = 0;
// 1:2 Prescaler, 8MHz
T0CONbits.PSA = 0;
T0CONbits.T0PS0 = 0;
T0CONbits.T0PS1 = 0;
T0CONbits.T0PS2 = 0;
// Enable Timer0 Overflow Interrupt
INTCONbits.TMR0IF = 0;
INTCONbits.TMR0IE = 1;
//Enable Timer
T0CONbits.TMR0ON = 1;
}
Quote: Unfortunately, it DOES care about the frequency. Not sure what its range is, but I remember it didn't work at just any old frequency. Sad I don't think it'll work on an analog voltage either.
Quote: Unfortunately, it DOES care about the frequency. Not sure what its range is, but I remember it didn't work at just any old frequency. Sad I don't think it'll work on an analog voltage either.
(10-29-2009, 05:01 PM)300SD81 I could get a better one, but what am I going to do with the stack of 18F14K22s I ordered for another scrapped project??
(10-29-2009, 05:01 PM)300SD81 Looking forward to those voltage readings before I try anything on the actuator.
(10-29-2009, 05:01 PM)300SD81 Any ideas on what the resolution of the actuator is? I kinda want to drop it down to 256 possible steps to get some cpu cycles back...
(10-29-2009, 08:07 PM)piledriver The freq sweep would be very handy
(10-29-2009, 08:07 PM)piledriver Do any of the unused pins have a feedback position output?
(10-29-2009, 05:01 PM)300SD81 I could get a better one, but what am I going to do with the stack of 18F14K22s I ordered for another scrapped project??
(10-29-2009, 05:01 PM)300SD81 Looking forward to those voltage readings before I try anything on the actuator.
(10-29-2009, 05:01 PM)300SD81 Any ideas on what the resolution of the actuator is? I kinda want to drop it down to 256 possible steps to get some cpu cycles back...
(10-29-2009, 08:07 PM)piledriver The freq sweep would be very handy
(10-29-2009, 08:07 PM)piledriver Do any of the unused pins have a feedback position output?
(10-29-2009, 09:29 PM)Tymbrymi All I know is the schematic for my CDI, which only has the three wires hooked up to it. On a hunch, I'm guessing the other two wires are for CAN control. That way the OE can choose if they want PWM or CAN for a certain application without increasing the parts they have to keep track of.
(10-29-2009, 09:29 PM)Tymbrymi All I know is the schematic for my CDI, which only has the three wires hooked up to it. On a hunch, I'm guessing the other two wires are for CAN control. That way the OE can choose if they want PWM or CAN for a certain application without increasing the parts they have to keep track of.
Update for anyone whos interested.. parts came in today and I got the board 99% completed..just have to go home and get a micro drill bit to attach the programming header.
If anyones even considering making this.. DO NOT attempt to solder 0805 smt components without a good set of tweezers. You end up going to walmart and getting seen in the makeup aisle by the hot girl you see at the bar every night... Or drop them, its nearly impossible to find soemthing the size of a piece of sand in carpet....
USB adapters there for scale, its not part of the circuit...
(11-03-2009, 03:48 PM)winmutt Cool man. Are you just using boost signal?
(11-03-2009, 03:48 PM)winmutt Cool man. Are you just using boost signal?
I like the #2 and particularly the alarm idea in #3.
My pressure sensors came in the fedex truck today. I am just going to suck it up and buy a scope since I can't find a decent one to borrow.
(11-04-2009, 04:53 PM)winmutt I like the #2 and particularly the alarm idea in #3.
My pressure sensors came in the fedex truck today. I am just going to suck it up and buy a scope since I can't find a decent one to borrow.
(11-04-2009, 04:53 PM)winmutt I like the #2 and particularly the alarm idea in #3.
My pressure sensors came in the fedex truck today. I am just going to suck it up and buy a scope since I can't find a decent one to borrow.
(11-04-2009, 09:36 PM)300SD81I know. The one I have is maybe 3x older than the benz(11-04-2009, 04:53 PM)winmutt I like the #2 and particularly the alarm idea in #3.
My pressure sensors came in the fedex truck today. I am just going to suck it up and buy a scope since I can't find a decent one to borrow.
You shouldn't need too good of a scope if your only using it to look at the PWM output. Mines older than my Benz and completely out of calibration, but I can still find 140Hz pretty easily. Just connect your scope to 60Hz AC, mine can take up to 300V, so I just use wall power, but it shoudln't be took hard to find a transformer that outputs 5, 9 or 12 VAC. Adjust it so that 60Hz takes up 7 units on the display, then connect your PWM to the scope, only changing the voltage sensitivity, 140Hz should be 3 units.
(11-04-2009, 09:36 PM)300SD81I know. The one I have is maybe 3x older than the benz(11-04-2009, 04:53 PM)winmutt I like the #2 and particularly the alarm idea in #3.
My pressure sensors came in the fedex truck today. I am just going to suck it up and buy a scope since I can't find a decent one to borrow.
You shouldn't need too good of a scope if your only using it to look at the PWM output. Mines older than my Benz and completely out of calibration, but I can still find 140Hz pretty easily. Just connect your scope to 60Hz AC, mine can take up to 300V, so I just use wall power, but it shoudln't be took hard to find a transformer that outputs 5, 9 or 12 VAC. Adjust it so that 60Hz takes up 7 units on the display, then connect your PWM to the scope, only changing the voltage sensitivity, 140Hz should be 3 units.
(11-05-2009, 12:26 AM)winmutt I know. The one I have is maybe 3x older than the benz
(11-05-2009, 12:26 AM)winmutt I know. The one I have is maybe 3x older than the benz