It's a DE9. DB is the 25 pin size used for the large serial port, parallel
ports, and old Macintosh SCSI.
A is 15 pin, used mainly for PC gameports and old Macintosh monitors. C is 37
pin, most commonly used for old PC external floppy drives. D is a three row 50
pin connector, uncommonly used
OK, I tried putty with 2 & 3 tied together and it loops back and shows
keystrokes while tied. So the NUC's RS232 port IS functional.
I found an FTDI USB RS232 but it ends in female pins, I need male.
Found a knockoff PL2303 USB-to-DB9 cable, I hope it's RS232 level, it
does end in a DB9. No
On Sun, 10 Apr 2022 at 18:29, Danny Miller wrote:
>
> Nothing to unplug- it's a built-in RS232 DB9. Nothing enumerates across it.
https://superuser.com/questions/131044/how-do-i-know-which-dev-ttys-is-my-serial-port
suggests "cat /proc/tty/driver/serial" will tell you which ttyS* has
hardware
tin.rr.com]
Sent: Sunday, April 10, 2022 10:27 AM
To: emc-users@lists.sourceforge.net
Subject: Re: [Emc-users] Can't compile MODBUS VFD in 2.8.2
CAUTION: This email originated from outside the Walla Walla University email
system.
Nothing to unplug- it's a built-in RS232 DB9. Nothing enumera
Nothing to unplug- it's a built-in RS232 DB9. Nothing enumerates across it.
I'm baffled where to go. I see there's a port /ttyS0 from the command line.
Launching LinuxCNC from the command line shows text warnings about
Modbus timing out. It's just not communicating. I played with the
On Sat, 9 Apr 2022 at 16:44, Danny Miller wrote:
> I tried specifying the port loadusr x200 device="/dev/ttyS0". I'm not
> sure how my serial ports are named. Would "/dev/ttyUSB0" be if that was
> an FTDI USB to serial device?
Plug and unplug it, see what appears and disappears in /dev/
--
Ah, found it:
https://forum.linuxcnc.org/25-classicladder/33130-hitachi-wj200-setup
That worked, cut and pasted the gcc lines.
LinuxCNC boots and loads it. But no modbus communication with VFD.
I've been using a Dell with a built-in RS232 successfully before.
This is on a new fanless NUC
On Friday, 8 April 2022 14:26:21 EDT Danny Miller wrote:
> I used "sudo apt-get install" and libmodbus5 was already there.
>
> halcompile --install x200_vfd.comp does:
>
> gcc -I/usr/include -I/usr/include/linuxcnc -URTAPI -U__MODULE__ -DULPAI
> -Os -o x200_vfd /tmp/tmp4bdQIY/x200_vfd.c
I used "sudo apt-get install" and libmodbus5 was already there.
halcompile --install x200_vfd.comp does:
gcc -I/usr/include -I/usr/include/linuxcnc -URTAPI -U__MODULE__ -DULPAI
-Os -o x200_vfd /tmp/tmp4bdQIY/x200_vfd.c -Wl,-rpath,/lib -L/lib
-llinxcnchal
Then, no error about missing typedef
On Fri, 8 Apr 2022 at 18:08, Danny Miller wrote:
> That directory just has the header file, it looks like the error is that
> it can't actually find the compiled definitions of the functions called
> out in the header.
It seems that libmodbus-dev is just the headers (and manpages)
On Friday, 8 April 2022 13:06:57 EDT Danny Miller wrote:
> So, I think libmodbus-dev is correct, the typedef and function names
> match.
>
> I installed it, now the file in /usr/include/modbus/modbus.h should
> work, and it looks like halcompile definitely uses it when given an
> explicit path,
So, I think libmodbus-dev is correct, the typedef and function names match.
I installed it, now the file in /usr/include/modbus/modbus.h should
work, and it looks like halcompile definitely uses it when given an
explicit path, since the error message changes.
That directory just has the
On Friday, 8 April 2022 03:57:45 EDT andy pugh wrote:
> On Fri, 8 Apr 2022 at 03:04, Danny Miller wrote:
> > I specified that. Now it doesn't fail on a missing type modbus_t,
> > but
> > rather "undefined reference" to any modbus_write_bit etc functions.
> > So even though I did get that
On Fri, 8 Apr 2022 at 03:04, Danny Miller wrote:
> I specified that. Now it doesn't fail on a missing type modbus_t, but
> rather "undefined reference" to any modbus_write_bit etc functions. So
> even though I did get that install for libmodbus to work, it just has
> the header file. It's not
Thanks Andy! Closer... it's in /usr/include/modbus/
I specified that. Now it doesn't fail on a missing type modbus_t, but
rather "undefined reference" to any modbus_write_bit etc functions. So
even though I did get that install for libmodbus to work, it just has
the header file. It's not
On Thu, 7 Apr 2022 at 03:27, Danny Miller wrote:
> And same prob. It's looking for stuff in the libmodbus's modbus.h but
> it's not seeing it somehow.
You could try giving it a complete path:
#include "/usr/share/modbus/modbus.h"
(quotes rather than braces, I think, for an explicit path)
Nevermind, fixed the "update" part and libmodbus installed.
Went back and tried sudo halcompile --install x200_vfd.comp
And same prob. It's looking for stuff in the libmodbus's modbus.h but
it's not seeing it somehow.
Danny
On 4/6/2022 7:31 PM, Danny Miller wrote:
OK I get:
Err:1
OK I get:
Err:1 http://deb.debian.org/debian buster/main amd64 libmodbus-dev amd64
3.1.4-2 404 Not Found [IP: 151.101.50.132 80]
E: Failed to fetch
http://deb.debian.org/debian/pool/main/libm/libmodbus/libmodbus-dev_3.1.3-2_amd64.deb
404 Not Found [IP: 151.101.50.132 80]
E: Unable to
On Wed, 6 Apr 2022 at 03:09, Danny Miller wrote:
> https://github.com/stephane/libmodbus IS the correct one.
wj_200_vfd.comp is a "comp" file, which means that it should compile
and install with just "sudo halcompile --install filename.comp"
it contains "#include " which will be looking in
I'm doing a long-awaited upgrade from 2.7 RT-Preempt to 2.8.2 Debian.
I have an X200 VFD. It is only superficially different than the
WJ200_VFD included. Like 2 coil numbers change. I modified it and
compiled and included it in my Linux 2.7 installation- I stumbled all
there there, but
20 matches
Mail list logo
