Rearranging pin assignment on mesa 5i25
- sirop
- Topic Author
- Offline
- Elite Member
Less
More
- Posts: 193
- Thank you received: 56
28 Oct 2015 19:13 #64392
by sirop
Replied by sirop on topic Rearranging pin assignment on mesa 5i25
I posted my VHD file to gist:
gist.github.com/sirop/dd4a8b7c3f7af1953913
You probably mean this line:
According to tom-itx.no-ip.biz:81/~webpage/emc/xilinx...14_install_index.php these members are:
'TAG, VERSION, CLOCK, INSTANCES, BASE ADDRESS, NUMBER OF REGISTERS, STRIDES, MPBITMASK'
As I understand, I have only one Encoder instance.
Yes, we'll probably have only one Encoder as we'll have additionally a magnetic position sensor connected into MESA card through SSI.
gist.github.com/sirop/dd4a8b7c3f7af1953913
You probably mean this line:
....
(QcountTag, x"02", ClockLowTag, x"01", QcounterAddr&PadT, QCounterNumRegs, x"00", QCounterMPBitMask),
....
According to tom-itx.no-ip.biz:81/~webpage/emc/xilinx...14_install_index.php these members are:
'TAG, VERSION, CLOCK, INSTANCES, BASE ADDRESS, NUMBER OF REGISTERS, STRIDES, MPBITMASK'
As I understand, I have only one Encoder instance.
Yes, we'll probably have only one Encoder as we'll have additionally a magnetic position sensor connected into MESA card through SSI.
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17904
- Thank you received: 4774
28 Oct 2015 19:24 #64394
by PCW
Replied by PCW on topic Rearranging pin assignment on mesa 5i25
Yes sorry I misread the ID information the first time
So this may in fact be a hostmot2 driver bug since I dont think there
has ever been a configuration with just one encoder module
As I said adding a second encoder on the P2 I/O connector is harmless
if the pins are just used as GPIO.
I will see if i can duplicate this bug with a 1 encoder setup and if its a real bug, get it fixed
So this may in fact be a hostmot2 driver bug since I dont think there
has ever been a configuration with just one encoder module
As I said adding a second encoder on the P2 I/O connector is harmless
if the pins are just used as GPIO.
I will see if i can duplicate this bug with a 1 encoder setup and if its a real bug, get it fixed
The following user(s) said Thank You: sirop
Please Log in or Create an account to join the conversation.
- sirop
- Topic Author
- Offline
- Elite Member
Less
More
- Posts: 193
- Thank you received: 56
29 Oct 2015 19:30 #64445
by sirop
Replied by sirop on topic Rearranging pin assignment on mesa 5i25
I followed your advice and added a second encoder as you said that only one encoder is too unusual.
But I still see two position pins -- now for each of the two encoders.
Output from mesaflash --device 5i25 --readhmid > myconfig.txt : gist.github.com/sirop/5dc11f91d109bb96d897
My new pinout VHD file: gist.github.com/sirop/2ff83efb44e513be7dbb
But I still see two position pins -- now for each of the two encoders.
Output from mesaflash --device 5i25 --readhmid > myconfig.txt : gist.github.com/sirop/5dc11f91d109bb96d897
My new pinout VHD file: gist.github.com/sirop/2ff83efb44e513be7dbb
halcmd: show pin
Component Pins:
Comp Inst Type Dir Value Name Epsilon Flags
74 s32 OUT 0 hm2_5i25.0.encoder.00.count 0
74 s32 OUT 0 hm2_5i25.0.encoder.00.count-la 0
74 bit I/O FALSE hm2_5i25.0.encoder.00.index-en 0
74 bit OUT TRUE hm2_5i25.0.encoder.00.input-a 0
74 bit OUT TRUE hm2_5i25.0.encoder.00.input-b 0
74 bit OUT FALSE hm2_5i25.0.encoder.00.input-in 0
74 bit IN FALSE hm2_5i25.0.encoder.00.latch-en 0
74 bit IN FALSE hm2_5i25.0.encoder.00.latch-po 0
74 float OUT 0 hm2_5i25.0.encoder.00.position 0.000010 0
74 float OUT 0 hm2_5i25.0.encoder.00.position 0.000010 0
74 bit OUT FALSE hm2_5i25.0.encoder.00.quad-err 0
74 bit IN FALSE hm2_5i25.0.encoder.00.quad-err 0
74 s32 OUT 0 hm2_5i25.0.encoder.00.rawcount 0
74 s32 OUT 0 hm2_5i25.0.encoder.00.rawlatch 0
74 bit IN FALSE hm2_5i25.0.encoder.00.reset 0
74 float OUT 0 hm2_5i25.0.encoder.00.velocity 0.000010 0
74 s32 OUT 0 hm2_5i25.0.encoder.01.count 0
74 s32 OUT 0 hm2_5i25.0.encoder.01.count-la 0
74 bit I/O FALSE hm2_5i25.0.encoder.01.index-en 0
74 bit OUT FALSE hm2_5i25.0.encoder.01.input-a 0
74 bit OUT FALSE hm2_5i25.0.encoder.01.input-b 0
74 bit OUT TRUE hm2_5i25.0.encoder.01.input-in 0
74 bit IN FALSE hm2_5i25.0.encoder.01.latch-en 0
74 bit IN FALSE hm2_5i25.0.encoder.01.latch-po 0
74 float OUT 0 hm2_5i25.0.encoder.01.position 0.000010 0
74 float OUT 0 hm2_5i25.0.encoder.01.position 0.000010 0
74 bit OUT FALSE hm2_5i25.0.encoder.01.quad-err 0
.......
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17904
- Thank you received: 4774
29 Oct 2015 21:18 - 29 Oct 2015 21:24 #64453
by PCW
Replied by PCW on topic Rearranging pin assignment on mesa 5i25
Look carefully (I didn't at first), you will see that the names
are truncated, the first pin is:
hm2_5i25.0.encoder.00.position
but the second is
hm2_5i25.0.encoder.00.position-latched
Why your output is truncated I dont know, heres what I got with
halcmd show pin | grep encoder.00.position
25 float OUT 0 hm2_7i76e.0.encoder.00.position
25 float OUT 0 hm2_7i76e.0.encoder.00.position-latched
are truncated, the first pin is:
hm2_5i25.0.encoder.00.position
but the second is
hm2_5i25.0.encoder.00.position-latched
Why your output is truncated I dont know, heres what I got with
halcmd show pin | grep encoder.00.position
25 float OUT 0 hm2_7i76e.0.encoder.00.position
25 float OUT 0 hm2_7i76e.0.encoder.00.position-latched
Last edit: 29 Oct 2015 21:24 by PCW.
The following user(s) said Thank You: sirop
Please Log in or Create an account to join the conversation.
- sirop
- Topic Author
- Offline
- Elite Member
Less
More
- Posts: 193
- Thank you received: 56
29 Oct 2015 21:26 #64454
by sirop
Replied by sirop on topic Rearranging pin assignment on mesa 5i25
Yes, you are right.
Got it also with line completion:
Got it also with line completion:
halcmd: getp hm2_5i25.0.encoder.01.position
hm2_5i25.0.encoder.01.position hm2_5i25.0.encoder.01.position-latched
Please Log in or Create an account to join the conversation.
Moderators: PCW, jmelson
Time to create page: 0.132 seconds