New Trajectory Planner - Testers/programs wanted

Tonight I tried to install the new Trajectory planner, to test it on another machine, and I'm getting stuck folowing the the instructions at the top of this.

After commanding ./configure --enable-run-in-place
I get:
checking for libmodbus3... no
configure: error: libmodbus3 not found!
install with "sudo apt-get install libmodbus-dev" or disable with
"configure --without-libmodbus"

When I try sudo apt-get install libmodbus-dev
I get
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package libmodbus-dev

This particular machine I want to test with needs modbus to function, and is currently running master from buildbot in order to get mb2hal.

Where am I going wrong?

You must be using 10.04?
There is a deb here for it I think:
linuxcnc.org/dists/lucid/base/binary-i386/

hard to find!

Chris M

Yes, I'm using 10.04.
Are there any instal instructions for the less than gifted at using Linux? (much much less in my case)

Todd Zuercher wrote: Yes, I'm using 10.04.

Todd - I'm running 10.04 and do not remember getting that error. I do have libmodbus5 and libmodbus-dev installed, though. I don't know if you want to try those or not.

HTH
Paul

The other machine I tested on was a plain 2.5 from cd install, and I didn't have that problem either. This machine has been running from an original EMC2 2.4 install, that has been upgraded a few times to eventually be a master (from buildbot) install to use the generic modbus driver mb2hal. (that was about 6months ago).
Clicking on the link from CMorly (thanks) took care of the libmodbus-dev dependancy problem.

My first tests, with g64p0.005 were actually slower with the new TP than the old on the file I was using. Adding q0.005 only shaved 3 min off a 25min runtime and without it it was that much slower. Tomorrow I still need to retest it with the old TP and the same g64 settings, to try and get a better apples to oranges comparison.
I haven't ruled out the possibility I didn't install something correctly.

what kind of gcode? If there are a lot of non-tangent arc-line or arc-arc segments - it will run pretty closed to the current TP. Those type of segment transistions are not handled yet and fall back to the current parabolic - 1 segment look ahead.

sam

Todd Zuercher wrote: The other machine I tested on was a plain 2.5 from cd install, and I didn't have that problem either. This machine has been running from an original EMC2 2.4 install, that has been upgraded a few times to eventually be a master (from buildbot) install to use the generic modbus driver mb2hal. (that was about 6months ago).
Clicking on the link from CMorly (thanks) took care of the libmodbus-dev dependancy problem.

My first tests, with g64p0.005 were actually slower with the new TP than the old on the file I was using. Adding q0.005 only shaved 3 min off a 25min runtime and without it it was that much slower. Tomorrow I still need to retest it with the old TP and the same g64 settings, to try and get a better apples to oranges comparison.
I haven't ruled out the possibility I didn't install something correctly.