Charge Amp Frequency

Hi

The DOS line endings are down to you

The error on line 11 is probably because there is a space in the assignment of the thread speed, had something similar when trying to make a sim of it
eg
threadX= 1000000

regards

Hi
Yes found a couple of space's and removed them, now I have this error

CP_my-mill_test.hal:18: Pin 'charge_pump.enable' does not exist
7070

checked the file and "charge_pump.enable" is there?

Steve

CP_my-mill_test.hal:18: Pin 'charge_pump.enable' does not exist
7070

checked the file and "charge_pump.enable" is there?

That is probably my fault, change it to charge-pump.enable

I have taken to naming components as a single word where possible.
As Andy says, if you put a a hyphen in a module-name and try to compile it with comp
the python parser tries to subtract name from module, very annoying.

Good morning

I can find it in this line only

net estop-out charge-pump.enable iocontrol.0.user-enable-out

is this correct?

Steve

yes thats correct Steve

Hi
I have looked over the .hal and .ini files and corected a number of spacing errors and I am now geting the following

HAL: ERROR: thread 'base-thread' not found
CP_my-mill_test.hal:26: addf failed
5766
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal componentsCP_my-mill_test.hal:26: addf failed
5766


I have double checked the files and all looks fine to my limmited experiance,





Steve

Hi

HAL: ERROR: thread 'base-thread' not found
CP_my-mill_test.hal:26: addf failed

I managed to make a sim to test this.
The reason is that base-thread has not been created, instead it is called thread1

Why this has happened is another matter altogether
You will also note that the servo-thread has been given the rate that was supposed to be for the base-thread and that thread1, which should be the fastest thread, is the default 1000000ns



I am not sure what is happening here, I will try some experiments.

There are some other issues with the hal file, you are creating a signal called charge-pump with this line
net charge-pump <= charge-pump.out

but that is not the problem right now

regards

Hi

I have finally got to the bottom of this, through something Andy mentioned which is not in the docs for threads.

Not only do threads have to be created in order of frequency speed, fastest first, but the ascending threads need to be multiples of the fastest one.

So if your fastest thread is 30000, you can create a second thread of 60000 or 90000 but not 40000.
This had not cropped up previously because I actually wanted a much slower thread which presumably was a multiple of the fastest one, even though I had not done so consciously.

What this means is that you cannot have a fast thread of say 40000 for your charge pump, unless your new 'servo-thread / base-thread' is 80000 and the extra thread is 1000000 to replace the old servo thread

This will probably restrict your steppers considerably, for the sake of getting a charge pump to work

I should first see if your base thread will activate the charge pump as it is. I have no idea if you have actually tried this or just looked at the figures and thought it would not.
If you have tried the config, but could not get it out of Estop, that is not the same thing.
stepconf has never given me a config which works with the charge-pump activated BOBs I have and I had to change the logic to get both Estop and charge-pumps to work.

If that does not work, try making your base thread 42000 say and see if the charge pump works AND the steppers operate OK
That will be far better than trying to run an extra thread

regards

Hi

Thanks for all the effort you have but in to this, I may well just not use the charge-pump as I have the steppers working very well and doing every thing I need.

Thinking about the frequency to switch the CP is it possible to use SIGGEN to generate the 12Khz and link the CP to it, or am I not understanding how it all works again

again thanks for all the help and just wait for the next problem

Steve