Logo
Home Prices

Topic: Remodnc and AWK1127-EU

By: NicoPosted on: Apr 4 2014 at 01:25:09 PM
Hi, Tried to connect with MOXA AWK1127-eu. Can transfer from CNC to REMO, but cant send it bak to cnc. Remo says that its waiting for CNC trigger?
Pse Help

By: SupportPosted on: Apr 4 2014 at 10:04:42 PM
What flow control is enabled in Remo?

Are you connecting to the Com port or to the moxa device's IP address?.


By: NicoPosted on: Apr 5 2014 at 10:12:21 AM
xon xoff in remo, en awk is connected with com port..
CAn send from cnc to remo, but not from remo to AWK

By: GuestPosted on: Apr 5 2014 at 07:40:55 PM
No reason why remo should wait for the cnc unless the cnc has sent a stop command.

You're not using "xonxoff wait" are you?

While remo is displaying the text "waiting for cnc" what happens if you then press the input or read button on the cnc ?

By: NicoPosted on: Apr 6 2014 at 10:59:10 AM
Nothings happens, but allready found something, it had something to do with de AWK1127EU. Like how many user that may control de RS232 port in the moxa. Default is 1, but if i change it to 2 users, ill get data back. And a setting "ignore jammed IP" strange that de Moxa Nport doen't care these settings, and that the AWK1127 from moxa makes a lot of trouble with this..
Allready contacted Moxa about this..waiting for an answer..
Remo still works great!! No and i'm not using XonXoff wait option, just XonXoff. Just like i said, did find out that Remo isn't the problem.

Thanks anyway!!

By: Guest Posted on: Apr 6 2014 at 05:29:36 PM
We tested remo quite a lot using Moxa nPort 2250 EU. (Wireless) and that worked fine. Although we preferred using it as an IP Server rather than the virtual com port.

By: AfterburnerPosted on: Apr 12 2014 at 08:33:09 AM
Ok, But here's the next question. Tied all moxa's to IP settings in remo, com looks fine with send/receive. But dripfeeding doesn't work with this setup. It keeps sending data, til programs is finished. Does not stop if feed dial is on 0%. This does only works with virtual com. Any sugguestions??

By: Support Posted on: Apr 12 2014 at 09:49:59 AM
Afterburner. At the top of this page is a post by Nico saying that he could not send to the CNC. We assumed nico can not send anything at all to the cnc.

Are you Nico? If so then your last comment says that you 'are' able to drip feed to the cnc.

So. Assuming you're different people with different questions.

When you set up the moxa device to use virtual com then you can do all the port settings in the dnc software. The com driver in the computer sends the settings to the moxa device over the network.

But when using the Moxa via its IP address then there is no com driver so all port settings, baud rate flow control etc must be done in advance using the moxa's own setup.

Afterburner, in your case it sounds as if you have not enabled flow control in the moxa.

By: NicoPosted on: Apr 14 2014 at 07:14:27 PM
Yeh sorrie, Afterburner and Nico are the same..
Yes i used flowcontrol, xon xoff. But have to ask, do i have to use a 5 or a 3 wire cable. We have a little trouble with the AWK1127. So make some things clear:
AWK1127 with virtual com driver > can send from CNC to remo but not from remo to CNC. Goes mega slow, and remo waits.

AWK1127 with com settings set in the AWK1127 over TCP/IP works great. sending and receiving, but does not stop if CNC in dripfeed (Tape mode). It sends the whole package at once.

Flow control in de the MOXA on XonXoff.
SO do i need the 5 wire cable, or can it be done with the 3 wire version?

Regards Nico (Afterburner)

By: Guest Posted on: Apr 14 2014 at 08:42:19 PM
XOn/XOff just needs the 3 wire cable. It'll also work with the 5 wire cable but the two rts/cts wires are simply ignored. So, if you have 3 wires then thats ok. But if you have 5 wires then dont go de-soldering any. It's not necessary.

The moxa has a lot of memory. so When drip feeding it is possible for the dnc computer to continue feeding the whole program into the moxa memory even though the moxa has stopped feeding data into the cnc.

What happens? Does the cnc throw an overflow alarm?

