Visit our Popular Forums

stevead · 18-06-2023, 03:52

Rename libtwocan_plugin_pi.dylib.jail to libtwocan_plugin_pi.dylib and run the otool command again.

Bella Donna · 18-06-2023, 08:16

doug@Dougs-MacBook-Air ~ % otool -l /Users/doug/Library/Application\ Support/OpenCPN/Contents/PlugIns/libtwocan_plugin_pi.dylib
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
doug@Dougs-MacBook-Air ~ %

stevead · 18-06-2023, 09:31

It seems like you need to install the developer tools.
The command to install the tools is

Code:

xcode-select --install

I can understand if you don't wish to pursue this any further..

I have a suspicion that the problem is due to new or different security permissiond in OSX Ventura.

Bella Donna · 18-06-2023, 10:14

doug@Dougs-MacBook-Air ~ % otool -l /Users/doug/Library/Application\ Support/OpenCPN/Contents/PlugIns/libtwocan_plugin_pi.dylib
/Users/doug/Library/Application Support/OpenCPN/Contents/PlugIns/libtwocan_plugin_pi.dylib:
Load command 0
cmd LC_SEGMENT_64
cmdsize 632
segname __TEXT
vmaddr 0x0000000000000000
vmsize 0x00000000000fc000
fileoff 0
filesize 1032192
maxprot 0x00000005
initprot 0x00000005
nsects 7
flags 0x0
Section
sectname __text
segname __TEXT
addr 0x0000000000003f70
size 0x00000000000d492f
offset 16240
align 2^4 (16)
reloff 0
nreloc 0
flags 0x80000400
reserved1 0
reserved2 0
Section
sectname __stubs
segname __TEXT
addr 0x00000000000d88a0
size 0x00000000000009b4
offset 886944
align 2^1 (2)
reloff 0
nreloc 0
flags 0x80000408
reserved1 0 (index into indirect symbol table)
reserved2 6 (size of stubs)
Section
sectname __stub_helper
segname __TEXT
addr 0x00000000000d9254
size 0x0000000000001016
offset 889428
align 2^2 (4)
reloff 0
nreloc 0
flags 0x80000400
reserved1 0
reserved2 0
Section
sectname __gcc_except_tab
segname __TEXT
addr 0x00000000000da26c
size 0x000000000000d90c
offset 893548
align 2^2 (4)
reloff 0
nreloc 0
flags 0x00000000
reserved1 0
reserved2 0
Section
sectname __const
segname __TEXT
addr 0x00000000000e7b80
size 0x000000000000fd14
offset 949120
align 2^4 (16)
reloff 0
nreloc 0
flags 0x00000000
reserved1 0
reserved2 0
Section
sectname __cstring
segname __TEXT
addr 0x00000000000f7894
size 0x000000000000230a
offset 1013908
align 2^0 (1)
reloff 0
nreloc 0
flags 0x00000002
reserved1 0
reserved2 0
Section
sectname __unwind_info
segname __TEXT
addr 0x00000000000f9ba0
size 0x000000000000245c
offset 1022880
align 2^2 (4)
reloff 0
nreloc 0
flags 0x00000000
reserved1 0
reserved2 0
Load command 1
cmd LC_SEGMENT_64
cmdsize 712
segname __DATA
vmaddr 0x00000000000fc000
vmsize 0x0000000000014000
fileoff 1032192
filesize 32768
maxprot 0x00000003
initprot 0x00000003
nsects 8
flags 0x0
Section
sectname __nl_symbol_ptr
segname __DATA
addr 0x00000000000fc000
size 0x0000000000000008
offset 1032192
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000006
reserved1 414 (index into indirect symbol table)
reserved2 0
Section
sectname __got
segname __DATA
addr 0x00000000000fc008
size 0x0000000000000418
offset 1032200
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000006
reserved1 415 (index into indirect symbol table)
reserved2 0
Section
sectname __la_symbol_ptr
segname __DATA
addr 0x00000000000fc420
size 0x0000000000000cf0
offset 1033248
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000007
reserved1 546 (index into indirect symbol table)
reserved2 0
Section
sectname __mod_init_func
segname __DATA
addr 0x00000000000fd110
size 0x0000000000000020
offset 1036560
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000009
reserved1 0
reserved2 0
Section
sectname __const
segname __DATA
addr 0x00000000000fd130
size 0x0000000000004a88
offset 1036592
align 2^4 (16)
reloff 0
nreloc 0
flags 0x00000000
reserved1 0
reserved2 0
Section
sectname __cfstring
segname __DATA
addr 0x0000000000101bb8
size 0x00000000000000c0
offset 1055672
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000000
reserved1 0
reserved2 0
Section
sectname __bss
segname __DATA
addr 0x0000000000101c78
size 0x00000000000001a0
offset 0
align 2^3 (8)
reloff 0
nreloc 0
flags 0x00000001
reserved1 0
reserved2 0
Section
sectname __common
segname __DATA
addr 0x0000000000101e20
size 0x000000000000a6f8
offset 0
align 2^4 (16)
reloff 0
nreloc 0
flags 0x00000001
reserved1 0
reserved2 0
Load command 2
cmd LC_SEGMENT_64
cmdsize 72
segname __LINKEDIT
vmaddr 0x0000000000110000
vmsize 0x000000000002e0e8
fileoff 1064960
filesize 188648
maxprot 0x00000001
initprot 0x00000001
nsects 0
flags 0x0
Load command 3
cmd LC_ID_DYLIB
cmdsize 64
name @rpath/libtwocan_plugin_pi.dylib (offset 24)
time stamp 1653602119 Thu May 26 14:55:19 2022
current version 0.0.0
compatibility version 0.0.0
Load command 4
cmd LC_DYLD_INFO_ONLY
cmdsize 48
rebase_off 1064960
rebase_size 808
bind_off 1065768
bind_size 22320
weak_bind_off 1088088
weak_bind_size 5704
lazy_bind_off 1093792
lazy_bind_size 16512
export_off 1110304
export_size 35152
Load command 5
cmd LC_SYMTAB
cmdsize 24
symoff 1147696
nsyms 2031
stroff 1184032
strsize 69576
Load command 6
cmd LC_DYSYMTAB
cmdsize 80
ilocalsym 0
nlocalsym 1
iextdefsym 1
nextdefsym 1209
iundefsym 1210
nundefsym 821
tocoff 0
ntoc 0
modtaboff 0
nmodtab 0
extrefsymoff 0
nextrefsyms 0
indirectsymoff 1180192
nindirectsyms 960
extreloff 0
nextrel 0
locreloff 0
nlocrel 0
Load command 7
cmd LC_UUID
cmdsize 24
uuid 13C15BA7-95B8-3074-9D8F-254B58BF4E76
Load command 8
cmd LC_VERSION_MIN_MACOSX
cmdsize 16
version 10.10
sdk 11.3
Load command 9
cmd LC_SOURCE_VERSION
cmdsize 16
version 0.0
Load command 10
cmd LC_LOAD_DYLIB
cmdsize 56
name @rpath/libTouCAN.0.2.3.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 0.2.3
compatibility version 0.2.0
Load command 11
cmd LC_LOAD_DYLIB
cmdsize 56
name libKvaserCAN.0.2.1.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 0.2.1
compatibility version 0.2.0
Load command 12
cmd LC_LOAD_DYLIB
cmdsize 48
name /usr/lib/libz.1.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1.2.11
compatibility version 1.0.0
Load command 13
cmd LC_LOAD_DYLIB
cmdsize 48
name /usr/lib/libc++.1.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 905.6.0
compatibility version 1.0.0
Load command 14
cmd LC_LOAD_DYLIB
cmdsize 56
name /usr/lib/libSystem.B.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1292.100.5
compatibility version 1.0.0
Load command 15
cmd LC_FUNCTION_STARTS
cmdsize 16
dataoff 1145456
datasize 2096
Load command 16
cmd LC_DATA_IN_CODE
cmdsize 16
dataoff 1147552
datasize 144
Load command 17
cmd LC_RPATH
cmdsize 88
path @loader_path/./../SharedSupport/plugins/twocan_plugin_pi/data/drivers (offset 12)
doug@Dougs-MacBook-Air ~ %

