Advanced Search

Here's an example:

 

It's a bit tricky because you do need to use muxed encoders for all
encoders (because the 7I89 uses physically muxed encoders)

 

Hi All

My intent is to merge some vhd files to get a 7i76e + 7i78 + 7i89 

I saw a post here (from PCW I believe) sayign the count in the 4th column was the number of those modules, so for the stepgens I want (6x or more) I've been putting x06, and same for the encoders (1x spindle + 6x on the DB25 headers), just increasing the built in Qcount. I believe I don't need muxed ones (I have single ended A/B/Z glass scales), finally I then make sure the total number of entries in the whole array was the same as the standard hostmot2 7i76e examples. No ide if this logic is sound or not... 

(HM2DPLLTag,x"00",ClockLowTag, x"01",HM2DPLLBaseRateAddr&PadT,HM2DPLLNumRegs,x"00",HM2DPLLMPBitMask), (WatchDogTag,x"00",ClockLowTag, x"01",WatchDogTimeAddr&PadT, WatchDogNumRegs,x"00",WatchDogMPBitMask),
(IOPortTag,x"00",ClockLowTag, x"03",PortAddr&PadT,IOPortNumRegs,x"00",IOPortMPBitMask),
(QcountTa    x"02",   ClockLowTag,x"06",QcounterAddr&PadT,QCounterNumRegs,x"00",QCounterMPBitMask),  
(StepGenTag,x"02",ClockLowTag, x"06", StepGenRateAddr&PadT,StepGenNumRegs,x"00",StepGenMPBitMask)
(MuxedQcountTag, MQCRev,ClockLowTag, x"01",MuxedQcounterAddr&PadT,MuxedQCounterNumRegs,x"00", MuxedQCounterMPBitMask),
(MuxedQCountSelTag, x"00",ClockLowTag, x"01", NullAddr&PadT,x"00",x"00",x"00000000"),
(SSerialTag,x"00",ClockLowTag,x"01",SSerialCommandAddr&PadT,SSerialNumRegs,x"10",SSerialMPBitMask),  
(LEDTag,x"00",ClockLowTag,x"01",LEDAddr&PadT,LEDNumRegs,x"00",LEDMPBitMask),
(NullTag,x"00",NullTag,x"00",NullAddr&PadT,x"00",x"00",x"00000000"),
(NullTag, x"00", NullTag,x"00",NullAddr&PadT,x"00",    
more null
more null

until I get to the same line number as the examples so same number of modules. 

I think I've made a dud bit file and written it to my 7i76e at some stage, the first time I tried to write it, mesaflash did the erasing, got halfway through the writing "WWWW..." thing and the terminal just hung. Ctrl + C'd the terminal, and I think the 7i76e stopped responding. 
I power cycled the card itself, and now mesaflash can see it and write known good bit files to it, but after I write new bit files and --reload, the --readhmid just returned "None" for all of the channels. 
I've since power cycled a few times and it seems to be writing standard bitfiles again by some miracle.

Can someone explain the header logic or point me to an explanation? 
Can I just keep changing the module count freely and the Xilinx tool will flag if it runs out of space? 
If the Xilinx tool compiles it okay can I be confident it won't brick the board?
How do I know if it's in fallback or normal boot? 
What do the other columns in the header do, do I need to set memory addresses where the modules start or block sizes or anything? I'm wondering if I could be increasing module count and then overflowing the following module or something. 
Does the total number of modules in that array need to be correct / a specific number / does it matter? 

I've skimmed the hostmot2 dataflow vhd file but fallen at the first hurdle: 





This line obviously reads that count but I can't see where NumberOfModules (function? attribute of the an object called "work"?) is defined so I'm lost. As you can tell I don't have a clue how this code works so I'm just a smidge lost  
I've had PCW post a few bitfiles here for me, for which I'm eternally grateful, but I feel bad so I'd prefer to acutally understand what's going on and be able to do it myself (and pass the favour on if it's not potentially harmful to someone elses setup!)

Thanks, 
Kealan

HI
I am wanting to add an optional rotary function to my table, to have a tubing cutter.  With another controller and software I just switched the Y axis control output cable to the rotary axis motor.  This is also the way it is done with my desktop laser to use its rotary optional drive assembly.
On my table I and using LinuxCNC software with a Mesa 7I76E card and QTPlasmaC GUI.  I have tried to leave out the Y home/limit entry in the pncconf setup, but it will not enable the Y axis.  I understand the need to do the homing operation so the software knows where it is for running a G-code.  After the homing I can position any axis to a location and then zero out the DRO and use that as a start position for the G-code. 
What I want is the Y axis not needing to home to be active.  This would allow me to home X and Z and position the Y to a zero position manually.
Thanks for your time
Tom V 

Thanks, sent it again.
-
Max

I don't see that, If you try again, I'll check the spam bucket...

I wrote an email on March 24th and haven't heard back, so I just wanted to follow up in case it got caught by your spam filter.
-
Max

Usable hal pins
amplifier-enable
machine-is-on
e-stop-out
x-enable
something like this
x-enable hm2_7i76e.0.7i76.0.0.output-00
Replace board and pins accordingly.

Pretty sure 2.9.3 should be OK (7I76EU support was added 2 years ago)

Mesaflash >3.5.2

So

7I76EU TB4     DRIVE

1 SPINDLE-      2 MIN
2 SPINOUT       3 IP
3 SPINDLE+     1 +10V
5 ENA-             4 COM
6 ENA+            5 RUN

Note that some or all of these connections may be at line potential
so make sure you do not touch them or allow them to connect to
any low voltage signal.


 

What version of mesaflash and LinuxCNC is needed for the 7i76EU?

Thanks
JT

Just email This email address is being protected from spambots. You need JavaScript enabled to view it. with your address and request
and we can put a couple in an envelope.

Encoder 2 on the 7i85S is used for the spindle and is actually single-ended, but it's still working fine. So I guess I’ve been lucky there, considering the damage on the board.

I’d really appreciate it if I could get two replacement chips, if it’s possible to have them shipped to Germany.
-
Max

That wire is on a 5V regulator pin, so maybe related, hard to tell.

Yes, NCV7608s are obsolete, we do have spares if you need a few.

Thanks, Tommy.
The shop is heated and very dry, especially during the German winter, so moisture is probably not the issue.
-
Max

Picture 2, that looks like arcing across those two parts, moisture can do that, but the rest of the boards look like there is no moisture in quantities to cause that.