Disable fifo in the moxa.

By: NicoPosted on: Apr 15 2014 at 06:24:14 PM
Fifo buffer in moxa allready disabled the first time. By the way with TCP/IP to moxa connection, i'll get at the end of the program a DNC message , something like Unhandled device?? restart remo as soon as possible.. Whats that message. Didn't had that with virtual comport.

By: GuestPosted on: Apr 15 2014 at 07:42:58 PM
You said that the dnc keeps feeding data without stopping. Are you saying that the cnc throws an overflow alarm and stops but the dnc keeps feeding to the end of the program and then displays that message telling you to restart?

Does that happen every time? Are you able to ever finish a job? I mean i assume you're making some parts?

By: NicoPosted on: Apr 15 2014 at 08:55:16 PM
No, the message of an unhandled device, only pops up if i use the TCP/IP to an moxa. First i thought that it was the lengt of the gcode list. I tested it with a big file. But it even gives that message with short files. But never with virtual com driver. And the fault with dripfeeding, is that i do not get any alarm on the cnc, it starts its cycle, and suddenly stops moving.(after a few lines of Gcodes (maybe a tool change) All axis are on hold, but spindle motor keeps running. No message on fanuc. And will wait, until you manualy stop the Fanuc. Tomorrow i'll try it with the old Nport 2150, after that, with a AWK1127.
And keep your advise in mind. Let you know what i've been testing tomorrow.
By the way, should i use TCP/IP to the moxa or the Realcom virtual driver. I think that TCP/IP works better and faster than virtual com.
And i still think that the troublemaker is the AWK1127.
Talk 2 yah later tomorrow.

Regards Nico

By: NicoPosted on: Apr 16 2014 at 08:47:51 PM
Hi, today i tested a few things. Moxa Nport on Fanuc 0-MD works fine with dripfeeding. MOXA AWK tested, with 5 and 3 wire cable. Like you said allready makes no difference. Took the Nport from the Fanuc 0-MD and connected it with the Fanuc 0-M. Whe know that the Nport was working fine with dripfeeding, so should work on de Fanuc 0-M. But this Nport also buffer overuns it. ps alarm 087. Thats strange, looked at the G127.5 being set by the tape switch. Also works fine. Can't find any solution to get it work on de 0-M. Settings of Nport and DNC are the same. We now know that AWK1127 is a client, and does not work with dripfeed, but why doesn't the Nport work on the 0-M. Is there an other setting in the fanuc?? Customer said that it worked with wincom on winXP. This sytem has win7 x64. Regards Nico ps. tested it with xon/xoff and rts/cts. It won't stop. And AWK1127 in real com mode does send data out, but seems to have a problem with receiving data... looked around on the net, but can't find an solution to get it work. Not even with the Nport on de 0-M

Regards Nico

By: NicoPosted on: Apr 16 2014 at 08:51:05 PM
quote: We tested remo quite a lot using Moxa nPort 2250 EU. (Wireless) and that worked fine. Although we preferred using it as an IP Server rather than the virtual com port.)) What operating system did you use??
Ps our setup: PC win7 x64 with REMO > AP/router Draytech > MOXA Nport W2150plus


By: GuestPosted on: May 2 2014 at 01:08:05 PM
still waiting for an answer?

By: SupportPosted on: May 2 2014 at 08:32:42 PM
You're waiting for an answer? I guess "guest" who said he'd tested using moxa 2250 hasn't returned (yet?).

So, unfortunately i dont know what OS he used. Although in our own tests we have no problem using such devices in Win7 or win8 both 32 and 64 bit versions)

By: NicoPosted on: May 14 2014 at 09:50:30 AM
I'm using win7 64 bit too, but it seems that is has some trouble with xon xoff.
Ordered a 2250 for testing. Think have to let the AWK1127 go for now.
Let you know how that turns out!!

By: SupportPosted on: May 14 2014 at 08:58:45 PM
We're getting some feedback from other users that the AWK1127 has some CNC flow control problems. Xon/xoff doesn't seem to work the same way that it does with other devices such as 2250.


Reply to this topic

You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
Security Verification