Advanced Search

what do you mean by a configuration problem, in a .hal file?

OK - I don't know how this got so 'catty wompus' but... turns out - it was my stepper setting. Originally - it was 8000 steps /inch. which seems to be what was in my 'backup' .INI. When I checked my step setting and did the math - I realized it should be 4000 steps. That improved the movement, but I was still getting 'follow errors' (or something like that). One thing I DID notice is - I was out by a factor of 2 when I did a G0 X.5 command. I went back to 8000 and suddenly I was out by a factor of 4... oops - wrong direction. Changed to 2000 steps/in and all my errors have gone and I am able to use the machine again.

I have to confirm yet - but I'm using a chinese 'blue' board parallel port controller and I'm wondering if my stepper switch settings are documented wrong.

Anyways - crisis resolved. Thank you for your help - this discussion can be closed.

Hi again,

The bug has been found in the driver. It was indeed not counting correctly resulting in trying to overflow the buffer (that caused an abort without writing beyond the buffer). I will be making a patch for it tomorrow.

Also, the mrje70a device is something of a piece with very complex modbus communication (I downloaded the comms spec). It seems to use "record reads and writes in depth" where several values are read/write from an address in a structure like fashion. These must be read/written using a single modbus transaction (when the "continuous read/write" column set to "impossible" it seems to denote that it is a record read/written in depth and not by incremental address). That is the first time I've seen such a hack. Luckily, the driver can do that (but you need to ignore the misalignment warnings from mesambccc). However, some extra pin setup is needed before you want to start writing or you will be sending half or malformed data. I'll show how to do that when I have made the patch.

All that said, the patch will also include a fix for the completely brain-dead mrje70a communication, where it returns a single signed byte (!) in a word register's LSB and zeros the MSB while leaving the user the hassle to tackle the sign extension. The patch will allow you to perform the proper sign extension to s32, s64 or float hal types by introducing a byte type.

slowpoke wrote:

Aciera wrote:

I have not used the anglejog component other than playing around with the sim config. As I understand it the 'scale' factor is used to avoid stair stepping in the tool path. Maybe the original discussion can give you some more clues:
forum.linuxcnc.org/38-general-linuxcnc-q...mode?start=10#253252

[edit]
I would tend to use the default values used in the sim config and adjust the
'max_vel',  'max_accel' pins (and possibly 'accel_fraction_in' for fine tuning) 
Thanks for your help. I should play with the sim config, I'm not sure how to do that?

Okay, figured out what I was doing wrong (anglejog.N.iscale-factor), so I now have angle jogging working.

Thanks for all your help!