Problem with G3PLC cenelecB - DSP PLC83 + AFE31

Hi Alessio,

Are you using mini DC or full DC? If you work with full DC, then it should work.

If you work with miniDC, then it seems that miniDC binary was not placed in the package.

Please contact the local SAE/FAE for the delivery.

Regards,

Il Han

Hi Kim,

thank for the response, but I've another question.

With the old version 7.3.1.6 I can use my device such as Base node(miniDC) and SN with the same binary using Intermediate GUI, now with the new version I must use two different version?

What is the difference between a miniDC and a full DC?

Thank for the response.

Alessio Roberti

Hi Alessio,

From version 7.7.x.x., we internally decided to separate the normal service node (SN) binary and the mini-DC binary (e.g. for maintenance purpose), so you need to use two separate binaries for mini-DC and the normal SN.

MiniDC only support 32 nodes, and full DC supports upto 1024 nodes, and thus needs a new hardware.
www.ti.com/.../tidep0006

Regards,
Il Han

Hi Il Han,

An information, I think that the division of mini and full DC was made for the memory in the PLC83 that is small, but if I want a "intermediate DC" with only 250 device max you think that with the sources of miniDC can I make this expansion or not?.

If we send a request to my local distribution can I have the program sources of Sitara?

In miniDC is corrected the problem with Cenelec B?

Thank you

Alessio

Hi Alessio,

No, you cannot make that expansion (250 device max) with miniDC, and in this case, you need to use full DC.

If you can use a binary for mini-DC that can be obtained from local distribution, then you can run the network on CENELEC B band.

Regards,

Il Han

Hi Il Han,

I've some question, the full-DC can be run on other linux machine (es: raspberry....)?

In the document of DC you said that to run the "g3_dc_L138.exe" (in the bin folder is named "g3_dc_AM335X_aes_msb_loadng" but I think is the same) in cenelec B band I can use the "-B" parameter to set the TONE MASK and write this on a file, but how do I write this hex value on file?
If I use the miniDC in a system with more 32 device, what happen to the miniDC, they work also but only with 32 device or the other devices can block the miniDC?

Thank for the response

Alessio

Alessio,

Sorry for the delayed response, not sure if you already resolved this, but we will get back to you on this.

Thanks,
Il Han

hi Alessio,

in the DC SDK you would find the g3_dc_AM335X_aes_msb_loadng.exe that is to be run for the Full/ Big DC .

Start the DC with the -B CENB.txt , the

CENB.txt file should simply have the tonemask written as below...
0x3F 0x10 0xFF .....0x00

eg. for CENA25
0x17 0x24 0xFF 0xFF 0x00 0xF8 0x0F 0x00 0x00 0x00 0x00 0x00 0x00 0x00

If the miniDC is made to connect to a network having 32 nodes , it would simply connect to at- max 32 and neglect the rest .( no join).

Regards.

Hi,

thank for the response. Now we use the full dc with a beagleboard black. 

From some time we receive this kind of message from the "g3_evt_mon".

Event Nr: XX
Time: Mon Jan 25 14:31:35 2016
Event type: G3_EVT_TYPE_NWK_STS_INDICATION
Status Type <0x20db>
Additional Info <Src Short-Addr<0x2>>

From the manual I saw that is a " MAC_STAT_COUNTER_ERROR = 0xdb + G3_ERROR_CODE_MAC_GROUP"

But what mean this kind of error?

Thank you 

Alessio

Dear Meghana

we have another truouble With Full DC. We are using it in a plant with 170 slave devices (nodes) . When we run the plant partially, the first 70 nodes linked up and we can see them on the supervision,  but when we try to connect the other devices all the system crush down  and all the device fails to connect ( the first 70 too). 

Can you give us any suggesstion to try to solve this problems?

Thank you.

Best regards

Alessio Roberti

Hi Alessio ,

First of all the Big DC that i am referring to is the one in the link below

Please check if the G3 PLC code would run straight away on the Beagle bone ..it all depends on the AM SDK versions that are being used on both the devices , the UART port configurations between the AM335 and the PLC SOM, etc ...

The error MAC_STAT_COUNTER_ERROR is caused when the Frame counter is say 0xFFFFFFFF or if a lower frame counter packet is sent after a larger frame count packet etc ...

The Big DC supports 1200 devices and should not crash with just 170 .

Regards.

Hi Meghana,

I will describe more accurately our system.

We have used a beaglebone black board such as this your product:
www.ti.com/.../spruht4.pdf
I've followed the instruction and have used ti-sdk-am335x-evm-08.00.00.00 for linux and v4.7.0.6 on the PL83 that is our custom board.
We have made a change on beaglebone, the comunication between PLC board and beaglebone is made with serial port and not usb.

Our system work in a strange mode.

If we feed the 170 device, 20 at once, the system seems to work but when we get to 70 device connected and we try to power other device, the DC have strange functionality, the devices those are connected started to disconnect and no other device returns attached on the DC. In this case sometime, we get receive message from SN with MAC_STAT_COUNTER_ERROR.
We have also the problem if we will power-on all the 170 devices at the same time.

Thank you for the response

Alessio

hi Alessio,

First of all we use the below tool chain in Big DC - ti-sdk-am335x-evm-06.00.00.00 for linux. the Beagle bone asks for the ti-sdk-am335x-evm-07.00.00.00 tool chain .

the frame counter error can come in case the frame counter is overwritten , corrupted or the sequence of packets sent have a smaller frame count compared to the one sent earlier ..

