Compiling Altivar VFD Modbus comp

More
11 years 7 months ago #57182 by Swapper
The port sniffing i have tried, maight not have been exactly like that but i tried with mb2hal and got data in the "sniffer"
When i run the altivar comp i get nothing, its not touching the serialport at all.
i have ran it with -v no difference.

The VFD does have modbus activated since i can read registers with mb2hal component.
That in my world means that serial coms and settings to read the VFD is correct.

Since the VFD comp is changed and compiled against newer linuxcnc software my guess is that something in the modbus lib is wrong and its not able to communicate correctly.

Please Log in to join the conversation.

More
11 years 7 months ago #57201 by fupeama

Swapper wrote: The port sniffing i have tried, maight not have been exactly like that but i tried with mb2hal and got data in the "sniffer"
When i run the altivar comp i get nothing, its not touching the serialport at all.
i have ran it with -v no difference.

The VFD does have modbus activated since i can read registers with mb2hal component.
That in my world means that serial coms and settings to read the VFD is correct.

Since the VFD comp is changed and compiled against newer linuxcnc software my guess is that something in the modbus lib is wrong and its not able to communicate correctly.


Can you describe sniff method?
I compiled altivar comp on 2.7.0 pre not on 2.8. But I can try it.

Please Log in to join the conversation.

More
11 years 7 months ago #57204 by Swapper
Hi
i tried the sniffer you provided

socat -d -d PTY: PTY

halrun:
loadusr -W atv_vfd -g -r 19200 -s 1 -t 1 -v -d /dev/pts/5

setp atv_vfd.spindle-on 1

cat /dev/pts/6

No results at all from cat

if you can try the same on 2.8 it would be very appreciated!

Please Log in to join the conversation.

More
11 years 7 months ago #57205 by andypugh
You _must_ set atv_vfd.enable to 1 otherwise nothing at all happens.

here is the source-code
Code:
594 // wait for enable signal after load axis 595 while (!*(haldata->enable)) { 596 // do nothing 597 sleep(1); // be nice to CPU -mah 598 }

Please Log in to join the conversation.

More
11 years 7 months ago #57221 by Swapper
Hi
Oh now where getting some errors at least :)


halcmd: setp atv_vfd.enable 1
halcmd: read_data: reading setup parameters:


ERROR invalid crc received 208 - crc_calc 5846

main: read_data retval=-16


ERROR Communication time out

main: write_data retval=-16
read_data: reading setup parameters:


ERROR Communication time out

main: read_data retval=-12


ERROR Communication time out

main: write_data retval=-12
read_data: reading setup parameters:

Please Log in to join the conversation.

More
11 years 7 months ago #57325 by Swapper
i gave in and hooked the VFD up with analog control, maybe someone will get it running in the future.

Please Log in to join the conversation.

More
1 year 8 months ago #321970 by nawaf
Controling  Altivar VFD ATV 310. I am using the driver provided by @dgarrett with slight modification.
Code:
$ source ~/linuxcnc-dev/scripts/rip-environment $ cd ~/atv_vfd $ make clean $ make$ make atv_vfd $ make install

and  its works

Don't forget to set the parameters in ATV 310
  • 401 : Reference Channel 1 = 164 (for modbus)
  • 406 : Channel Configuration = 02 (for separate mode)
  • 407 : Command Channel 1 = 10 (for modbus)
  • 701 : Modbus Address = 01
  • 302 : Rated Motor Power = Nominal motor power given on the nameplate, in kW
  • 304 : Rated Motor Voltage = Nominal motor voltage is given on the nameplate, in V.
  • 305 : Rated Motor Current = Nominal motor current is given on the nameplate, in A.
  • 306 : Rated Motor Frequency = Nominal motor frequency is given on the nameplate, in Hz.
  • 307 : Rated Motor Speed = Nominal motor speed is given on the nameplate, in RPM.

Please Log in to join the conversation.

Time to create page: 0.237 seconds
Powered by Kunena Forum