Activity for Ethernet/IP Explorer & C# Stack

alki posted a comment on discussion General Discussion

alki — Thu, 06 Feb 2025 14:14:27 -0000

Thanks for adding everything into r58. I forgot to mention in my list of changes that I also optimized the tabbing order of the fields within the ExplicitMessages window.

F. Chaxel committed [r58] on Code

F. Chaxel — Wed, 05 Feb 2025 14:55:58 -0000

ExplicitMessage improvement by alki

alki posted a comment on discussion General Discussion

alki — Wed, 05 Feb 2025 14:23:03 -0000

Hi! I did some improvements in the ExplicitMessages window. Inhibiting the Data field for certain services not needing a data payload, thus preventing errors if data values still happen to be around (like GetAttributesAll, Get_Attribute_Single, NOP, GetMember, RemoveMember) Refreshing the SendWindow text box whenever you jump from one field to the next Re-activated the tb_data_Leave() function by adding a handler to the tb_data text box while commenting out the string manipulation stuff not being...

F. Chaxel committed [r57] on Code

F. Chaxel — Mon, 03 Feb 2025 16:12:32 -0000

Patch by alki

alki posted a comment on discussion General Discussion

alki — Mon, 03 Feb 2025 14:43:32 -0000

Added this entry to CIPObjectLibrary of Enums.cs. Anybus_ADI_Object = 0xA2,

alki posted a comment on discussion General Discussion

alki — Mon, 03 Feb 2025 14:40:46 -0000

I propose the following change: delete line 180 in ExplicitMessages.cs because the getExtraData() call in line 188 will take care of concatenating the data bytes. Otherwise you'll have the data field twice causing an error in the adapter. See attached Wireshark screenshots explicit_msg_nok.png and explicit_msg_ok.png private void b_send_Click(object sender, EventArgs e) { refreshSendWindow(); List lb = new List(); List path = GetPath(getClasseId(), getInstanceId(), getAttributeId());...

alki posted a comment on discussion General Discussion

alki — Thu, 23 Nov 2023 07:58:10 -0000

Thank you for releasing SetupEnIPExplorer_1.2.1.exe!

F. Chaxel committed [r56] on Code

F. Chaxel — Wed, 22 Nov 2023 15:09:35 -0000

Ethernet/IP Explorer & C# Stack released /SetupEnIPExplorer_1.2.1.exe

Ethernet/IP Explorer & C# Stack — Wed, 22 Nov 2023 15:09:02 -0000

alki posted a comment on discussion General Discussion

alki — Wed, 22 Nov 2023 08:21:42 -0000

Hello fchaxel , as before with r53, I'd like to recommend Ethernet/IP Explorer to a customer who's specifically asking for explicit message support. With the above bug entry, I just realized that explixit messaging is broken since r53. Could you therefore compile a new release incorporating the latest commits, please ? Thank you!

F. Chaxel committed [r55] on Code

F. Chaxel — Thu, 14 Sep 2023 03:08:38 -0000

Patch by Wouter van Kesteren

Wouter van Kesteren modified a comment on discussion General Discussion

Wouter van Kesteren — Tue, 12 Sep 2023 14:13:53 -0000

In https://sourceforge.net/p/enipexplorer/code/53/ there was a wrongfully deleted line. Instead of removing lb.AddRange(path); inside of b_send_Click the line above it should have been removed. The following patch corrects it and makes it match up with refreshSendWindow again. diff --git a/EnIPExplorer/ExplicitMessages.cs b/EnIPExplorer/ExplicitMessages.cs index ae073a4..c21375b 100644 --- a/EnIPExplorer/ExplicitMessages.cs +++ b/EnIPExplorer/ExplicitMessages.cs @@ -176,7 +176,7 @@ namespace EnIPExplorer...

Wouter van Kesteren posted a comment on discussion General Discussion

Wouter van Kesteren — Tue, 12 Sep 2023 14:13:21 -0000

