• Posts 86
  • Reputation 0
  • Member Since
  • Last Active
    This user has not added any photos yet.
All Posts Topics Started Likes
Hi everybody. I wish everybody to be well in 2018. It is so quite here. Nothing is moving? 
@HKTarzan do you make any progress on testing the input module? Do we have any progress on output modules? Do not forget to export in pdf so everyone can read.
I know you may be byzy with other things but I just asking.
0 0
OK @LeissKG I see your point. It looks fine what you are proposing but let see what others have to say.
0 0
@LeissKG are you suggesting to alter the RC circuit for IO_3, IO_4 input? (C23, R20 and C26, R23). If a user like to tinker with this to have immunity to glitches and use the input card (IO_3, IO_4 as counter inputs) it is up to him. I do not see the problem on that. Or you can do some kind of software low pass filter to that inputs.
About the output module and PWM @HKTarzan is working on that in various output configurations (Low Side switching, High Side switching, Totem Pole, Motor drive etc...may be PWM) So PWM card will be another module. Not everything in the same module.
That was the idea. Many output configurations in different modules. As in "real" PLCs.
We are waiting @HKTarzan to present his ideas. Lets give him some time to see his "magic".
I think I answer to your thinking (or not?)
0 0
HKTarzan wrote:
For the record, here is the latest schematics in PDF format after the drawing restructuring

I like this modular approach. Do you have output module in PDF? (or I miss it somewhere). Thanks
0 0
@Geato very nice scanner. I had it in my Modbus directory since 2015 but forgotten. Time to wake up. Thanks
@LeissKG I will prepare an answer to you counter question in due time.
P6 is used in the addressing function, P7 is status. Counter module must designed very carefully and is a different module. I think if we need encoder input or even counter we must go for hardware solution. The chip is not very expensive. You can do it with software with interrupt inputs for A an B channels  (I did it with Arduino Due) but you need fast CPU (for fast counting).
Is what asking about? Are you referring to the input module or to a different specific module for counter?
Or I may miss something in your question. 
0 0
I totally agree with @LeissKG. In every word. Raspberry is very popular device. It is beyound imagination what momentum can give the NEO OPENPLC project.
@Theogoralves you said:
"If I make OpenPLC-Zero expansible as well, there will be no difference between the two, apart from the fact that one will be driven by a RPi Zero module, and the other will be driven by an H3 quad-core CPU. OpenPLC-Zero is supposed to be a cheap, entry point device"
So what? We are building the first one (zero) easily and inexpensive (in human resources, time  and money) fully attached to our PLCNEO bus, in DINrail, in the same box, the community will start doing projects (a lot!) and on top of that we are building the NEO CPU. Take ABB for instance. They have many CPUS
If you are wiling not to follow that direction (Raspberry zero 485 interface with our I/O bus) I think that I have little to offer in that discussion.
Do not see Raspberry zero as a "competitor" to your NEO CPU. Think that the first will make the world to know the second.
You have a grate mind and you accomplished beautiful things with your OPENPLC issue.
Follow the road to success. That is the power of people in open community. And we people love and trust the Raspberry thing to connect with NEO I/O modules
0 0
485 chip will enable us to plug the module directly on I/O modules. If you do not want to be on same type of our I/O box we can make it flat dinrail mounted and plug it into  OPENPLC I/O modules. On top of what is your plan it will be nice addition to have.
0 0
@thiagoralves are you thinking of using this Ethernet module or to use the ENC28J60 chip and build the Ethernet interface.
I think that will be better. we will have more room to go around and fit analog in / out on board + 485 chip. 
Nice idea to provide an image with everything ready out of the box.
0 0
@thiagoralves what can I say. You just read my mind. I support all the way your idea (doing the Raspberry "abra katabra" module). @LeissKG we talk there your ideas.
My first thought was to use this cheep zero thing (I have all three versions of Raspberry but not the zero).
But then I realize this board has no Ethernet. I did know that it will be that easy to embed.
So I will try to contribute as I can to that.
And of course this is not our final board. Just to shake things out.
I was using Arduino Modbus library with the CODESYS environment. The example that comes with Raspbery + CODESYS + Arduino + Modbus. Working like a charm. It will do for the compination Raspberry + OPENPLC + ARDUINO + Modbus as well

