Hi
Dug out an old project that uses EB1 hardware and worked fine, programmer and EB083 combo board. In the chart I enter a loop and wait until the button on Port A/2 is pressed. All good.
In v10 the component macro associated with reading EB083 Port A appears to have a bug. It doesn't detect the buttons being pressed. If I add in a button component allocated to the same pin (A/2) it works fine when the EB083 button is pressed.
Port B has the display and it's fine.
Regards
EB083 Port A
-
- Valued Contributor
- Posts: 1183
- http://meble-kuchenne.info.pl
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 289 times
- Been thanked: 417 times
-
- Matrix Staff
- Posts: 1464
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 514 times
- Been thanked: 474 times
Re: EB083 Port A
Hi Iain.
Thank you for the report.
Would you like to try the attached component?
If it works for your project then it will be added to the component database.
Thank you for the report.
Would you like to try the attached component?
If it works for your project then it will be added to the component database.
- Attachments
-
- ComboBoard.fcpx
- (10.94 KiB) Downloaded 37 times
Martin
-
- Valued Contributor
- Posts: 1183
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 289 times
- Been thanked: 417 times
Re: EB083 Port A
Hi Martin
I put the file in Programdata/MatrixTSL/Flowcodev10/Components.
Compiles OK but I still cant read from PortA (bank 0) using GetSwitchState
If I use the GetPort command I can detect button press.
Regards
I put the file in Programdata/MatrixTSL/Flowcodev10/Components.
Compiles OK but I still cant read from PortA (bank 0) using GetSwitchState
If I use the GetPort command I can detect button press.
Regards
-
- Matrix Staff
- Posts: 1464
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 514 times
- Been thanked: 474 times
Re: EB083 Port A
Hi Iain.
My apologies, I uploaded the wrong file.
Attached should be the updated version.
My apologies, I uploaded the wrong file.
Attached should be the updated version.
- Attachments
-
- ComboBoard.fcpx
- (10.94 KiB) Downloaded 36 times
Martin
-
- Valued Contributor
- Posts: 1183
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 289 times
- Been thanked: 417 times
-
- Valued Contributor
- Posts: 1183
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 289 times
- Been thanked: 417 times
Re: EB083 Port A
Hi
Just to be clear, I'm using v10 with an EB006-30-9 programmer and EB083 combo. It's not to hand so I think it's the EB083.
It's only v10 that has an issue.
I opened up a previous (v8) chart in v10, made a couple of changes and had the issues described. With the new component, I deleted the existing combo then re-placed it, then recompiled but the problem remains.
I'll try creating a new chart with the new component when I'm next beside it.
Regards
PS
It's in hardware, not tried simulation.
PPS
Just tried in Sim, it works. Doesn't using a 16F1939 in the programmer/combo
Just to be clear, I'm using v10 with an EB006-30-9 programmer and EB083 combo. It's not to hand so I think it's the EB083.
It's only v10 that has an issue.
I opened up a previous (v8) chart in v10, made a couple of changes and had the issues described. With the new component, I deleted the existing combo then re-placed it, then recompiled but the problem remains.
I'll try creating a new chart with the new component when I'm next beside it.
Regards
PS
It's in hardware, not tried simulation.
PPS
Just tried in Sim, it works. Doesn't using a 16F1939 in the programmer/combo
-
- Matrix Staff
- Posts: 1464
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 514 times
- Been thanked: 474 times
Re: EB083 Port A
Hi.
I have just tried using EB083 & EB006 with 16F1937 and the hardware is working as expected.
The only thing I have spotted with Flowcode simulation is the background of the quad 7seg component was invisible, so I have just sorted that out.
I have just tried using EB083 & EB006 with 16F1937 and the hardware is working as expected.
The only thing I have spotted with Flowcode simulation is the background of the quad 7seg component was invisible, so I have just sorted that out.
Martin
-
- Matrix Staff
- Posts: 1756
- Joined: Mon Dec 07, 2020 10:06 am
- Has thanked: 446 times
- Been thanked: 606 times
Re: EB083 Port A
Good morning Chipfrier,
Would you mind sending us your project and generated .C file so we can investigate further.
Would you mind sending us your project and generated .C file so we can investigate further.
Regards Ben Rowland - MatrixTSL
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
-
- Valued Contributor
- Posts: 1183
- Joined: Thu Dec 03, 2020 10:57 am
- Has thanked: 289 times
- Been thanked: 417 times
Re: EB083 Port A
Hi Ben
Further info
Previously I was using my laptop running W8.1 with FCv8, 9 and 10 for the tests, results as above.
Today, using my W10 machine running FC10 I get a different result when using Martin's component.
I'm using a EB006-00-09 and an EB083-00-1 with a 16F1939 installed.
I created a new chart. This prints out blah blah on display then loops until Port A/2 is pressed. During the loop it displays the value of the variable used to read the switch. First time I included that.
In simulation the board suggests a key has been pressed but no value is returned.
In hardware looping around I get a value of 56 displyed which would indicate Port A2-A5 are pressed (they are not). Pressing any button makes no difference to the value. A0-A1 are set as digital and crystal is on A6-A7.
Pressing the buttons on the board illuminates the associated LEDs.
Regards
Further info
Previously I was using my laptop running W8.1 with FCv8, 9 and 10 for the tests, results as above.
Today, using my W10 machine running FC10 I get a different result when using Martin's component.
I'm using a EB006-00-09 and an EB083-00-1 with a 16F1939 installed.
I created a new chart. This prints out blah blah on display then loops until Port A/2 is pressed. During the loop it displays the value of the variable used to read the switch. First time I included that.
In simulation the board suggests a key has been pressed but no value is returned.
In hardware looping around I get a value of 56 displyed which would indicate Port A2-A5 are pressed (they are not). Pressing any button makes no difference to the value. A0-A1 are set as digital and crystal is on A6-A7.
Pressing the buttons on the board illuminates the associated LEDs.
Regards