NE500 symbolic link question

Support
1

Hi Chris,

When using the NE500 on an 0.6.dev nightly of MWorks, we have had success passing a symbolic link as the serial device path.
e.g.
<iodevice type=“ne500” tag=“ne500” address=‘“/usr/local/dev/cu-NE500-0”’ response_timeout=“300ms”
where

$ ls -la cu-NE500-0
lrwxr-xr-x 1 histedmh admin 26 Aug 10 12:51 cu-NE500-0 → /dev/cu.usbserial-AI02FUQP

I’m now testing on a recent MWorks nightly: 0.8.dev-20170810. It looks like I can pass the serial device name in /dev directly, but the symbolic link has stopped working. Were there any changes that might have caused this?

Thanks,
Mark

2

Hi Mark,

When using the NE500 on an 0.6.dev nightly of MWorks, we have had success passing a symbolic link as the serial device path.

Do you mean a 0.7.dev nightly? The NE500 interface didn’t support USB-to-serial adapters until 0.7.

I’m now testing on a recent MWorks nightly: 0.8.dev-20170810. It looks like I can pass the serial device name in /dev directly, but the symbolic link has stopped working.

I see why the symbolic link is failing. The fix will be in tonight’s nightly build.

Chris