Compiling Altivar VFD Modbus comp

Swapper
Offline
Junior Member

25 Mar 2015 22:35 #57182 by Swapper

Replied by Swapper on topic Compiling Altivar VFD Modbus comp

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 or Create an account to join the conversation.

fupeama
Offline
Senior Member

26 Mar 2015 16:12 #57201 by fupeama

Replied by fupeama on topic Compiling Altivar VFD Modbus comp

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 or Create an account to join the conversation.

Swapper
Offline
Junior Member

26 Mar 2015 18:57 #57204 by Swapper

Replied by Swapper on topic Compiling Altivar VFD Modbus comp

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 or Create an account to join the conversation.

andypugh
Offline
Moderator

26 Mar 2015 19:03 #57205 by andypugh

Replied by andypugh on topic Compiling Altivar VFD Modbus comp

You _must_ set atv_vfd.enable to 1 otherwise nothing at all happens.

here is the source-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 or Create an account to join the conversation.

Swapper
Offline
Junior Member

27 Mar 2015 04:11 #57221 by Swapper

Replied by Swapper on topic Compiling Altivar VFD Modbus comp

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 or Create an account to join the conversation.

Swapper
Offline
Junior Member

31 Mar 2015 04:24 #57325 by Swapper

Replied by Swapper on topic Compiling Altivar VFD Modbus comp

i gave in and hooked the VFD up with analog control, maybe someone will get it running in the future.

Please Log in or Create an account to join the conversation.

nawaf
Offline
New Member

19 Feb 2025 09:49 - 20 Feb 2025 05:08 #321970 by nawaf

Replied by nawaf on topic Compiling Altivar VFD Modbus comp

Controling Altivar VFD ATV 310. I am using the driver provided by @dgarrett with slight modification.

$ 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.

Last edit: 20 Feb 2025 05:08 by nawaf.

Please Log in or Create an account to join the conversation.

Time to create page: 0.074 seconds

Compiling Altivar VFD Modbus comp

Attachments: