Help me understand this simple schematic

[Noitoen]

That is for position mode

Don't have that info in the manual I found online. Still think that it's a parameter issue

[Noitoen]

Maybe more than one type of Dyn4 drives around

[J Tiers]

Maybe more than one type of Dyn4 drives around

Sure..............

[RB211]

They all do RS232 for the USB setup, The details I showed are in Appendix C. Very well could be an error in the manual, conflicting information. Tech support via email though aligns with what I read in Appendix C. I don't think any of their motors are rated to go 6000 RPM, mine is rated 3000 RPM with a max of 5000, and I took it to 5500 via RS232. I think most of us are familiar with VFD's and just how flexible they are with setup and programming, so I was pretty taken back by how simplified the servo drive came across when it had to deal with input configuration, as there isn't any input configuration. This is how you do it, like it or not!

[Noitoen]

Sure..............

I've seen that in the manual I've downloaded and it's for all 3 models.

[genea]

I am going to take a known good cable(twisted pair) and only hook up the AIN+ and AIN- (0 to 10v) to the JP4 header. Try the Acorn and will try the regulated power supply. If this does not work as expected, I'm going to assume my JP4 is fried and waste any more time with analog control when RS232 works perfectly. I understand your points but if you witnessed how unreliable analog control has been on this, I'd think you'd take your digital chances.

The fact that you're using 0-10v as analog input indicates to me that you're trying to run in position (pulse) servo mode. I also think that the graph in post #17 is related only to position servo mode.

The post no. 1 schematic title shows that this is for the spindle. I don't think you need or want a dead zone to control spindle speed, or direction so position mode doesn't seem appropriate. The dead zone helps prevent oscillations when the axis is at the commanded position and there's noise on the input. With that in mind, and I may be wrong, but I think you should be operating in speed servo mode. You can command a full stop or reverse polarity of the DAC output if you want a quick reverse for power tapping. Acorn keeps track of the number of revs. What am I missing?

From what I see in the manual the AIN+ and AIN- inputs (in speed servo mode) range between -10v to +10v (see the chart on page 6 of the manual).

You don't say so, but when you applied 5v to the DIR lines did you do it through the existing 2K resistor? If so, that may have resulted in insufficient current through the LED. Or did you connect directly to the DIR+ pin? I couldn't find current limits specs for the LED, but in some input circuit examples they use 270 ohms with a 5v input.

[RB211]

The fact that you're using 0-10v as analog input indicates to me that you're trying to run in position (pulse) servo mode. I also think that the graph in post #17 is related only to position servo mode.

The post no. 1 schematic title shows that this is for the spindle. I don't think you need or want a dead zone to control spindle speed, or direction so position mode doesn't seem appropriate. The dead zone helps prevent oscillations when the axis is at the commanded position and there's noise on the input. With that in mind, and I may be wrong, but I think you should be operating in speed servo mode. You can command a full stop or reverse polarity of the DAC output if you want a quick reverse for power tapping. Acorn keeps track of the number of revs. What am I missing?

From what I see in the manual the AIN+ and AIN- inputs (in speed servo mode) range between -10v to +10v (see the chart on page 6 of the manual).

You don't say so, but when you applied 5v to the DIR lines did you do it through the existing 2K resistor? If so, that may have resulted in insufficient current through the LED. Or did you connect directly to the DIR+ pin? I couldn't find current limits specs for the LED, but in some input circuit examples they use 270 ohms with a 5v input.

Did it both ways with Dir input. Again, the setup page in the software is very basic, three radio buttons, Position, Speed, or Torque mode. You can read the current settings of the drive and save the current settings, and set the gains. 0 to 10v is CW, -10 to 0 is CCW. OR you can reverse the spindle via the schematic which is also backed up in appendix C. My Acorn does 0 to 10 for spindle. The new Acorn6 will do +/- 10v.

[J Tiers]

So, it went to 3000 with a +5v input.

That's an incredible coincidence, when you look at the spec page. It shows that +5 is 3000 rpm. So the analog input was probably working fine.

It looks more likely that the process for switching scaling did not work right, or was not done right.

[RB211]

So, it went to 3000 with a +5v input.

That's an incredible coincidence, when you look at the spec page. It shows that +5 is 3000 rpm. So the analog input was probably working fine.

It looks more likely that the process for switching scaling did not work right, or was not done right.

When the new drive arrives next week hopefully, first thing I will do is plug in that test configuration and I fully suspect to see 500 RPM per Appendix C and tech support email I posted. The drive is already on its way to the land of Evan.

If there is one thing that has been proven it is that the manual is filled with contradictory information. The schematic I posted earlier is what the community has settled upon for spindle drive control. I am not the first one to use this setup for a Taig nor an Acorn. In fact these servos are a popular choice for small CNC conversions.

[J Tiers]

............................

If there is one thing that has been proven it is that the manual is filled with contradictory information. ..................................s.

A reasonably common problem.

So many companies apparently do not do what is required...... You write the manual FIRST, then you make the hardware etc do what the manual says. If that is either not possible, or not optimal, for some function, then you edit the manual first, to the new preferred way the function should work, and then make the changes to the hardware etc so that it does what the revision says.

The manual is a "part", or "component". It should be under ECO control like any other component. I know... that seems so rigid and uncompromising. Yep, that would be because it IS rigid and uncompromising. It's how you get a product out correctly with the fewest screwups possible, which would be none.

If companies would do that, the manual would always agree with the product. When they do not, it seems almost as if they really don't care how the product works........ or that they don't even know what it is supposed to do.

[Joel]

it seems almost as if they really don't care how the product works........ or that they don't even know what it is supposed to do.

Competency is getting more and more sparse, and at an accelerating rate. It now seems to be the rule and not the exception, as I am sure many here have likewise noticed. Hardware, software, documentation, customer service - everything.
I expect A.I. to breed an even more pervasive, if not ubiquitous level of extreme and painful ignorance.

[skunkworks]

Competency is getting more and more sparse, and at an accelerating rate. It now seems to be the rule and not the exception, as I am sure many here have likewise noticed. Hardware, software, documentation, customer service - everything.
I expect A.I. to breed an even more pervasive, if not ubiquitous level of extreme and painful ignorance.

eh. It will be fine. Smiley face.

[RB211]

Well, so far I've gotten a 32bit 80+ MHZ Arm Cortex processor to blink an led like an airplane strobe light... What a waste of silicon... Had I stuck to programming full time since high school, I'd actually be good at this stuff...

[J Tiers]

Well, you seem to have a timer function sorted out..... Along with a somewhat different version of "hello world", a bit akin to sputnik. And, don't forget, you have an actual functioning program, so you must have the address space sorted out reasonably, I/O working, etc.

That's actually a good start, for the first use of a new processor.

[RB211]

Well, you seem to have a timer function sorted out..... Along with a somewhat different version of "hello world", a bit akin to sputnik. And, don't forget, you have an actual functioning program, so you must have the address space sorted out reasonably, I/O working, etc.

That's actually a good start, for the first use of a new processor.

STM32 F411. Problem with it is there's 20 different ways to program them and you need to settle on an environment early on. Most books showcase the older methods and I want to use what STM recommends going forward. The book I'm reading uses Keil's IDE, and I'm not.