Hello team,
I would greatly appreciate it if RFID devices attached to a GTW could be configured with a custom name, similar to how serial ports can be named.
Currently, we have production lines with multiple gateways connected to Tulip stations, and each Tulip application needs to be configured to point to specific gateways.
Because of this, we are forced to either create a separate step for each production line or develop a separate application for each one, all pointing to specific gateways.
With this suggested improvement, we could have a single application and use the assigned name to filter the data, significantly reducing complexity.
At the moment, maintaining these applications is time-consuming and costly for us. This change would greatly improve scalability and simplify maintenance.
@nawaz-anwarudeen do you know if some other customers have a similar request? as @ChirristopherOficial mentioned, this is a huge improvement for making more efficient our apps.
Hi Edgar - I will inquire and get back.
@ChirristopherOficial and @emendoza,
I’d like to understand a bit more about the use case. If you have multiple gateways at each station, how do you determine which one that you need information from?
Sincerely,
Jake
@jakerigos Right now, we point the trigger to the gateway’s name instead of using “This Station.” ( the gateway name is hard-coded). With this logic, each production line has its own application or step, and when we need to update the process, we have to perform the same changes for each app (production line) and then publish the changes.
With this product suggestion, we would use “This Station” for the triggers and just filter by the RFID name. If a gateway is replaced, we would only need to rename the RFID on the gateway, without updating and publishing any app.
Does that make sense to you?
Hi @ChirristopherOficial,
I think so.
Just to clarify, you have a setup like this:
- RFID 1 → Gateway 1 → Station 1
- RFID 2 → Gateway 2 → Station 1
- RFID 3 → Gateway 3 → Station 1
Ideally, you want to have separate logic for each RFID based on the gateway. You also want a more dynamic way to call out each gateway at each station. For example “When device [Barcode Scanner] outputs at [specific station] [MyStationVariable]” instead of “[specific station] [Station X]“. Then you would have a table mapping edge devices to stations to look up assignments.
Also, are you using the barcode scanner driver for this?
Sincerely,
Jake
Hi Jake,
yes something more flexible but we are using RFID readers instead of barcode scanners
current state, we have 7 production lines, and we have 7 apps doing the same the only thing different between them are the triggers pointing to different GTW ( because we need to know from what RFID the data is coming from)
so i was thinking that if we handle the RFID as we handle the RS232 ( data , and name ) we could use the same trigger for all the station and by using the device output name we could know from where the data is coming
something like this ( I’m terrible at drawing )
so triggers for the app will be more simple and flexible something like this (IMG edited not real) :
and if we change the GTW for a new one we just have to set the same name for the RFID on the new GTW.
and RFID configuration on GTW will looks like this:
(IMG edited not real)
this is the feature request we are very interested to have
@benjamin.hueske