Just to validate the if all the service nodes are working fine you can make one of the node miniDC ( pre 7.7 version if plc83 or 7.7 version if plc84  ) and then check if the setup has the issue as the miniDC can connect to 75 without any issue ...then involve DC with Beagle bone .

Regards.

Hi Meghana

Thank you for your reply, but i didn't understand thelast period of your reply: with miniDC you told me is possible to connect until 32 nodes, so how i can try 75 SN with miniDC?

Now i 'll try to use the version you have indicate me 07.00.00.00 and i let you know. Please give me more information about the test with minidDC and 75 SN.Thank you for your support.

Regards

Alessio

hi Alessio,

Actually i was indicating at checking the 75 nodes as the SN can ideally have 75 nodes as neighbors but the minidc can only connect to 32 as i mentioned before .it is possible if we have say 2-3 minidc networks but the SN's of the different network talking to each other ..

Can you share the DC syslogs for the 2 cases below with max log level?

"If we feed the 170 device, 20 at once, the system seems to work but when we get to 70 device connected and we try to power other device, the DC have strange functionality, the devices those are connected started to disconnect and no other device returns attached on the DC. In this case sometime, we get receive message from SN with MAC_STAT_COUNTER_ERROR."
and
"We have also the problem if we will power-on all the 170 devices at the same time."

Regards.

Hi Meghana

we need two explanation.

When you say that we can use 2-3 miniDC in the same network for test more than 32 device, the PAN network of each one mini-DC are the same or are three different PAN.

Now I can't create what do you need, but I think that can made that soon. You can explain me how can change log level e what file I need to send you?

Thank You

Alessio

hi Alessio ,

if the PAN id is the same they will have issues communicating to each other because of redundant / same addresses so different pan id would be better .

To change syslog " log " level use command
inside PLC / folder --> vi /etc/syslog-startup.conf
set log level to 8.

To get syslog
inside PLC folder ---> vi /var/log/messages.

Regards.

Dear Meghana

i think you must help me since the begin of the configuration of 1 simple net of devices: I build our simple net of devices  with 1 BN and  n.6 SN connected  in series with distance  50 cm each one. When i try to start the net i can see that  only one of the SN ( that i ll name MOM) reach  to connect directly to BN and the others connect to BN passing trought the MOM. If i disconnect the MOM the other SN  disconnect too. If i change  the position of  MOM  in the series the situation doesn't change . All the SN are identical hardware and software. Please tell me : That is the question?

Dear Meghana 

adding my last request i want ask you if a manual about functions of G3PLC net configuration is available. We have not clear the working of routing fo devices,for example how works the paramenters MAC PIB on the zero configuration GUI.

Thank you

hi Alessio ,

From your observation it seems that as the node used to form the hop in a network MOM is removed the node connected will also be removed .

Here what is the data transfer happening .. is the DC pinging the nodes ? ideally when the MOM is off the network any further activity to nodes using the MOM will remove the route to the nodes as the entry to the MOM itself would be removed if the MOM is removed from the network and the DC pings to MOM .

the details on the G3 network behavior can be got from the SPEC ,

rest of the details can be got in the  TI G3 User Guide-Zero Config GUI.pdf related to the Zero config  gui .

Regards .

Hi Meghana,

Thank for the reference manual. We have isolated the MAC_STAT_COUNTER_ERROR error and from the log we receive this information:

Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> SBD <0x68b94> freed
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BD <7149>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BUF <2383>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_malloc> SBD allocated <0x68b7c> bufLen <37>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_malloc> SBD allocated <0x68bb8> bufLen <64>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> SBD <0x68b7c> freed
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BD <7148>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BUF <2382>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MAC_checkRxCnt> RxPacket-SrcAddr (0x19), RxPacket-frameCnt (0x3c) keyID(0x0)
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MAC_checkRxCnt> SrcAddr (0x19) is in RX-Table index(0x11),valid-framecnt(0x1), frameCnt(0x00000045) seq#(0xba)
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MAC_checkRxCnt> tbl-index(0x11) frame error srcAddr(0x19) old-frameCnt(0x45) RxFrameCnt(0x3c) keyID(0x0)
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> SBD <0x68bb8> freed
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BD <7149>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <MP_SBM_pool_free> N of free BUF <2383>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <ADP_pnm_bn_macCommStsIndHndlr> status<8411>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <ADP_macCommStsIndEvt> status<8411>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <EVTM_checkEvtEna> eventId<2056> / fd<7>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <UTIL_writeSock> sockFd<7>/cnt<86>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <UTIL_writeSock> write<86>
Mar 3 18:46:14 am335x-evm daemon.info G3 Base Node: <UTIL_writeSock> bytesLeft <0>

My question is: Why the two counters, RxFrameCnt and old-frameCnt, are different and How can "re-sync" this two counters for remove this kind of error?

For the question about new SN that non connected to the BN, instead the old SN started to disconnect, I had this log:

Error_PSKsvr972.txt

and at the 973 Line We can see

"am335x-evm user.err psksvr_AM335X: <PSKSVR_getPSKforEUI> Unable to open file pskeuilist, errno 2. Using default PSK."

What mean and why we receive this information?.

Thank You

Alessio

hi ALessio,

The old Frame count is for previous packet received and rx frame counter is for current frame . it should be ideally greater that the old frame else we would get the MAC ERROR . this is sent by the SN to the DC please check at SN end .

the error on line 973 is because we can also have a file called pskeui list that is used to define the list of nodes the DC joins to .
but in normal case we use default and not the list hence this error is fine .

regards.