Stepper precision +-5%

JoergS5

You are probably both right, modern steppers and drivers will have changed all. The document I found seems to be very old.

Maybe the best approach is to build a test station, measure and compare different solutions, then select the best for the requirement. I wished there were better books about measuring. I have problems finding good sources how to use dial gauges etc.

@arhi said in Stepper precision +-5%:

anyhow I have often access to these (and similar) encoders so we can do it in second batch if not now

Sounds good - let´s wait for a time to do this when almost nobody speaks any more about coron...

arhi

@JoergS5 said in Stepper precision +-5%:

BTW think of me at 11th, this is my birthday.

happy birthday

Unfortunately, I did not do anything with this yet. I managed to find some code that simulates profibus slave but I'm having issues making code that simulates master in order to talk with this encoder. My profibus adapter is missing, ordered a new one but I doubt it will arrive quickly (not yet sent by the seller)... Still working on getting the master code to work but I have to slow down since today as ... work

JoergS5

@arhi thank you!

Improving precision is a continuous process, so take your time. Unfortunately, I don't know Profibus yet, I cannot help you.

mendenmh

@arhi There seems to be a python package which can be a profibus master:

https://pypi.org/project/pyprofibus/

arhi

@mendenmh thanks that's awesome, testing immediately

arhi

@JoergS5 said in Stepper precision +-5%:

Improving precision is a continuous process, so take your time.

yeah but I can't keep the encoder indefinitely .. this one will have to go back in a week or two ... I'll get another one next time they get a new order for few weeks again but it's not something I have on a shelf forever (these things go into some nasty military equipment made to do some ugly military stuff)

arhi

@mendenmh said in Stepper precision +-5%:

@arhi There seems to be a python package which can be a profibus master:

https://pypi.org/project/pyprofibus/

I have some data out of the encoder

PS D:\dev\profibus\pyprofibus> python3.8.exe .\arhi_readencoder.py
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa4\xc8')
bytearray(b'\x00\x00\xa7\x19')
bytearray(b'\x00\x00\xb1f')
bytearray(b'\x00\x00\xb5E')
bytearray(b'\x00\x00\xb9\xc3')
bytearray(b'\x00\x00\xbdJ')
bytearray(b'\x00\x00\xc4\x87')
bytearray(b'\x00\x00\xcb\x89')
bytearray(b'\x00\x00\xd3\xd0')
bytearray(b'\x00\x00\xd6/')
bytearray(b'\x00\x00\xe1E')
bytearray(b'\x00\x00\xeby')
bytearray(b'\x00\x00\xf7\xe7')
bytearray(b'\x00\x00E\x9f')
bytearray(b'\x00\x00x\xd5')
bytearray(b'\x00\x00\x97\x89')
bytearray(b'\x00\x00\x97i')
bytearray(b'\x00\x00\x97i')
bytearray(b'\x00\x00\x97i')
bytearray(b'\x00\x00\x97i')
Traceback (most recent call last):
  File ".\arhi_readencoder.py", line 65, in <module>
    sys.exit(main())
  File ".\arhi_readencoder.py", line 41, in main
    handledSlaveDesc = master.run()
  File "D:\dev\profibus\pyprofibus\pyprofibus\dp_master.py", line 714, in run
    if self.debug:
KeyboardInterrupt
PS D:\dev\profibus\pyprofibus>

it changes when I rotate the shaft and it's different if I select 13bit and 16bit singleturn "module" so .. hopefully that's that ... now to use this numbers somehow and connect step pin with this code, will probbly need to move this to a pi or something else with gpio

I'm not the python person, need to figure out wth is \x97i and \xbdJ and why I have in byte array value like \xb5E

mendenmh

So, if you look up the 'struct' module, I think struct.unpack on those, assuming they are big-endian 4-byte integers will convert them. The funny mixture of backslash codes and regular characters is because some of the return values fall in the printable ascii character set, and get printed normally, which others fall outside and get printed as a hex byte preceded by a backslash.

arhi

@mendenmh thanks, I see it now, it does not print bytearray always as bytes but will output hex only for non-printable chars .. interesting .. anyhow, I'm moving this to RPI or OPI today so that I can add a "step" function to it so I can record a full circle data