In https://sourceforge.net/p/enipexplorer/code/53/ there was a wrongfully deleted line. Instead of removing lb.AddRange(path); inside of b_send_Click the line above it should have been removed. Follow patch corrects it and makes it match up with refreshSendWindow again. diff --git a/EnIPExplorer/ExplicitMessages.cs b/EnIPExplorer/ExplicitMessages.cs index ae073a4..c21375b 100644 --- a/EnIPExplorer/ExplicitMessages.cs +++ b/EnIPExplorer/ExplicitMessages.cs @@ -176,7 +176,7 @@ namespace EnIPExplorer...

alki posted a comment on discussion General Discussion

alki — Thu, 15 Sep 2022 14:30:45 -0000

That's great - appreciate!

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Thu, 15 Sep 2022 11:17:40 -0000

Hi Done. Bye.

F. Chaxel committed [r54]

F. Chaxel — Thu, 15 Sep 2022 11:16:48 -0000

Ethernet/IP Explorer & C# Stack released /SetupEnIPExplorer_1.2.exe

Ethernet/IP Explorer & C# Stack — Thu, 15 Sep 2022 11:16:03 -0000

alki posted a comment on discussion General Discussion

alki — Thu, 15 Sep 2022 07:41:16 -0000

Hi, do have a new release planned some time? I would love to see one incorporating commits r53 from 2021-05-21, since I'd like to recommend your EIP Scanner to our customers. Thank you!

F. Chaxel committed [r53]

F. Chaxel — Fri, 21 May 2021 03:54:28 -0000

Two patchs by alki

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Fri, 21 May 2021 03:40:07 -0000

Hi, Yes this line of code was here at the beginning of the communication stack development process, and its removal was forget. Bye.

alki posted a comment on discussion General Discussion

alki — Thu, 20 May 2021 07:59:53 -0000

Since this tool reads out the I/O data lengths for Class 1 connections (Implicit Messaging) anyway I don't see a reason to define the Forward_Open T->O Connection Size Type as "variable". It should be "fixed" instead. In particular, Anybus CompactCom for EtherNet/IP based network interfaces do not accept variable size types. I could mitigate this by simply commenting out this line in EnIPBase.cs which seems out of place anyway : if (conf.O2T_P2P) O2T_ConnectionParameters = 0x4800; else O2T_ConnectionParameters...

alki modified a comment on discussion General Discussion

alki — Thu, 20 May 2021 07:52:26 -0000

Possible fix in ExplicitMessages.cs: (1) Substitute getAttributeId() by this (probably some cut&paste error) : private UInt16 getAttributeId() { UInt16 attributeId; if (!(UInt16.TryParse(tb_attribute.Text, out attributeId))) { attributeId = 0; tb_attribute.Text = "0"; } return attributeId; } (2) These lines need to be deleted otherwise this CIP is sent for a simple Get_Attribute_Single Identity request [0e 04 0e 03 20 01 24 01 30 01] instead of this [0e 03 20 01 24 01 30 01] : lb.Add(getServiceId());...

alki modified a comment on discussion General Discussion

alki — Thu, 20 May 2021 07:51:28 -0000

alki posted a comment on discussion General Discussion

alki — Thu, 20 May 2021 06:37:03 -0000

Thanks !

F. Chaxel committed [r52]

F. Chaxel — Thu, 20 May 2021 02:24:53 -0000

Small patch on ExplicitMessages.cs

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Thu, 20 May 2021 02:23:20 -0000

Hi, This ExplicitMessages form is a third party code to this application & protocol stack. I've never look inside it. Sure tb_attribute should replace tb_class (a bad copy/paste certainly), at two places. For the request construction the two lines supression (at two places !) and the ByteArrayToString convertion I will check it soon. Bye.

alki posted a comment on discussion General Discussion

alki — Wed, 19 May 2021 15:32:40 -0000

