Help in understanding Hal -d setting to VFD

andypugh wrote: This almost looks like the module has forgotten how to handle the "device=" parameter

(It acts puzzled, and then falls-back to the default)

The "unhandled argument" is not due to permissions, that would be a different error.

What is the exact loadusr line for the component?

loadusr -W wj200_vfd device="/dev/ttyUSB0"

I assume thats what you were asking for. Thats the exact line I use in hal to attempt loading the driver to the device.

Would there be another way to link ttyS0 to ttyUSB0 within linux itself? If it could be done on that end wouldnt the driver not care about what the loadusr line says? If there is a way I hope its easy LMAO!

Also know I am using Master 2.8

Just another thought to add to the confusion.

After I use sudo chmod 666 /dev/ttyS0 in terminal for linux I start linuxcnc and it opens without errors. I just wanted to make sure you knew that because its odd that an error came up before I did this despite the error complaining about /dev/tttyUSB0 ...

If I reboot I can recreate the error by simply chmoding the USB0 and not the ttyS0

Yes, but, does it actually work?

It sounds like it is connecting to ttyS0 and that won't raise any errors, but probably is not going to work.

It is possible that the device has been re-assigned to a different ttyUSB. (Though that, too, would cause a different error).

This might help:
unix.stackexchange.com/questions/66901/h...-under-a-static-name

andypugh wrote: Yes, but, does it actually work?

It sounds like it is connecting to ttyS0 and that won't raise any errors, but probably is not going to work.

It is possible that the device has been re-assigned to a different ttyUSB. (Though that, too, would cause a different error).

This might help:
unix.stackexchange.com/questions/66901/h...-under-a-static-name

Thanks for the link I will try this next. But to answer your question, no it does not work. Also just to do a sanity check I opened terminal and used ls /dev to verify that the rs485 was still designated as ttyUSB0 and it has not changed.

So..... it appears that the driver is loading ttyS0 thus why nothing is working. I will take a crack at the link you gave me to see if I can pull something off there. If I do and it works I will post here again. If not, I hardwired the baby into the 7i76. So if I attempt that expect different questions from me LMAO!!!

if "device=" worked before then I am puzzled why it stopped working.

One possibility is that something (like a windows editor) has introduced invisible wierd characters into the loadusr line.

Just an update on where things stand so at some point someone here who has this hardware can see the trail I left.

I followed the above link to go into linux and then create a symlink within linux itself, not linuxcnc. The path for the file would be /ect/udev/rules.d/filenamehere. Within that created file I made the following line creates the symlink for my usb on my machine:

KERNELS=="1-3", SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="ttyS0", MODE="0660"

I verified this symlink code would work by creating a test usb port which it would create with no issues. I then used the above line to link /dev/ttyUSB0 to /dev/ttyS0 .

I rebooted everything and then fired up linuxcnc. Once the software started I then went to start the spindle and nothing happened. For some reason this still is not working.

Aside from the settings within the vfd I even went as far as using stty -F /dev/ttyUSB0 9600 and then also editing my hal file loadusr line to accept the device="/dev/ttyUSB0" in hopes that it was simply a failure in communication there but still no start on the spindle.

I will begin to prepare to wire this thing in through TB4 on the 7i76. I have about exhausted the limits of my abilities on this one. If anyone out there is using the Hitachi WJ200 with a rs485 feel free to give a shout to me so I can see what you have done.

Thanks for all the help Andy, it was worth the go. I may revisit this later. If I do and find any success I will let you guys know.