Advanced Search

timo wrote:

 because I might have damaged a drive or two without beeing aware of the importance of the wiring.

 
A cage-clamp terminal done up nice and tight with the cable not actually inside the clamp is a popular way to blow up a drive. Give the wires a good tug after tightening the clamps.

Kieran wrote:

How's the rigidity of the harmonic drive? 

It seems OK. The HD website quotes values for torsional stiffness, but to be honest I don't know what value would be appropriate for a milling machine, so the numbers aren't useful to me. 

But I frequently use it just as a handy way to mount round stock and have noticed no issues. 
 

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)

 

Does this help at all?
wiki.linuxcnc.org/uploads/orient.svg
It's one potential way to do it.

Probably .hal and .comp which is overflowing

Excuse me for mess in the component but it is in the working session ...

I am sorry

I will enumerate all hard code and

Is has behaviour as I described higher ... I am confused and I have feeling like something in the working session is mixing together but no way to find it out...

Please let me know what I am doing wrong

thanks
regards E..

My experience is limited, but typicaly getting from a scan to a usable model is the hard part. I would ask for a demo with a sample component and be sure it goes all the way to the point that you expet to use the scan.

Thank you that's a good idea, by coincidence i already started making myself familiar with vismach, cause i really don't wanna crash the machine. I try to start as soon as possible an make a crude 3D model of the machine to import it into vismach. But i still need to figure out how to do the virtual Y axis compound move. I think i need to paint a picture of the axis configuration of the machine to post it here. Cause i have a few questions in regards of the axis/joint names.

I spent a few hours yesterday evening in the workshop of a user who has duplicated the Marco Reps controller configuration, with an Rpi5 and Leadshine EL8 (as detailed here: github.com/marcoreps/linuxcnc_leadshine_EL8 ) 

The cia402 component is seeing an enable signal, and the cia-controlword into lcec is setting to 6. But nothing seems to be happening in the drives, and there is no position feedback when turning a motor shaft. 
cia402.opmode is showing zero, and that leads me to think that stat_voltage_enabled is zeroSo possibly no data is being seen from the drives?
command-line ethercat commands list 7 devices (all in pre-op) and the lcec component also lists 7 devices, so _some_ comms is happpening. 

It feels like some sort of drive-enable isn't happening? 

Any thoughts? I felt a bit foolish turning up as an "expert" and then being completely baffled. (first contact with EtherCAT)


 

Forgot the link to the docs
gnipsel.com/linuxcnc/flexgui/controls.html#led-buttons

JT

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

I even added LED's to the reload and save button if you want them you just have to add a Dynamic Property. Big thanks to Chris for helping me understand the LED's

Just edited the nc code file.


Just saved the file so it shows a reload is needed.


So much fun...
JT

The whole thing has evolved over time, and I have failed to update the wiki page. (its been about 13 years...)

I have attached the whole config folder.  But be aware that this machine has many configurations and so has several INI files. 
If you start with the hobbing.ini and look to see which HAL files it uses, you should be able to identify all the used files. 

I think we need to see the code.

The easiest way to find out if your kinematic is gibberish is to try to compile and install it using 'halcompile'. Verifying the kinematic model is of course more difficult and usually requires either a vismach model of the machine or the machine itself.

blazini36 wrote:

Any chance of adding a "save" button for the code viewer? I see the "save_as_pb", I'd rather just overwrite the existing file without a prompt if it's possible.
 

I never thought about that but it makes sense because you can edit the nc file in Flex you should be able to save your edits then reload.

Save menu item and button added.

JT