Advanced Search

Reply redacted.

This is described on page 11 of the 7I96S manual

basically:

RX-/TX- connect to RS-485 "A"
RX+/TX+ connect to RS-485 "B"
W7 right
 

I have a 7i96s rev E that I'm trying to connect to a WJ200 VFD. The VFD  uses a 2-wire RS485 interface with pins labeled SN and SP.

How should I connect this to the 7i96s i/o pins?  What position should W7 be in? 

Thanks,
BR

 

ok i think i found a bug dealing with pocket in the tool table causing some odd behavior. let me dig into it some and see what is happening.

Hi Andy,

Sorry for the confusion.

Python files in /linuxcnc/lib/ may not be processed by the "make" command.

Python files in /linuxcnc/src/ may be processed by the "make" command.

I've tested it now.
You were right.

Hi,
I am wondering if there may be someone experienced with linuxCNC and MESA board based controllers from Warsaw (Poland) (or near Warsaw).

Cris.

Thank you Tommylight, I gave up on my previous efforts and installed Mint as you suggested. Upgrading now. Hope this one is less hairy than my last attempt.
Will let you know when it's up and running.

It is cheaper to get the real ones from Mesa.

It's standard linuxcnc homing from here on
linuxcnc.org/docs/html/config/ini-homing.html

From what I can see, the lcec EL1014 driver expects PDOs at 0x6000, 0x6010, 0x6020 and 0x6030. Two of your units have that.
Three of your units have PDOs at 0x3101:1, 0x3101:2, 0x3101:3 and 0x3101:4.
Maybe there is a reason for that? Different versions? I don't know the products very well.

You can use the generic driver for the 0x3101 units.  And for the other units as well.
Run "lcec_configgen -typedb=false" and hopefully you should get the "generic" driver for all devices in the output.
 

ah are you using the tool setter page to set the spindle zero with the probe spindle zero button?

where is your z home position set?

Sherline lathe running LinuxCNC  2.9.4
Trying to get G71 to work. Seems like some code if not right. Wont read U,W,  commands.
When eliminating one another one shows up that it wont read. 
Seems like someone has already fixed or worked it out.
Please help,
Thank 
Skipper

This indicates a loss of communication , most commonly this is a real time issue
with the network connection.

Typical fixes for network real time issues:

If you host computer uses a RealTek Ethernet chip, it's likely you need to install the DKMS 8168 driver.

If you have a Intel Ethernet chip, disabling IRQ coalescing helps (see hm2_eth manual page)

To tesl network latency, run this command:

sudo chrt 99 ping -i .001 -q -c 60000 [card_ip_address]

This will run for 1 minute and print timing statistics.

Where [card_ip_address] is the 7I96s card ip address (192.168.1.121 or 10.10.10.10)

I do not mess with working configs. Currently testing on a VM. I'm trying to solve a problem with the old interface locking up after probing.
Your comment is supremely unhelpful. If I was someone who had just broken a working install and I was desperate to get it working again, maybe making them feel dumb is the wrong approach.
Not sure what version of probe basic the old one is but I am testing on the latest available installed via apt based on the documentation.