Bella Donna · 18-06-2023, 10:25

Thanks stevead--

I'm very happy to keep pursuing this if it holds the possibility of being helpful to the developer community. I don't have much in the way of developer skills (a bit of Xojo experience) but I'm fairly computer knowledgeable. So let me know if there's anything I can try from my end. Getting the tank level monitoring working is fairly low priority, so don't feel like I'm trying to pressure you.....

stevead · 19-06-2023, 00:27

There is something weird (aka different) with the rpath for the entry associated with the dynamic library libKvaserCAN.0.2.1.dylib

Note the differences between Load Commands 10 & 11.

I can't explain why it is different and I am not aware of any other users reporting a similar issue.

Anyway let's try and fix your problem.

At a terminal prompt, change to the folder where libtwocan_plugin_pi.dylib is located.

Then run the following command.

Code:

install_name_tool -change libKvaserCAN.0.2.1.dylib @rpath/libKvaserCAN.0.2.1.dylib libtwocan_plugin_pi.dylib

Bella Donna · 19-06-2023, 08:44

That did the trick! I now have access to TwoCan preferences. Thanks!

Given what you know about my setup, how should I configure the preferences? I've poked around and tried some different settings, but I'm not getting anything in the TwoCan debug window. The same data as before is coming into the OpenCPN debug window.

