Re: [DISCUSS] Having a in-person community meetup?
Ah... if there is TAC support, I will forward this message to IoTDB community to see if there are committers want to join for the Historian development face to face. --- Xiangdong Huang School of Software, Tsinghua University Christofer Dutz 于2023年1月5日周四 18:59写道： > > Hi Jinlin, > > Would you be willing and able to attend such an event? > You would be more than welcome. > > As I’m also part of the Apache Travel Assistance committee … I’d also like to > ask any others here too: > Would you like to attend such an event, but the costs of travelling are what > you can’t afford or would have a too big impact on your budget to be willing > to come? > > Because there theoretically is the option of having Apache cover the costs > for travelling and accommodation. However, this would put quite a lot of > extra work for us for setting it up and running it. > So, if it’s only 1-2 people, this probably doesn’t make much sense, but if > there were more, it might make sense. > > And please … don’t say: “I can’t afford it and would like assistance”, if the > problem is that the fuel has become too expensive for your Ferrari or the > parking costs for your private jet are skyrocketing ;-) > > And if you don’t want to publicly answer … feel free to DM me. > > Chris > > > From: jl hong > Date: Thursday, 5. January 2023 at 02:16 > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Having a in-person community meetup? > This sounds exciting :) > > Jinlin > > Lukas Ott 於 2023年1月5日 週四 上午12:11寫道： > > > cool :-) would be fun so that I can finally ask all my questions in person > > ;-) > > > > Am Mi., 4. Jan. 2023 um 16:37 Uhr schrieb Ben Hutcheson < > > ben.hut...@gmail.com>: > > > > > Sounds like fun. > > > > > > Ben > > > > > > On Wed, Jan 4, 2023 at 4:30 PM Christofer Dutz < > > christofer.d...@c-ware.de> > > > wrote: > > > > > > > Ok … > > > > > > > > Uwe from codecentric FFM (the new office) was delighted my me asking if > > > > codecentric would be willing to accommodate us during the hackathon. > > > > So, that would be one option … I guess Sebastian would like that option > > > ;-) > > > > > > > > Chris > > > > > > > > > > > > From: Christofer Dutz > > > > Date: Wednesday, 4. January 2023 at 16:24 > > > > To: dev@plc4x.apache.org > > > > Subject: [DISCUSS] Having a in-person community meetup? > > > > Hi all, > > > > > > > > some of you remember the times around our graduation. We had loads of > > > > in-presence meetups and that really fuled the drive in the community. > > > > Covid sort of was the opposite and it felt like we were sort of losing > > > our > > > > drive a bit. > > > > > > > > Now that Ben now also lives in Germany, I wanted to bring up this topic > > > > again. > > > > > > > > What do you folks think of a 2-3-day hackathon on PLC4X (and possibly > > the > > > > Historian)? > > > > Probably we would need to sort of do it Friday to Sunday. > > > > > > > > Also currently probing if we could not get TAC to help finance the > > > travels > > > > of everyone except me. > > > > > > > > Even if I would love a week on the Bahamas, probably something in > > Germany > > > > somewhere round Frankfurt or Stuttgart would make sense > > > > (from the perspective of people being able to come there via public > > > > transport and keeping the connection options simple and cheaper) > > > > > > > > What do you folks think. > > > > > > > > > > > > Chris > > > > > > > > >
Re: AW: Building a PLC4X and IoTDB Historian?
> If we get something to work in private we could easily go TLP or through the > Incubator whatever is decided then to do. +1 --- Xiangdong Huang School of Software, Tsinghua University Niklas Merz 于2022年11月28日周一 21:08写道： > > Hello all, > > I think this is a good compromise to get started and then publish it > with a bit of fanfare (marketing) as an Apache project to the world once > it's ready. > > I am also interested in working with you on this project. I think PLC4X > and IoTDB need something like this to become popular in the automation > world. > > Regards > Niklas > > On November 28, 2022, Julian Feinauer > wrote: > > I fully agree with that. > > If we get something to work in private we could easily go TLP or > > through the Incubator whatever is decided then to do. > > > > Julian > > > > PS.: Do you setup the repo and invite myself? > > > > Von: Christofer Dutz > > Datum: Montag, 28. November 2022 um 13:47 > > An: dev@plc4x.apache.org > > Betreff: Re: Building a PLC4X and IoTDB Historian? > > And if we already agree on a name (I think “Apache Historian” would be > > a good name), > > we could even already work on code with that package-name and maven > > coordinates, so we don’t have to change much when coming to Apache? > > > > Chris > > > > From: Christofer Dutz > > Date: Monday, 28. November 2022 at 13:18 > > To: dev@plc4x.apache.org > > Subject: Re: Building a PLC4X and IoTDB Historian? > > Hi Julian, > > > > Indeed, your concerns are valid regarding creating an already > > abandoned TLP. > > > > In that case, I would opt for a private repo on GitHub which we invite > > everyone willing to help work on it and as soon as we have something > > workable, we make it public as part of a TLP? > > > > This avoids at least the fear of creating a new TLP that’s product > > doesn’t even see the light of day. And as soon as we have something we > > want to show the world, we join Apache? > > > > Would that be a compromise? > > > > > > Chris > > > > From: Julian Feinauer > > Date: Monday, 28. November 2022 at 13:14 > > To: dev@plc4x.apache.org > > Subject: AW: Building a PLC4X and IoTDB Historian? > > Hey, > > > > as I said.. we could just do it as part of one of the TLPs like PLC4X > > or IoTDB easily or in a private repo as well, for sure. > > I just want to avoid to create a TLP which is soon abandoned, that’s > > my only concern. > > Regarding all your comments I totally agree and am with you. > > > > Julian > > > > Von: Christofer Dutz > > Datum: Montag, 28. November 2022 um 13:07 > > An: dev@plc4x.apache.org > > Betreff: Re: Building a PLC4X and IoTDB Historian? > > Hi Julian, > > > > well … I would be hesitant to try something like this without the > > legal shield of the ASF … from what I’ve learned in the early days, > > Siemens and Co. continuously threatened to sue me for my work on > > PLC4X. > > The only thing that helped me then, was to say: I am doing everything > > legally, so you’d have trouble succeeding with that and you also can’t > > sue me but would have to sue the ASF and good luck on that not > > backfiring badly on you publicly. > > > > I know that in the sector of drivers in the past there were several > > occasions where open-source developers were annoyed so much by > > nuisance law-suites, that they gave up. > > > > I also know Historians are silly expensive systems. I haven’t seen one > > under 100k€ and the annual fees for certified solutions tend to start > > at 100k€/year/production-line … so there’s a lot of money for them to > > fear losing. So yes: I’m too scared to try something like this > > publicly without a legal shield. > > > > We could however work on something like this in a protected repo at > > GitHub etc. and go to TLP as soon as we have something. > > > > Would that be an option? > > > > Chris > > > > > > From: Julian Feinauer > > Date: Monday, 28. November 2022 at 12:57 > > To: dev@plc4x.apache.org > > Subject: AW: Building a PLC4X and IoTDB Historian? > > Hey Chris, > > > > wrt testing I meant how „sustainable” the community is, that we intend > > to building. > > You know the effect pretty well if you ask “How wants to start this” > > everybody is like “me, me, me” and after 2 weeks you stand there > > alone. > > And one important aspect of a TLP for me is that the c
Re: Building a PLC4X and IoTDB Historian?
> I guess I would sort of also vote for a separate Project. Would however only > make sense if some people from both of our projects would join in. Agree, I think the iotdb developers in Timecho can join. > And name-wise … one of the names of Historic Historians (Ideally a Greek one) > would make it into my top 10 ;-) … sort of like Hudson or Jenkins are > “famous” Buttler names ;-) If we consider famous names (well, there will be culture bias), I'd like to suggest this one: https://en.wikipedia.org/wiki/Sima_Qian , as "Records of the Grand Historian" is tooo famous (at least in China). BTW. naming "Apache Historian" directly may be another option. Best, ------- Xiangdong Huang School of Software, Tsinghua University Christofer Dutz 于2022年11月27日周日 22:56写道： > > How about Apache Ephorous? ;-) > > https://en.wikipedia.org/wiki/Ephorus > Ephorus of Cyme (/ˈɛfərəs/<https://en.wikipedia.org/wiki/Help:IPA/English>; > Greek<https://en.wikipedia.org/wiki/Greek_language>: Ἔφορος ὁ Κυμαῖος, > Ephoros ho Kymaios; c. 400 – 330 BC) was an ancient > Greek<https://en.wikipedia.org/wiki/Ancient_Greece> > historian<https://en.wikipedia.org/wiki/Historian> known for his universal > history<https://en.wikipedia.org/wiki/Universal_history>. > > Chris > > From: Christofer Dutz > Date: Sunday, 27. November 2022 at 15:28 > To: dev@plc4x.apache.org > Subject: Re: Building a PLC4X and IoTDB Historian? > Hi all, > > I guess I would sort of also vote for a separate Project. Would however only > make sense if some people from both of our projects would join in. > > And name-wise … one of the names of Historic Historians (Ideally a Greek one) > would make it into my top 10 ;-) … sort of like Hudson or Jenkins are > “famous” Buttler names ;-) > https://en.wikipedia.org/wiki/List_of_Greek_historiographers > https://en.wikipedia.org/wiki/List_of_historians > > I think anything but a turnkey-ready solution will not be accepted by anyone > in the Automation industry. > > Chris > > > > > From: Xiangdong Huang > Date: Sunday, 27. November 2022 at 14:05 > To: dev@plc4x.apache.org > Subject: Re: Building a PLC4X and IoTDB Historian? > If we just provide a solution, or demonstration, then either is ok. > If we want to provide an "one-box thing" (even without GUI), +1 for a > new project. > > > I don’t even think it would be bad if an entity like Timecho would add > > enterprise offerings, because I know, that the industry won’t “buy” > > something, if there’s no commercial support or anyone, they can throw money > > at, even if it’s free (That might even make them more skeptical). > Yes, indeed. :D > > Best, > --- > Xiangdong Huang > > Ben Hutcheson 于2022年11月27日周日 18:38写道： > > > > Hi, > > > > I think it's a great idea. > > > > I'd vote for having a separate project for something like this, just so > > it's clear that it is a historian and people can build it separately. I > > wouldn't want it hidden away in an obscure folder in the PLC4X repo. > > > > Cake does go with Cafe. > > > > Ben > > > > > > On Sun, Nov 27, 2022 at 3:09 AM Christofer Dutz > > wrote: > > > > > Hi all, > > > > > > Trying to respond to all (except the naming question ;-) ): > > > > > > @Ryan: PLC4X Doesn’t have such a queueing, but IoTDB has … so we could be > > > collecting data on one node, writing that to TSFiles using the > > > IoTDB-Client > > > (As Xaingdong mentioned). > > > These could either be online and transfer data to the server right away, > > > or operate in an offline-like mode and periodically fetch data in bursts > > > from the client (Hope that’s correct, please correct me if I’m wrong) > > > > > > @Xaiangdong: In general, PLC4X operates in an active mode, but we also > > > have a proposed and prototypically proven “passive-mode”. Here the > > > software > > > doesn’t actively participate in the data acquisition directly, but simply > > > listens to the data stream and makes data available. We also have > > > something > > > we call a “Data-Diode”, which technically makes interference impossible as > > > it lets ethernet packets flow in one direction, but nothing in the other > > > (Firewalls usually have the problem of letting packets pass in both > > > directions for established connections). We invented this, because we knew > > > we will never have validated and audited open-source software, to a level > >
Re: Building a PLC4X and IoTDB Historian?
If we just provide a solution, or demonstration, then either is ok. If we want to provide an "one-box thing" (even without GUI), +1 for a new project. > I don’t even think it would be bad if an entity like Timecho would add > enterprise offerings, because I know, that the industry won’t “buy” > something, if there’s no commercial support or anyone, they can throw money > at, even if it’s free (That might even make them more skeptical). Yes, indeed. :D Best, ------- Xiangdong Huang Ben Hutcheson 于2022年11月27日周日 18:38写道： > > Hi, > > I think it's a great idea. > > I'd vote for having a separate project for something like this, just so > it's clear that it is a historian and people can build it separately. I > wouldn't want it hidden away in an obscure folder in the PLC4X repo. > > Cake does go with Cafe. > > Ben > > > On Sun, Nov 27, 2022 at 3:09 AM Christofer Dutz > wrote: > > > Hi all, > > > > Trying to respond to all (except the naming question ;-) ): > > > > @Ryan: PLC4X Doesn’t have such a queueing, but IoTDB has … so we could be > > collecting data on one node, writing that to TSFiles using the IoTDB-Client > > (As Xaingdong mentioned). > > These could either be online and transfer data to the server right away, > > or operate in an offline-like mode and periodically fetch data in bursts > > from the client (Hope that’s correct, please correct me if I’m wrong) > > > > @Xaiangdong: In general, PLC4X operates in an active mode, but we also > > have a proposed and prototypically proven “passive-mode”. Here the software > > doesn’t actively participate in the data acquisition directly, but simply > > listens to the data stream and makes data available. We also have something > > we call a “Data-Diode”, which technically makes interference impossible as > > it lets ethernet packets flow in one direction, but nothing in the other > > (Firewalls usually have the problem of letting packets pass in both > > directions for established connections). We invented this, because we knew > > we will never have validated and audited open-source software, to a level > > that it would be certified for some of these use cases. > > > > So, either we can live with everything the SCADA system is already > > requesting, or we add an active PLC4X node in the secure network, that > > requests data, and simply ignores it, and a second – passive mode – node > > sits outside the secure network to capture the information. > > > > I agree that this sort of thing needs to be a “product”. The Automation > > Industry just doesn’t know how to work with frameworks. Ideally a one-box > > thing. > > Right now, most tools I have seen don’t even need the calculation or the > > visualization. This is usually done on another level. Important would be > > that we could be somewhat API compatible with existing products. Them > > usually having SQL or REST APIs, should make it relatively easy to sort of > > produce frontends to our Apache Historian, that are API compatible with > > some existing industry products, so they are replaceable. > > > > If we wanted to add a visualization layer or a data-curation layer later > > on, we should have a chat with the NiFi or StreamPipes folks as that’s what > > they already have. > > > > For now, I would be proposing to build something that uses PLC4X for the > > data-acquisition, IoTDB for the storage and build a REST frontend for this, > > that’s somewhat API compatible with one of the major established products > > and to add more on a step-by-step basis. > > > > I don’t even think it would be bad if an entity like Timecho would add > > enterprise offerings, because I know, that the industry won’t “buy” > > something, if there’s no commercial support or anyone, they can throw money > > at, even if it’s free (That might even make them more skeptical). > > > > > > What do you all think? Does this make sense? If yes, where would it make > > sense to start working on something like this? In the IoTDB project? In the > > PLC4X project, in a separate (new) project? > > > > > > Chris > > > > > > From: Xiangdong Huang > > Date: Sunday, 27. November 2022 at 06:02 > > To: dev@plc4x.apache.org > > Subject: Re: Building a PLC4X and IoTDB Historian? > > Hi all, > > > > It makes sense to use PLC4X+IoTDB to build a historian software. > > Actually, there are several users using IoTDB as their historian > > solution... > > > > According to my knowledge, a historian software contains several
Re: Building a PLC4X and IoTDB Historian?
Hi all, It makes sense to use PLC4X+IoTDB to build a historian software. Actually, there are several users using IoTDB as their historian solution... According to my knowledge, a historian software contains several features: - get data from OPC/modubs server and write to IoTDB * use PLC4x + IoTDB-client. (we call this data collector) - (optional) there is a single-way network gateway for security. * If the gateway is deployed between device and PLC4x program, then we need to check whether plc4x supports that. * If the gateway is deployed between IoTDB-client and IoTDB, then we need to check wheter IoTDB-client supports that. - Calculation Engine, e.g., we want to write C to IoTDB when we collect A and B from a device (for example, C=A+B/2 ) * IoTDB's trigger supports that but we need a Drag-and-drop programming GUI. (maybe integrating some open source projects, like Red-node is a good idea) - get the latest data from IoTDB for visualization (usually users need to draw a process flow diagram, and put the latest data on each device icon on the diagram) * IoTDB supports getting latest data. but we need a new software for drawing the diagram (I do not know if there is any open source project for this. In our real applications, we ususally buy and integrate some other commerical software) - send alert message if the real time data meets some rules * IoTDB trigger supports the rule. but currently we have no a GUI. (IoTDB also supports Prometheus Alert Manager) - get the historical data * IoTDB supports that and grafana is good at visualization - last but not the least, if we provide all the features to industrial users, all the GUIs should be integrated into one entrance. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Ryan Truran 于2022年11月27日周日 08:18写道： > > Hi folks, long time lurker… > > A historian would be great. Does PLC4X queue data on the machine it’s > running on already? > > A common pattern in historians is to queue data on the runtime server until > data can be extracted to a sql server, preventing data loss, and reducing > the need for redundancy. > > There are a ton of edge cases to watch out for which I can elaborate on > further. > > I’m a former Industrial Controls Engineer turned software dev and can help > out where needed. > > -Ryan > > On Sat, Nov 26, 2022 at 10:24 AM Otto Fowler > wrote: > > > Would you name it “Cake”? > > > > From: Christofer Dutz > > > > Reply: dev@plc4x.apache.org > > Date: November 26, 2022 at 10:36:23 > > To: dev@plc4x.apache.org , > > d...@iotdb.apache.org > > Subject: Building a PLC4X and IoTDB Historian? > > > > Hi all, > > > > I am currently thinking, if it wouldn’t be a good idea to build something > > like an open-source Historian based on PLC4X and IoTDB. > > > > For those of you, who don’t know what a Historian is. In the manufacturing > > industry they have these extremely expensive servers (usually you buy them > > as a bundle of hard- and software). > > These servers are nothing else than a really crappy and brutally expensive > > Database for storing Time-Series data. > > > > The thing is most commercial products are currently really having trouble > > to keep up with the increasing amount of Data being sent. > > > > So instead of suggesting building an Historian at each customer’s site, I > > thought: Perhaps a ready-to-use solution based on open-source would be a > > good idea. > > Not 100% sure where I’d locate such an initiative, but I would tend to see > > it more on the Database side. > > > > I think IoTDB would be the perfect storage system, all we seem to need is > > some sort of rest-interface that matches the industry standards for > > querying the information and on the other side something like PLC4X to fill > > the database. > > > > Here some examples: > > > > https://www.ge.com/digital/documentation/historian/version80/c_historian_apis_overview.html > > https://cdn.logic-control.com/docs/aveva/historian/HistorianRetrieval.pdf > > > > What do you folks think? > > > > > > Chris > >
Re: [DISCUSS] Rename Fields -> Tags?
+1 for Tag. Just want to share that I researched many historian systems (include OSIsoft PI, Siemens WinCC, Emerson DeltaV, etc.), all of them are using "Tag". --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Otto Fowler 于2022年11月9日周三 11:41写道： > > +1 > > From: Ben Hutcheson > Reply: dev@plc4x.apache.org > Date: November 8, 2022 at 15:20:51 > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > +1, while I don't have your commitment to go around and change it. I think > it makes it better aligned with OT nomenclature. > > On Tue, Nov 8, 2022 at 2:21 AM Christofer Dutz > wrote: > > > Hmmm … ok, > > > > So, I count two people for using Tag and sort of Two for using Field. > > Am I correct with this? > > > > At least my LinkedIn question seems to be clear that most people would be > > expecting “Tag”. > > And I mean … I think we don’t need to work on having PLC4X accepted on > the > > IT side, but on the OT side. > > Making it more aligned with what the OT folks expect seems to be a better > > path for me. > > > > But I would really appreciate a bit more clear outcome of this > discussion… > > so anyone who’s not posted his opinion yet is highly encouraged to do so. > > > > I’d just hate to rename something like that after a 1.0.0. > > > > Chris > > > > > > > > From: jl hong > > Date: Tuesday, 8. November 2022 at 02:56 > > To: dev@plc4x.apache.org > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > Hello Chris, > > I had the same confusion with Łukasz about what "Tag" meant when I first > > met it in using Rockwell > > PLCs.Maybe it is more difficult to understand than "Field".Also, I think > > "Field" is not accurate enough too. > > Finally, I think either "Tag" or "Field" is acceptable, and people should > > both be able to understand it from the document or context. > > By the way, we call it "Point Position" in Chinese, I translated > directly. > > > > Christofer Dutz 於 2022年11月8日 週二 凌晨4:49寫道： > > > > > Probably should rename „fieldQuery“ to „fieldAddress” (or tagAddress) > as > > I > > > split Fields and Queries as a query usually targets more than one > element > > > and an address normaly doesn’t. > > > > > > Chris > > > > > > From: Christofer Dutz > > > Date: Monday, 7. November 2022 at 21:40 > > > To: dev@plc4x.apache.org > > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > > And regarding your points, Lukasz, > > > > > > The output from the Browse API is that it is a BrowseItem. This > contains > > a > > > Field (or Tag if we rename it) and loads of metadata. > > > Is the Field readable, writable, subscribable, loads of protocol > > dependent > > > options. > > > > > > The Field itself now should be able to produce an address string that > > > should be able to re-produce it. The APIs all support “addFieldQuery” > > which > > > takes this string representation or “addField” which directly receives > > the > > > field object. > > > > > > Chris > > > > > > > > > From: Łukasz Dywicki > > > Date: Monday, 7. November 2022 at 13:48 > > > To: dev@plc4x.apache.org > > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > > Hey Chris, > > > I do not insist on any side. Knowing how hard it is to get a "common > > > understanding" on certain things I think it is easier if we stick with > > > project specific concept. > > > > > > Other point, we do not need to re-use a PlcField and field notion > > > everywhere. For example output from browse api might be a descriptor > > > which can be used to construct a field address. After all, a browsing > > > functionality might provide more information than needed to fetch data > - > > > ie. human readable name, description or other elements which are > > > irrelevant for driver to get data. > > > > > > As a side note, I do acknowledge that best time to do naming and larger > > > API alignments is prior 1.x release. > > > > > > Best, > > > Łukasz > > > > > > On 6.11.2022 13:32, Christofer Dutz wrote: > > > > Hi Lukasz, > > > > > > > > even in protocols like ADS and EIP at Rivian everyone is referr
Re: [PROPOSAL] Implement a Java GUI application for browsing PLCs with PLC4X
+1 for a GUI tool. IMO, the tool should be lightweight. Netbeans is too heavy... （it comes to my experience when I used Netbeans several years ago..). And, using Netbeans, Eclipse, IDEAJ framework may reduce our coding workload, but will raise the skill bar because contributors has to know the framework well. JavaFx is good for me, a Java skill-stack programmer :D. Web based GUI is also a good choice (consider Grafana in time series area). Best, --- Xiangdong Huang School of Software, Tsinghua University Łukasz Dywicki 于2022年6月23日周四 20:59写道： > > I been wrapping head around this as I had a necessity to watch CANopen > traffic decoded by plc4x. I ended up building fairly basic web page > which displayed most recent frames (so I could stay with local socketcan > transport), yet it was far from useful or portable. Recently I also did > struggle a lot with bloody modbus. My usecases are often focused on > making the commissioning to generate further software configuration. > > My little research in topic of desktop applications ended up at javafx > which allows to make it small and compile to native binary thanks to > graal. My experiences with RCP platforms are rather bad (I did some > small Eclipse RCP projects), even if I have no issues with OSGi. Problem > I see in RCP platforms is sparse development documentation, I also > perceive both Eclipse RCP and Netbeans as focused mainly on organizing > navigation while strongly depending on UI frameworks (jface/swt or > swing/awt). Effectively you still need to build tables and so on, but > with much more overhead. > Please do not take above too seriously in context of Netbeans, I don't > know much about it and its flexibility. I don't know how to build it > with Maven, hence it feels strange. > For the Kotlin stuff and frameworks there - I can say that any UI > project which Google is pushing is a red flag to me. Looking at GWT, > Angular 1.x (I used both) I simply fear that they can step back from > "experiment" after a year or two leaving everything to the community. I > looked at kootlin and javafx a while ago and there is not much happening > there. I don't know if is because of maturity, javafx issues or shift to > other UI approaches. > > As I had no time to work on it I just postponed that to a future. Yet, I > still dream from time to time about proper "fieldbus.app". ;-) > > Cheers, > Łukasz > > On 23.06.2022 14:46, Michal Harakal wrote: > > Hi, > > > > I would be also interested in, having a strong opinion on technology stack, > > but fully open to design and function. > > > > My suggestion is writing a Desktop App with Kotlin Jetpack Compose for > > Desktop: > > > > Props: > > * modern, state of the art, way to write reactive UI (natural way to > > implement unidirectional data flows architectures) > > * JVM target > > * open source, backed by Google And Jetbrains (they use it in their > > critical products) > > * Kotlin provides 1A class interoperability support with Java and JVM > > * since Jetpack Compose is originally created and used by Android, you can > > have an Android App out of the box, with little effort > > * integration with Jetbrains Intellij > > * even if you don't know Jetpack Compose Framewrok, you can contribute too > > with your Java/Kotlin skills imedialtely on domain/bussines etc. parts of > > code .. > > * easy to learn > > * with multiplatform support are native apps with their native UI > > frameworks (e.g. iOS) > > > > Cons: > > * Still in Alpha > > * backed by Google and Jetbrains > > * Kotlin is probably not the number one programming language here > > > > > > Best regards, > > Michal > >> Christofer Dutz hat am 23.06.2022 10:55 > >> geschrieben: > >> > >> > >> Hi all, > >> > >> Again, I was in need of a simple application to simply monitor the values > >> on a Modbus device (I’m currently configuring my Wago PFC200 Modbus Slave > >> interface). > >> I could use stuff like the “Modbus Poll” GUI tool, but my trial expired > >> and I’m not willing to pay 130€ for this limited functionality. > >> > >> So, I thought, it would be an awesome addition to PLC4X if we had some > >> sort of GUI application, that uses the Discover functionality to find > >> possible PLCs and list them in a tree view. > >> If the use double clicks on one of these connections, it connects and > >> possibly executes the Browse functionality and lists up what it finds. > >> > >> I know that I could simply start working on something like that, but I > >> thought this would also be a great thing for someone else to implement as > >> it doesn’t require too deep knowledge of PLC4X internals. > >> > >> And I suck at building beautiful UIs :-) > >> > >> Anyone interested? > >> > >> Chris
Re: Update to my role at Apache
Congratulations, Chris. And I also second you keep the VP of plc4x as you really did a lot of effort on it :D Look forward PLC4x and IoT-related project being better and better. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lukas Ott 于2022年3月5日周六 19:28写道： > I do not think it is necessary as it is just the report and is not related > to our decision making process. So i am fine. > > Christofer Dutz schrieb am Sa., 5. März 2022, > 11:42: > > > Hi all, > > > > I am not sure everyone on the project heard it, but last Thursday I was > > elected as one of the members of the Board of Directors of the ASF. > > > > I am more than happy to continue my role as VP of Apache PLC4X (Currently > > it's writing the board report), but I just wanted to hear your opinions. > > I am also happy to step back, if you think this is necessary. > > > > What do you folks think? > > > > Chris > > > > > > >
Re: CANOpen_cant send data to vcan on linux(Ubuntu)
> And I might add, that you should subscribe to the mailinglist, by sending an
> empty email to dev-subscr...@plc4x.apache.org
If so, I think he may do not receive email replies ...
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Christofer Dutz 于2021年11月17日周三 下午8:48写道：
>
> And I might add, that you should subscribe to the mailinglist, by sending an
> empty email to dev-subscr...@plc4x.apache.org
>
> I had to moderate your email manually... If you're subscribed this happens
> automatically.
>
> Chris
>
> Holen Sie sich Outlook für Android<https://aka.ms/AAb9ysg>
>
> From: Łukasz Dywicki
> Sent: Wednesday, November 17, 2021 1:40:33 PM
> To: dev@plc4x.apache.org
> Subject: Re: CANOpen_cant send data to vcan on linux(Ubuntu)
>
> Hey,
> There might be several reasons why you can't see anything on the interface.
>
> 1. Interface is down, make sure you perform both commands:
> sudo ip link add dev vcan1 type vcan
> sudo ip link set up vcan1
> 2. The candump command might not list "loopback" messages, I am not sure of
> that, but you need to verify its options.
> You can also use interface statistics to see if counters go up:
> ip -details -statistics link show vcan1
>
> Let me know if any of above helps. The PDO address you use is valid and
> should trigger message on the bus.
>
> Best,
> Łukasz
>
>
> śr., 17 lis 2021 o 13:26 蒋怀川 napisał(a):
>
> >
> > 中文==
> >
> > 你好，导师，我是一名java程序员，我在使用canopen当中遇到一些相关的疑问。如下面的截图所示，我向vcan发送数据，但是Vcan没有打印出任何提示信息。这种问题我需要如何处理，谢谢。
> >
> >
> >
> > English
> > Hello, tutor, I'm a java developer,I have some questions about using
> > CANopen. As shown in the screenshot below, I sent data to Vcan, but Vcan
> > did not print any prompt information. How do I deal with this problem?
> > Thank you.
> >
> >
> >
> > code==
> >
> >
> >
> > org.apache.plc4x
> > plc4j-driver-canopen
> > 0.8.0
> >
> >
> >
> > ===
> > package com;
> >
> >
> > import org.apache.plc4x.java.api.exceptions.PlcConnectionException;
> > import org.apache.plc4x.java.api.messages.PlcWriteRequest;
> > import org.apache.plc4x.java.api.messages.PlcWriteResponse;
> > import org.apache.plc4x.java.canopen.CANOpenPlcDriver;
> > import org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection;
> >
> >
> > import java.util.concurrent.CompletableFuture;
> > import java.util.concurrent.ExecutionException;
> >
> >
> > public class CANOpenVcanDemo {
> > public static void main(String[] args)
> > throws PlcConnectionException, ExecutionException,
> > InterruptedException {
> > String canInterface = "vcan1";
> > String connectionString =
> > String.format("canopen:socketcan://%s?nodeId=11",
> > canInterface);
> > DefaultNettyPlcConnection plcConnection =
> > (DefaultNettyPlcConnection) new
> > CANOpenPlcDriver().getConnection(connectionString);
> > plcConnection.connect();
> > if (plcConnection.isConnected()){
> > System.out.println("Connected");
> > }else {
> > System.out.println("not Connected");
> > return;
> > }
> > if (plcConnection.getMetadata().canWrite()) {
> > PlcWriteRequest.Builder builder =
> > plcConnection.writeRequestBuilder();
> > //String address = "SDO:11:0x1600/0x01:INTEGER64";
> > String address = "RECEIVE_PDO_1:11:INTEGER64";
> > //CANOpenDataType
> > builder.addItem("rpdo_0x200", address,123);
> > PlcWriteRequest plcWriteRequest = builder.build();
> > CompletableFuture completableFuture =
> > (CompletableFuture)
> > plcWriteRequest.execute();
> > System.out.println("===>flag");
> > PlcWriteResponse plcWriteResponse = completableFuture.get();
> >
> > System.out.println(plcWriteResponse.getResponseCode("rpdo_0x200"));
> > }
> > }
> > }
> >
> >
> >
> >
> >
> >
> >
> >
Re: [VOTE] Apache PLC4X Build-Tools Site-Skin 1.1.0 RC1
Hi, +1 non-binding I checked: - mvn package Minor issue: I find a strange thing... After downloading the release source file [1], and unzip the file on MacOS, I find all files's creation time is 1979-11-30... It is not a big issue (or it can not be called as an issue), but not very friendly... [1] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/plc4x-site-skin/1.1.0/rc1/rc1/apache-plc4x-site-skin-1.1.0-source-release.zip Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lukas Ott 于2021年9月9日周四 下午3:18写道： > > +1 (binding) > > Actions performed: > Downloaded all staged artifacts under the url specified in the release vote > email into a directory we’ll now call download-dir. > Verified the signature is correct > gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) < > cd...@apache.org>" > Verified the SHA512 hashes > Verified the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in > the extracted source bundle. > Verified the content of LICENSE, NOTICE, README, RELEASE_NOTES files in > the extracted source bundle. > Run RAT externally with no surprises > Successfully built with Ubuntu 20.04 and > openjdk 11.0.11 2021-04-20 > OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04) > > Am Mi., 8. Sept. 2021 um 20:41 Uhr schrieb Christofer Dutz < > christofer.d...@c-ware.de>: > > > Apache PLC4X Build-Tools Site-Skink 1.1.0 has been staged under [2] > > and it's time to vote on accepting it for release. > > > > All Maven artifacts are available under [1]. Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > > are required to pass. > > > > Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git > > Release tag: site-skin/v1.1.0 > > Hash for the release tag: be516d634bcff0c09c714e948fd5958915f47771 > > > > Per [3] "Before voting +1 PMC members are required to download > > the signed source code package, compile it as provided, and test > > the resulting executable on their own platform, along with also > > verifying that the package meets the requirements of the ASF policy > > on releases." > > > > You can achieve the above by following [4]. > > > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM > > items in [4]) > > [ ] -1 reject (explanation required) > > > > > > [1] https://repository.apache.org/content/repositories/orgapacheplc4x-1035 > > [2] > > https://dist.apache.org/repos/dist/dev/plc4x/build-tools/plc4x-site-skin/1.1.0/rc1/ > > [3] https://www.apache.org/dev/release/validation.html#approving-a-release > > [4] https://plc4x.apache.org/developers/release/validation.html > >
Re: [DISCUSS] Change the naming scheme for release-tags?
+1.
Also will call a discussion on the IoTDB mail-list to keep consistent :D
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
Otto Fowler 于2021年1月21日周四 下午8:29写道：
> Sounds fine to me.
> +1
>
> > On Jan 21, 2021, at 05:26, Christofer Dutz
> wrote:
> >
> > Hi all,
> >
> > a little discussion on the IoTDB list made me realize that I never
> actually discussed this here and I'd like to do it before we start the next
> release.
> >
> > This will be the first containing Go content. Go resolves dependencies
> quite differently as it doesn't ship binaries, but you instead reference
> Git repositories (GitHub is actually best integrated type). You reference a
> version of a Go library via git tags. So if you want a version 1.2.3, you
> actually reference a tag named "v1.2.3". I have seen that if you don't
> stick to that some tools and utils might have problems.
> >
> > So I would like to ask you, if you would agree that we change the
> release-tag naming scheme from "releases/{full-version}" to
> "v{full-version}" ... it doesn't have any side-effects to any other tools.
> And it would eliminate the little discrepancy in the naming "release"
> branch, but "releases/" as prefix for tags (because if there's a branch
> called "release" we can't prefix a tag with "release/".
> >
> > So what do you think?
> >
> > Chris
> >
>
>
Re: Some issues in the website's example
Hi Ben, Thanks for your kindly and quickly reply. One more question, I am using Prosys OPC UA Simulation Server, and the NodeId is: ns=3;i=1002, NodeClass is Variable, DataType is Double. So, how to define the field address in PLC4x? I checked [1], the example is: DOUBLE_IDENTIFIER = " ns=2;s=HelloWorld/ScalarTypes/Double"; What is the meaning of "HelloWorld/ScalarTypes", or, where I can confirm how to get the needed info of DOUBLE_IDENTIFIER from Prosys OPC UA Simulation Server? [1] https://github.com/apache/plc4x/blob/develop/plc4j/drivers/opcua/src/test/java/org/apache/plc4x/java/opcua/ManualPLC4XOpcua.java Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Ben Hutcheson 于2020年12月18日周五 上午8:41写道： > Hi Xiangdong, > > Yes you are right, the example in the opc ua section doesn't look right. I > can take a look at updating it tomorrow. > > Your best bet would be to follow the getting started - java section. > https://plc4x.apache.org/users/getting-started/plc4j.html > > the connection string format for the opc ua driver is > > opcua:tcp://127.0.0.1:12686/milo?discovery=false > > (Discovery option being optional.) > > Also if you are comfortable the 0.8.0-SNAPSHOT is more stable. > > You'll have to add the repository to your pom.xml file though. > > > > > > apache.snapshots > > Apache Snapshot Repository > > https://repository.apache.org/snapshots > > > > false > > > > > > > > > > Specifically with the OPC UA driver we are in the process of merging an > update to the 0.8.0-SNAPSHOT to support specifying the data type in the > address field. > > The current address format is:- > > ns=2;s=HelloWorld/ScalarTypes/Boolean > > This will change to:- > > ns=2;s=HelloWorld/ScalarTypes/Boolean:BOOL > > With the update, however the :BOOL datatype will be optional, unless > you need to read/write unsigned values. > > If you have any more questions let us know. > > Kind Regards, > > Ben > > > On Thu, Dec 17, 2020 at 6:59 PM Xiangdong Huang > wrote: > > > Hi, > > > > Today I followed the User guide on the website to run PlC4x to collect > > data, and then find an issue of the example [1]. > > > > In the reading data example, the example creates an opcuaReadConnection, > > and then uses opcuaConnection. What is worse, opcuaConnection has no > such a > > read() method but the example calls it.. (version 0.7.0) > > > > I think the API may change but the document did not keep to update. > > > > [1] https://plc4x.apache.org/users/protocols/opc-ua.html > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > >
Some issues in the website's example
Hi, Today I followed the User guide on the website to run PlC4x to collect data, and then find an issue of the example [1]. In the reading data example, the example creates an opcuaReadConnection, and then uses opcuaConnection. What is worse, opcuaConnection has no such a read() method but the example calls it.. (version 0.7.0) I think the API may change but the document did not keep to update. [1] https://plc4x.apache.org/users/protocols/opc-ua.html Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [DISCUSS] Changing Schema for Kafka Source Connector
Hi,
Though I am not from Kafka project, maybe I can join the discussion
as I have some experiences and usually we (mean, the database) consumes
data from Kafka.
I am reading the current Kafka adapter's implementation,
and will be back soon :D
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Christofer Dutz 于2020年11月8日周日 上午5:26写道：
> Hi Ben,
>
> I have to admit that even if I created most of the connector, I have
> almost no experience with Kafka.
> I don't even understand the schema topic ;-)
>
> But it does make sense from your email and I can imagine that the current
> way it's implemented could be an issue.
> I have no objections to changing this.
>
> Perhaps it would be cool to involve some people from the Kafka project?
> Perhaps callout on the i...@apache.org mailing-list too? (I'd probably do
> both, if I were you)
>
> Chris
>
>
>
> Am 07.11.20, 14:31 schrieb "Otto Fowler" :
>
> Is it a breaking change? Is anyone using it?
> I would be fine with changing it, but we would need to be clear on
> those
> things.
> Also, I think the names should reflect what the project uses,
>
> plcfields not fields etc
>
> From: Ben Hutcheson
> Reply: dev@plc4x.apache.org <
> dev@plc4x.apache.org>
> Date: November 7, 2020 at 06:10:42
> To: dev@plc4x.apache.org
> Subject: [DISCUSS] Changing Schema for Kafka Source Connector
>
> Hi,
>
> Putting together a doc for the schema for the source connector for
> Kafka it
> appears that the existing schema is something like this:-
>
> {
> "type": "record",
> "name": "source-connector",
> "namespace": "com.apache.plc4x.kafka.config",
> "fields": [
> {
> "name": "running",
> "type": "int16"
> },
> {
> "name": "conveyorLeft",
> "type": "int16"
> },
>
> ]
> }
>
> In which the schema needs to be modified depending on what tags are
> being
> collected.
>
> If we change it so that the tags are included in an array of name/value
> pairs then we wouldn't have to modify the schema when tags are
> added/deleted. The new schema would be something like this.
>
> {
> "type": "record",
> "name": "source-connector",
> "namespace": "com.apache.plc4x.kafka.config",
> "fields": [
> {
> "name": "tag",
> "type":{
> "type": "array",
> "items":{
> "name":"tag",
> "type":"record",
> "fields":[
> {"name":"name", "type":"string"},
> {"name":"value", "type":"string"} <- With this
> eventually being a union of different types.
> ]
> }
> }
> }
> {
> "name": "timestamp",
> "type": "string"
> }
> ]
> }
>
> What are your thoughts on changing this? It would allow us not to have
> to
> send the schema within each packet.
>
> It does increase the packet size for the specific case that the tags
> will
> never change and the schema isn't being included in each packet, but I
> think this would be few and far between.
>
> Ben
>
>
Re: Build Server changed ... working on it ...
Hi Chris, > I’ll keep on working on setting up everything on the new CI system Thanks for notifying us. Could you briefly guide us on what may need to be set? Best, --- Xiangdong Huang School of Software, Tsinghua University Christofer Dutz 于2020年7月27日周一 上午3:55写道： > Hi folks, > > so today I managed to get the configuration on the new CI server running > and I think we're back in business. > > Chris > > Am 25.07.20, 15:25 schrieb "Christofer Dutz" : > > Hi all, > > I just noticed, that infra moved our build agent from the old > build.apache.org to the new ci-build.apache.org … so we will never be > able to build on the old server again (Just before reaching build 1000 ☹ ) > … just wanted to tell you about this. > > I’ll keep on working on setting up everything on the new CI system … > but for now it might be, that we won’t have SNAPSHOTs for a few days. > > Chris > > >
Have to run `mvn package` before running example codes in the repo
Hi, I just checkout to the develop branch and want to run the project in IDEA. However, the IDEA says, class not found Class: RequirePcap Location: org.apache.plc4x.java.utils.rawsockets.netty.RawSocketChannelTest Actually, I can indeed find the RequirePcap source code from the repo. I tried to run `mvn generate-sources` but it does not work. Then I tried to run `mvn package -DskipTests`. Fortunately, it works. After running the command, I can execute example codes in IDEA. My question is, can we avoid to let new developers/users run the command? (or leave the tips in a conspicuous place). Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (PLC4X-216) Upgrade PLC4x-IoTDB example and supply the document
Xiangdong Huang created PLC4X-216: - Summary: Upgrade PLC4x-IoTDB example and supply the document Key: PLC4X-216 URL: https://issues.apache.org/jira/browse/PLC4X-216 Project: Apache PLC4X Issue Type: Task Reporter: Xiangdong Huang IoTDB v0.10.0 has released and we recommend using session API for fast data ingestion. Besides, the doc about iotdb-integration is empty now. Will fix the above two tasks in this issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [WEBINAR] "Hands On": Reading Siemens S7 with PLC4X
Hi, It is OK for me. Many thanks. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2020年4月7日周二 下午5:34写道： > Hi, > > here is now the registration Link: > https://my.demio.com/ref/dpA7kBrZC5CBONv7 > > Best > Julian > > Am 07.04.20, 10:48 schrieb "Julian Feinauer" < > j.feina...@pragmaticminds.de>: > > Hey, > > its planned for one hour (or 1 and half). > Would this be fine or too late? > > J > > Am 07.04.20, 10:39 schrieb "Xiangdong Huang" : > > Hi Julian, > > How long the webinar will last? > If it is less than one and a half hours, it is fine. > 17 CEST is 11 PM in China... > (However, I have a ALC Beijing online meeting at 10 PM) > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer 于2020年4月7日周二 > 下午4:24写道： > > > Hi folks, > > > > as promised we will do an english version of our webinar about > “getting > > started” with PLC4X. > > I suggest Thursday 9th of April at 17 CEST. > > Would this fit for everybody or are there people in time zones > that would > > like to attend but do not have time? > > > > Best > > Julian > > > > > > >
Re: [WEBINAR] "Hands On": Reading Siemens S7 with PLC4X
Hi Julian, How long the webinar will last? If it is less than one and a half hours, it is fine. 17 CEST is 11 PM in China... (However, I have a ALC Beijing online meeting at 10 PM) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2020年4月7日周二 下午4:24写道： > Hi folks, > > as promised we will do an english version of our webinar about “getting > started” with PLC4X. > I suggest Thursday 9th of April at 17 CEST. > Would this fit for everybody or are there people in time zones that would > like to attend but do not have time? > > Best > Julian >
Re: [GERMAN] PLC4X Webinar
Hi Julian, Typing manually is impossible... Some platforms can generate subtitles automatically, like Youtube, or the App (I forget the name) that used in ACEU19. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2020年3月31日周二 下午8:02写道： > Hi Xiangdong, > > rather English Webinar (perhaps we have tot hink about timezones). > English subtitle on live video will be tough... don’t know if anybody here > can type that fast : D > > J > > Am 31.03.20, 13:47 schrieb "Xiangdong Huang" : > > Hi Julian, > > English +1. Or, if there is English subtitle on live... > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > mehedi hasan 于2020年3月31日周二 下午6:27写道： > > > Hi Julian, > > Thanks for the email. > > > > It would be really nice to have it in English, would help me to > learn about > > it. > > > > Thanks in advance. > > > > Best Regards > > Mehedi > > > > > > > > > > On Tue, Mar 31, 2020 at 12:20 PM Julian Feinauer < > > j.feina...@pragmaticminds.de> wrote: > > > > > Hi folks, > > > > > > just as notice. > > > Tomorrow we will host an (introductionary) Webinar on PLC4X with a > > > complete end-to-end example on connecting to Siemens S7. > > > The Webinar is in german, but I, nonetheless wanted to share it > here for > > > interested People. > > > > > > If you are interested, see the full announce below: > > > > > > In unserem ersten (technischen) Webinar, am 01. April um 14 Uhr, > werden > > > wir Dir kurz das Projekt Apache PLC4X vorstellen und auch gegen > OPC UA > > > abgrenzen. Dann gehen wir in die Praxis über und zeigen Dir, wie > man > > > mittelsPLC4X< > > > > > > https://pragmaticindustries.com/?nltr=NzsxO2h0dHBzOi8vcHJhZ21hdGljaW5kdXN0cmllcy5jb20vZXhwZXJ0aXNlL3BsYzR4Lzs7YWFkNGY1ZmEyNWJiNGIyOWQ5M2I0ZGU1ZDQ5ZTI1NWE%3D > > > > > > aus Java auf eine Siemens S7 Steuerung zugreifen und diese > auslesen kann. > > > > > > Registration Link is here: > https://my.demio.com/ref/ypg5cluxPecOLWcx > > > > > > If we find enough people being interested in an english version, I > > promise > > > we will do one, then please reply here : ) > > > > > > Best > > > Julian > > > > > > > >
Re: [GERMAN] PLC4X Webinar
Hi Julian, English +1. Or, if there is English subtitle on live... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 mehedi hasan 于2020年3月31日周二 下午6:27写道： > Hi Julian, > Thanks for the email. > > It would be really nice to have it in English, would help me to learn about > it. > > Thanks in advance. > > Best Regards > Mehedi > > > > > On Tue, Mar 31, 2020 at 12:20 PM Julian Feinauer < > j.feina...@pragmaticminds.de> wrote: > > > Hi folks, > > > > just as notice. > > Tomorrow we will host an (introductionary) Webinar on PLC4X with a > > complete end-to-end example on connecting to Siemens S7. > > The Webinar is in german, but I, nonetheless wanted to share it here for > > interested People. > > > > If you are interested, see the full announce below: > > > > In unserem ersten (technischen) Webinar, am 01. April um 14 Uhr, werden > > wir Dir kurz das Projekt Apache PLC4X vorstellen und auch gegen OPC UA > > abgrenzen. Dann gehen wir in die Praxis über und zeigen Dir, wie man > > mittelsPLC4X< > > > https://pragmaticindustries.com/?nltr=NzsxO2h0dHBzOi8vcHJhZ21hdGljaW5kdXN0cmllcy5jb20vZXhwZXJ0aXNlL3BsYzR4Lzs7YWFkNGY1ZmEyNWJiNGIyOWQ5M2I0ZGU1ZDQ5ZTI1NWE%3D > > > > aus Java auf eine Siemens S7 Steuerung zugreifen und diese auslesen kann. > > > > Registration Link is here: https://my.demio.com/ref/ypg5cluxPecOLWcx > > > > If we find enough people being interested in an english version, I > promise > > we will do one, then please reply here : ) > > > > Best > > Julian > > >
Something need to be written in the webpage of integration?
Hi, I come from IoTDB (incubating) community and I wonder I just subscribed to this mailing list one minute ago (I thought I have subscribed to this mailing list long long ago...) Chris told me there is an example of integration PLC4j with IoTDB Cheers! I'd like to volunteer to maintain the module if IoTDB upgrades version and change APIs. Besides, I notice that [1] is empty. What does this page want to show? Just the introduction of IoTDB in one sentence? Or readme of IoTDB integration? [1] https://plc4x.apache.org/users/integrations/apache-iotdb.html Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (PLC4X-146) Problem when using examples/hello-integration-edgent with plc-simulator
Xiangdong Huang created PLC4X-146: - Summary: Problem when using examples/hello-integration-edgent with plc-simulator Key: PLC4X-146 URL: https://issues.apache.org/jira/browse/PLC4X-146 Project: Apache PLC4X Issue Type: Bug Components: Integration-Edgent Affects Versions: 0.6.0 Reporter: Xiangdong Huang Hi, I am trying to use PLC4x (PLC4J actually) and find some errors: # When I used `HelloPlc4x`, the clioption was: --connection-string test://127.0.0.1 --field-addresses RANDOM/foo:BYTE OK it works! 2. Then I tried org.apache.plc4x.java.examples.integration.edgent.PlcLogger, and the cliOption was: --connection-string test://127.0.0.1 --field-address RANDOM/foo:BYTE --polling-interval 1000, then error occurs: 11:14:25.568 [pool-1-thread-1-489175fe-87ea-41a2-87c2-35b62b8ac594] ERROR o.a.p.edgent.PlcConnectionAdapter - reading from plc device test://127.0.0.1 null failed11:14:25.568 [pool-1-thread-1-489175fe-87ea-41a2-87c2-35b62b8ac594] ERROR o.a.p.edgent.PlcConnectionAdapter - reading from plc device test://127.0.0.1 null failedorg.apache.plc4x.java.api.exceptions.PlcIncompatibleDatatypeException: Incompatible Datatype java.lang.Byte at index 0 at org.apache.plc4x.java.base.messages.items.BaseDefaultFieldItem.getByte(BaseDefaultFieldItem.java:59) at org.apache.plc4x.java.base.messages.DefaultPlcReadResponse.getByte(DefaultPlcReadResponse.java:158) at org.apache.plc4x.java.base.messages.DefaultPlcReadResponse.getByte(DefaultPlcReadResponse.java:152) at org.apache.plc4x.edgent.PlcConnectionAdapter$MySupplier.get(PlcConnectionAdapter.java:175) at org.apache.edgent.function.Functions$ThreadSafeSupplier.get(Functions.java:165) at org.apache.edgent.oplet.functional.SupplierPeriodicSource.fetchTuples(SupplierPeriodicSource.java:50) at org.apache.edgent.oplet.core.PeriodicSource.run(PeriodicSource.java:81) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at org.apache.edgent.runtime.etiao.TrackingScheduledExecutor$TrackedFuture.run(TrackingScheduledExecutor.java:226) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.edgent.runtime.etiao.ThreadFactoryTracker$2.run(ThreadFactoryTracker.java:87) at java.lang.Thread.run(Thread.java:748) I tried some other data type like INTEGER, and got the same error. Is there something wrong? -- This message was sent by Atlassian Jira (v8.3.4#803005)