Possible fix in ExplicitMessages.cs: (1) Substitute getAttributeId() by this (probably some cut&paste error) : private UInt16 getAttributeId() { UInt16 attributeId; if (!(UInt16.TryParse(tb_attribute.Text, out attributeId))) { attributeId = 0; tb_attribute.Text = "0"; } return attributeId; } (2) These lines need to be deleted otherwise this CIP is sent for a simple Get Attribute Identity request [0e 04 0e 03 20 01 24 01 30 01] instead of this [0e 03 20 01 24 01 30 01] : lb.Add(getServiceId()); lb.Add(((byte)(path.Count...

Giova posted a comment on discussion General Discussion

Giova — Fri, 18 Dec 2020 20:24:45 -0000

Explicit messages function doesn't permit to insert Attrbute. Path segment error is generated. Any solution? Thanks.

Jonathan Sánchez U posted a comment on discussion General Discussion

Jonathan Sánchez U — Fri, 14 Aug 2020 02:50:32 -0000

getAttributeId method is using cb_class value getAttributeId method Line 429 possible fix: if(!(UInt16.TryParse(tb_attribute.Text, out attributeId))) Maybe same issue in tb_attribute_Leave method as well but I have not checked

F. Chaxel committed [r51]

F. Chaxel — Tue, 05 May 2020 06:23:38 -0000

Small patch by tswaehn

F. Chaxel committed [r50]

F. Chaxel — Sun, 15 Dec 2019 07:20:15 -0000

Download snapshot information

F. Chaxel committed [r49]

F. Chaxel — Wed, 13 Feb 2019 07:32:52 -0000

Change in Universal Robot user decoder structures

F. Chaxel committed [r48]

F. Chaxel — Sun, 03 Feb 2019 17:21:39 -0000

Minor improvments during grid update

F. Chaxel committed [r47]

F. Chaxel — Sun, 03 Feb 2019 13:39:17 -0000

Rollback enum reordering & Getsbyte method patch

F. Chaxel committed [r46]

F. Chaxel — Fri, 01 Feb 2019 16:54:31 -0000

Simplification in ForwardClose call

F. Chaxel committed [r45]

F. Chaxel — Fri, 01 Feb 2019 03:56:23 -0000

Missing update

F. Chaxel committed [r44]

F. Chaxel — Thu, 31 Jan 2019 16:48:55 -0000

Small update

F. Chaxel committed [r43]

F. Chaxel — Sun, 27 Jan 2019 07:36:12 -0000

Small patch : wrong buffer size for LargeForwardOpen request

F. Chaxel committed [r42]

F. Chaxel — Mon, 17 Dec 2018 05:40:33 -0000

smal bug patch

Rasty Slutsker posted a comment on discussion General Discussion

Rasty Slutsker — Sun, 16 Dec 2018 15:50:11 -0000

The same mistake in public void SetInt32

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Mon, 03 Dec 2018 05:20:05 -0000

Hi, Thank's for the bug fix. Bye.

F. Chaxel committed [r41]

F. Chaxel — Mon, 03 Dec 2018 05:19:08 -0000

Bug fix : unappropriate data type used for LREAL coding

Rasty Slutsker posted a comment on discussion General Discussion

Rasty Slutsker — Sun, 02 Dec 2018 16:40:47 -0000

Found the problem public void SetDouble(ref int Idx, byte[] buf, Double? val) instead of public void SetDouble(ref int Idx, byte[] buf, UInt64? val)

Rasty Slutsker posted a comment on discussion General Discussion

Rasty Slutsker — Sun, 02 Dec 2018 14:08:56 -0000

Hi I try to create custom decoder with LREAL. REAL works, but show gagbage, if I change t LREAL it disappears from the list in context menu. Axis pnStatus;UINT axNumber;UINT drStat;UINT busCycle;UINT pcmd;LREAL Did someone try LREAL fileds? Thank Rasty

F. Chaxel committed [r40]

F. Chaxel — Wed, 16 May 2018 13:46:04 -0000

Hex display option of integer values in the property grid

F. Chaxel committed [r39]

F. Chaxel — Tue, 15 May 2018 15:46:04 -0000

UserType compiler patch

Ethernet/IP Explorer released /SetupEnIPExplorer_1.1.exe

Ethernet/IP Explorer — Wed, 09 May 2018 15:23:56 -0000

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Tue, 08 May 2018 14:07:07 -0000

I've made a mistake in the Read/Write process analysis. Frames 820-821 : Read 0x96 att3 return 32 byte 0 Frames 934-935 : Write 0x96 att3 byte 30 (start counting at 0) to 0x10 is OK Frames 936-937 : Read back get the byte at 0x10. So seems to be a display problem.

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 14:07:00 -0000

Hello, I've just downloaded and compiled your new Version. After that I went to implicit Messaging and the conection Lights of the Axis changed to always on, after I pressed Forward Open. After that changes in the Output structure are shown on the Axis software and finally I managed to move the Axis. A BIG BIG THANK YOU for your help. We made a big step forward. I have to check if we can use your code to write a DLL to interface to the Axis form C++. Can you please give me some contact data so that...

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Tue, 08 May 2018 12:36:12 -0000

Quite strange Write shows only 26 bytes written. So off course byte n°30 is not modified when readed back ! Try to write first byte (or bellow byte n°26). I have to see why it's like this and why all the array is not sent ! ... but this tool has not be tested with a lot of devices (only 2 in fact). The EDS file shows a config assembly instance #5. You can try implicit messaging using the 3 assemblies attributs instance : using the last source code from this morning will be better than the .exe from...

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:29:04 -0000

But The Data to the Axis is not sent. (I also tried the first Bytes, also a completely correct filled 32 Byte Block)...

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:27:46 -0000

In Ethernet/IP Explorer -> I see the Output of the Axis

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:27:01 -0000

second - the Data, the Input is all 0

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:25:46 -0000

From the RC-Software of the Axis

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:25:09 -0000

Second capture. I restarted teh Program, opened teh interface, clicked the Tree, Opened Implicit Messaging, Moved my Assemblys to O->T / T->O and clicked forward open. The Interesting for me: When I change some Values which should be written to the Axis, I can end the Ethernet/IP and restart it, and I still see the same changed values. On the Axis I do ont see any changes...

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:16:02 -0000

First capture. I did all Changes directly in the GUI. I clicked to the Assembly #100/150, then I changed Byte 30 of Assembly #150 to 16 and got a write OK. After that I clicked to the Assembly #100/150 agian.

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Tue, 08 May 2018 12:06:49 -0000

First File the EDS... I will try to do the Wireshark captures and post them later on...

F. Chaxel committed [r38]

F. Chaxel — Tue, 08 May 2018 06:42:25 -0000

Somes changes with ForwardOpen (Path, Transport field, Data size)

F. Chaxel committed [r37]

F. Chaxel — Mon, 07 May 2018 14:47:24 -0000

Adds forgotten CIP Type

F. Chaxel posted a comment on discussion General Discussion

F. Chaxel — Mon, 07 May 2018 12:30:59 -0000

Hi, Maybe implicit (Forward open) messaging is required to write into the device. Please post a link to the eds file or the file itself ... a config assembly is sometimes required for Foward Open connection (even with 0 byte) and the eds file shows it. Could you post a wireshark capture of the write operation who says OK but not working : to looks at the device response ? .. also maybe the Forward open connection with the error response. Bye.

Bernd Tinkl posted a comment on discussion General Discussion

Bernd Tinkl — Mon, 07 May 2018 07:47:45 -0000

Additional Info: In the Software of the Axis I can setup the Structure of the Ethernet/IP data (Operation Mode). When I change it I can see that the ammount of Data in the exchanged Assemblys also changes. Bernd