J1939 PGN 65030

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 1:39 pm

Hi me again,

Im having a masive problem getting 3 Maretron ACM100 AC Monitors to work on PV750. The Maretron devices are suposed to be NMEA2000 but seam to be J1939 They have a device class of 30, a device function of 140, data source of 255 and I have three set with insidance 0,1,and 2. I have set SPNs etc and no matter what I cant get any of the values to display. The devices are working fine and can see the values in 65030 using the Software supplied by Maretron (N2KAnalizer) using their USB100 gateway. I can also see the devices using Actisense USB to NMEA Gateway and in their NMEA Reader software. Though their software does not give me values.

Has anyone got any ideas? I am running out of time on this project as the PV750 is on a new boat which is off to Kenya by ship this Saturday. So I only have one more full day to get things finished. I have been getting help from FWM in UK and UK supplier but as of yet no solution has been found. I am worried that the J1939 has been somehow adapted to suit NMEA2000 but really dont know. Maretrons NMEA2000 display products display this data by default of course.

Any help welcome.

Thank you,

Simon

Post by **ksaenz** » Thu Oct 13, 2011 2:54 pm

Hello simonchurchill,

I assume you added PGN 65030 to the database, did you check the NMEA box?

Which CANPort are you using?

What are the settings of the device you set-up in the CANPort to read the parameters?

Regards,

ksaenz

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 3:13 pm

Hi Ksaenz,

Yes 65030 added to database and added in various ways so far, i.e. have tried it as NMEA2000 with insidances and without. Tried as J1939 also. Using CanPort 3 and have tried many ways to set up in canport.

I am one of I think at least 4 people to have got involved in this one and I am starting to think Maretron are not keeping things simple?

I can sent screen shots if you like?

Thanks

Simon

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 3:17 pm

Method 1

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 3:18 pm

Method 2

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 3:22 pm

Method 3

simonchurchill · Post by **simonchurchill** » Thu Oct 13, 2011 3:25 pm

Database Example,

Other 65030 lines are same but for where this one has type as bit, others are measured and signed.

Post by **ksaenz** » Thu Oct 13, 2011 4:02 pm

Would it be possible for you to send me the configuration file (.murphyConfig) and a CAN log by PM?

Thank you,

ksaenz

mbowdich · Post by **mbowdich** » Fri Oct 14, 2011 9:51 am

This may seem like a no brainer question, but are you applying 12VDC to the connections on Port 3?

simonchurchill · Post by **simonchurchill** » Sat Oct 15, 2011 10:12 am

Yep 12V power connected.

Problem is now sorted.

In the end we set up ACM100s as J1939 devices and used a static address for each.

When viewing each of the devices properties we could see the addresses as being Hex C0, C1 and C3. So in the source address box entered 192, 193 and 194 for each.

I hope that these addresses stick and dont change? I did notice that the devices addresses seamed to follow my instancing i.e. I had already given the three ACM100s an instance of 0, 1 and 2. It was after this I noticed that the source addresses matched my instance setting (each ACM100 can have its instance set manualy in software, they are all set to 0 by default) C0 = 0, C1 = 1 and C2 = 2. Is this a coinsidance? Will they keep these source addresses?

mbowdich · Post by **mbowdich** » Mon Oct 17, 2011 7:39 pm

Make sure you double check the J1939 bus with a CAN analyzer for your address claims. I am not familure with the ACM100, but it may be following your instance scheme not statically, but dynamically during the address claim process. (i.e. - all start with address 192, but get incremented during address claim.) If it is dynamically changed during claim, then there is the possibility of the address being assigned at random during the boot up process.

This happens with multiple PV750/450s on the same bus when assigned the same address; they pull from the pool of available addresses, and if the pool is set to small, they keep attempting address claim indefinately. It's better to check and be safe, than sorry.

J1939 PGN 65030

J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030

Re: J1939 PGN 65030