stevead · 19-06-2023, 10:27

Good news that we' ve resolved the initial problem, however I think we have a major disconnect.

For TwoCan you need to physically connect your Mac to the NMEA 2000 network using one of the supported CAN Bus adapters:
Kvaser Leaflight
Rusoku Toucan
Canable Cantact

Neither TwoCan nor OpenCPN's built-in NMEA 2000 feature support your YDNR-02 funky NMEA 2000 output over TCP/IP..

If the YDNR-02 converts NMEA 2000 to NMEA 183 and transmits it over TCP/IP then that would be your simplest option.

TwoCan documentation can be found at the following link

One thing that may be of interest to you is that the TwoCan plugin can replay Yacht Devices log files.

Bella Donna · 19-06-2023, 11:16

I'm glad to have been able to provide a bit of assistance!

I've suspected that we had a disconnect for a while, but I didn't/don't understand where.

So, given your understanding of what's going on on my end, and given that having fluid levels monitoring in OpenCPN is not worth changing my setup to provide physical connection to my Mac, do you think there's any possibility of getting the data into OpenCPN-->Engine Dashboard using NMEA Converter? I'm thinking that using the attached parsing document for the fluid levels data that I'm seeing in the OpenCPN debug window, if I knew the format that Engine Dashboard could decipher I should be able to construct a translator for NMEA Converter.

Or am I still barking up the wrong tree?

Should I be posting in a different thread?

stevead · 20-06-2023, 08:04

I was assuming that the YDNR-02 would convert NMEA 2000 PGN 127505 (fluid levels) to its respective NMEA 183 XDR sentence.

However upon reading the YDNR-02 manual, it appears that from page 51, it states that the conversion for PGN 127505 is to wrap NMEA 2000 data in a proprietary NMEA 183 DIN/PGN sentence.

Kind of stupid as the current NMEA 183 v4.11 standard fully defines XDR sentences including fluid levels. Perhaps Yacht Devices have fixed this with a firmware update.

In anycase from a quick perusal, provided the NMEA Converter plugin can perform an equality match on a NMEA 183 sentence field (ie. match the PGN), then it may be possible to generate a valid XDR sentence.

Good luck.

Bella Donna · 20-06-2023, 09:51

Thanks stevead--I'm writing to Alexey at Yacht Devices. I'll let you know if I get anything useful back....

Bella Donna · 20-06-2023, 13:34

From Yacht Devices:
"Two methods are currently adopted in the industry:

- SeaSmart/MiniPlex NMEA 0183 protocol extension — NMEA 0183 DIN/PGN sentence

- XDR sentences

SeaSmart/MiniPlex NMEA 0183 protocol extensions were implemented first, both more than 6 years ago,

their both specs were open, thus we adopted our NMEA 2000<-->NMEA 0183 converter to use SeaSmart/MiniPlex NMEA 0183 protocol extensions.

Back then NMEA 0183 has no XDR definition for "Fluid Level".

As Developer correctly mentions, "Fluid Level" via XDR was added only recently, in the latest NMEA 0183 Standard v4.11.

Thus we have not implemented it ( yet ? ) in our products."

Bella Donna · 21-06-2023, 08:29

I asked if and/or when it might be implemented in the Yacht Devices products, and this was their answer:

"I do not think it is necessary.

My position here is that OpenCPN Developers should add support for PGN and DIN sentences instead,

as they are supported not only in our products but in SeaSmart and MiniPlex products as well, and they are still strong on the market.

Thus, OpenCPN can cover more of the contemporary gateway products range.

It should be easy — for example, SeaSmart protocol extension ( with decoding and data examples ) is published on their site:

http://www.seasmart.net/pdf/SeaSmart...evG_043012.pdf

And to my knowledge, OpenCPN developers intend to support MXPGN sentences — they already got this sentence description in their technical library:

https://opencpn.org/wiki/dokuwiki/li...n_sentence.pdf "

stevead · 21-06-2023, 09:38

It appears as though you are stuck between a rock and a hard place.

I know for certain that ShipModul Miniplex gateways support NMEA 183 v4.11 XDR sentences for engine & fluid level data. I have communicated with Shipmodul in the past about their support for v4.11 standard transducer names.

In addition refer to page 84 in the ShipModul manual

So Yacht Device's claims are a tad specious.

I'm very sorry but I have no intention of updating the Engine Dashboard to support proprietary protocols.