Advanced Search

This tells you the following:

1. The component is sending a request to the vfd starting with '[01] [01] ..'
ie it's calling device with address '01' and the function code '01' (ie read coil status) ....

2. In modbus protocol a response starts with echoing the device address ie '01' followed by the functionn code, ie also '01' in your case.

3. Note that the response does not start with [01],[01] but [01], [81]. The '81' tells you that the device has sent you an exception response to your 01 query. The next byte in the response, ie [02], is the exception code (which would indicate that you requested and illegal data address ).
www.simplymodbus.ca/exceptions.htm

Not sure but it seems a bit odd to me to read coil status [01] from address [03] [05] but then have the total number of coils [00] [00]
www.simplymodbus.ca/FC01.htm

 

Have you added

pcie.aspm=0 r8168.eee_enable=0 pcie_aspm=off idle=poll

to the kernel command line? (via grub)
Sometimes that is needed also.

To make sure you are running the dkms driver, try running this script: 

 

To run this, first

chmod +x edriver.txt

and then

./edriver.txt

(from the Downloads directory)

and paste the results here.

(not my script but nicely lists network drivers) 

for i in "/path/to/this/RTAI-git-tree/ksrc/patches/v5.4.279/"*.patch ; do patch -p1 < "${i}" ; done
I verified I had this correct before I sent it in the command line. Just in case I missed something, I'll try it one more time. Do I just have to repeat that one command?

 

do you already have your layout on github ? then i would create a new board in rio so that you have the pins in the right place.
 

Not yet, I still need to confirm the outputs work correctly. Hopefully I have more time to work on it this weekend. When I do I'll generate a pinout diagram, some instructions for ordering and assembly, and upload it. It should be 100% pin compatible with the iceshield, your example iceshield config works perfectly so far. 
 

It's ok thanks.
In meantime i figure it out that information is clearly visible in Halshow window Pins -> classicladder -> 0

Thanks for the help,
I was using
loadusr -Wn -hy_vfd -g
It didn't like that. Had to drop the -Wn as you did.
Now I have debugging info. Please see attachment.
I did re-confirm my settings in the vfd, they are set to comm and 8n1 RTU at 9600. I am also loading hy_vfd at 9600 as well.

Does that response mean it is receiving something but not what it expected, or it expects 8 bytes and got nothing?

can you post the _exact_ command you typed before you got the '>'?

try:

I got through most of the first part but got stuck on "for i in". The new line after would just show ">" and did not know how to get out, so I closed terminal, and now I don't know how to continue from here.

Hello,
plese could you be so kind and help me connect pyvcp scale value which is i think integer number to ClassicLader %IW0 input variable to use as comparison later in classicladder. 

pyvcp code:<scale>
<font>("Helvetica",16)</font>
<width>"25"</width>
<halpin>"my-hscale"</halpin>
<resolution>1</resolution>
<orient>HORIZONTAL</orient>
<initval>1</initval>
<min_>0</min_>
<max_>999</max_>
<param_pin>1</param_pin>
</scale>
in hal ini file:

net input-password  pyvcp.my-hscale classicladder.0.in-('%IW0')???

Thank you   
 

Tried using -g in the loadusr command, told me invalid option for g. So not sure how to get into debug mode.

this seems to work for me:

I do not know how to see any errors from when I try to run it from within Axis. I assume there is the same error.

open a terminal and run:

This will bring up the config picker, pick your machine config and all debug messages will be printed to the terminal window.

Tried using -g in the loadusr command, told me invalid option for g. So not sure how to get into debug mode.
attached is the error I get when I try to use it in halrun per Andy example found somewhere around here. This is the response to:
setp vfd.enable 1

I do not know how to see any errors from when I try to run it from within Axis. I assume there is the same error. 

Thank you for letting us know.

We do have hardware on our suspect list but not likely as restarting LinuxCNC without removing power to the hardware fixes the issue.

Invert the spindle on pin in hal ir in PncConf wizard, there is a check mark to the right of the pin .

i did, but still the same.
i have done ping 10.10.10.10 during the nigh and i have lost some packet.

my hardware is Realtek RTL8111/RTL8168