RS-232 Component Macro & Parity Bits

[Ron]

Hello,

I was wondering if parity checking is supported by the RS-232 Macro.

If Yes, how do I set even or Odd?

Thanks

Ron

[Benj]

Hello Ron

Currently parity checking is not part of the RS232 component.

This may be a possible future addon to the RS232 component though as it would prove useful to verify the integrity of the data being sent and received.

[Ron]

Hi,

How about parity and/or MODBUS error checking routine built in to the RS232 macro. If we have a PIC with more memory for it, this would be the best, without going crazy..

It would be nice to be able to view a list of what features are being added to future releases of V3 and V4. I have made a few suggestions, some of which I am sure you guys got a laugh out of, but several were possible from the sounds of it.

1) Being able to lock a macro that I write, so someone else can use it, but not break it.

2) embedding linker, clock speed, and config bits in source code so when I open the file I do not have to make sure everything is set up the way I need it. allow each to be independent of the others. If I want linker params & clock speed, but not config bits allow it. Mix and Match to the programmers needs.

3) error checking in RS232 macro - parity and even better of you guys include Modbus as an option.

4) A true switch de-bounce macro - at least in the way we think about them in the PLC/Machine Tool world here in North America. This is a macro I would love to write, and lock, and let everyone else use. See number 1 above.

There was one or two others that I had mentioned to Steve via posts and email that he had commented might be possible. A list to see what is coming would be nice. If a suggestion does not make the list, then we know not to dream about having it someday.


Thank you,

Ron

[Benj]

Hello Ron

Steve is away at the moment but he may be able to give you a definative answer next week.

I like your idea for locking macros, That would prove to be most useful.

I will make sure that Steve sees your input anyway.

Thanks again.

[Steve]

Thanks for the suggestions, Ron. Here are some comments...

1) Being able to lock a macro that I write, so someone else can use it, but not break it.

Yes - I like this idea. I will try to implement this in v4.

2) embedding linker, clock speed, and config bits in source code so when I open the file I do not have to make sure everything is set up the way I need it. allow each to be independent of the others. If I want linker params & clock speed, but not config bits allow it. Mix and Match to the programmers needs.

At the moment, you can customise the FCD files to do this sort of thing. Perhaps we need to document things better?

3) error checking in RS232 macro - parity and even better of you guys include Modbus as an option.

This is a possibility.

4) A true switch de-bounce macro - at least in the way we think about them in the PLC/Machine Tool world here in North America. This is a macro I would love to write, and lock, and let everyone else use. See number 1 above.

I agree, the debouncing of the switch is not too good within Flowcode at the moment. Most people use the "input" icon to detect switch transitions - would you be able to provide an example of proper switch debouncing using the input icon? I'm sure a lot of our customers would like to see a proper implementation.