@thiagoralves to be honest I never had the time to work with OPENPLC but now is the time. I will start porting OPENPLC + Modbus to my Raspberry.
Do you propose reading from the site or you have any document to make "easy start "? I think the editor is from PLCOPEN (the same CODESYS is using) 

Also I want to consider something very important for our final CPU board (when time comes).
One feature good to have is two Ethernet ports. The easier solution having these connected as a switch. Not separate IPs
Think this possibility in communication.
we can have distance CPUs connected "daisy chain" using Modbus TCP/IP.
So we can use many number of nodes from a few meters to 100 meters apart. 
Of course we can use an external switch for that but is not so clever and processional idea in distributed I/O.
Most PLCs now have 2 ports switch as common feature.
Can at least consider that?
0 0
Geato wrote:
@thiagoralves - just running out the door but here is your USB to 485 adapter: https://www.digikey.com/products/en?keywords=768-1041-ND%20

Yes but I can propose this:

I used them in our factory for frequency inverters (drives) programming. Working very well. 1 Euro each!
0 0
@Geato please delete your answer "@vorrias - The files you are trying to look at are....." I deleted my question.
Not the answer to the CPU matter. So no question no answer. There is a simple explanation on that. If you want only call me in skype to explain (vorrias_home) . Thanks
@Geato as for Raspberry you may have right, but I am not saying to invest anything on that solution. Just s simple interface. Raspberry platform anyway is a device that @thiagoralves suggest to run OPENPLC.
I am not saying to STOP CPU NEO. It is a grate idea. Just a simple solution for us to start testing the cards and for anybody wants ta play with our I/O modules until our CPU is ready.
@LeissKG I am looking your answer to understant it and I will be back.
0 0
@Thiagolalves since we are waiting to see what @HKTarzan has done with the output modules unofficially since the discussion for CPU module not started yet, I am thinking on top of the CPU we are going to build (and that will take some time) it will be easier to build first a "mother board" or a "HAT" for the raspberry board, so to plug this into our NEO I/O bus system. That will be an inexpensive board with a RS485 chip (may or may not contain an analog out /analog in SPI chip that raspberry do not have) so everybody in the community will embrace our I/O designs out of the box.
I think it is a simple and inexpensive idea that Raspberry community will love it and probably may help us along the way of building more I/O modules.
I really like to see some reaction on that from people in this discussion. Specialy from @Tiagolalves who is initiated this thread.
0 0
thiagoralves wrote:
@HKTarzan, I added you to our github repository: http://www.github.com/thiagoralves/OpenPLC-Neo.

Hi everyone. @thiagoaralves I think you must edit the link. The dot is not needed. this is the correct :

Then I will delete these lines. Thanks

I think @HKTarzan waits to build the input first and then to upload but I thin it is better to upload the  modules anyway (with  version V1.0 ) and then to proceed with corrections along with some readme notes.
So users can see that the project is alive to see the status of the project and they can joined in.
@HKTarzan do we have any news about the Output modules?
0 0
@HKTarzan isolation is a good practice. I think it is a "must to have" except in case that has problems in high speed switching in IGBT circuits. The cost is negligible. Only space  matters.
Aa..and I think we must make with this lot and a relay output as well. @Geato is expert in PLC relays as we see.
It is good to send for production and relay out as well (for AC loads or high amperage applications).
0 0
@HKTarzan looks good and I like this "spliting into blocks" idea. Makes life easier.
Now I see you put a driver for the MOSFET. I thing that will help us when making High Side switching using an P MOSFET (or using same N MOSFET and just connecting the load to Source pin of the MOSFET? )
Datasheet dictates 10V between Gate - Drain for N MOSFET to have RDS(on) 0.07 OHM.
0 0
count post selected

Add a Website Forum to your website.