Issue tracker for sabre support

Looking at touche.h, line 65 (as of Jun 13th commit), the double touch time is set to 300ms. Above in the comments, it is explained that there is ~260ms of processing time when both tips are pressed. For clarification, does this mean that the system cannot meet the rules timing requirements to distinguish between a single touch or double touch due to processing/communication delays?

I am also wondering what are good methods to measure these timings across the whole system given the various factors?

Hello. I was to use an automated scoring system for my Boffer Combat.

The main things I can think of is that Boffer Combat has many opponents at one and multi hit locations.

Would I just have change the software to track more that 2 combatants then to change the hardware to add multiple lamè connectors?

Edit: correct epee to lamè

Are the program and assembly instructions updated to accommodate saber and foil?

Hi,
I've been trying to familiarise myself with the project code while I await the arrival of parts to make it.
In the process I think I may have spotted a typo in the show_hits function.
Line 113:
else if (action_player2 == ActionManager::VALID_HIT)
I think should be
else if (action_player2 == ActionManager::INVALID_HIT) ??

PS: I'm really enjoying learning about this project - you are doing great work!!

Pro:

• makes the assembly faster and easier (for some)
• cheaper bill of material
• smaller pcb
• use of ATMEGA328P directly, no useless components (like arduino's led , buttons or usb driver)

Cons:

• makes the assembly harder (for some)

Hi,
Big fan of the project! I was also thinking of developing a system, but this is great. While researching the issue of detecting guard hits (talking epee specifically), the question has been posed multiple times, without a good answer besides capacitive sensing, which has its obvious drawbacks.

According to this thread, https://forum.arduino.cc/t/wireless-fencing-scoring-system-detecting-a-pwm-signal-without-common-ground/686963 the patent for true wireless systems uses PWM detection to discriminate against grounded hits. Now, the issue is that without a common ground, floating detector pins will give a lot of false negatives.

But, doing further investigation (reply nr 8 here https://www.avrfreaks.net/forum/communication-wout-common-ground) 100kHz and up signal could be detected reliably.
I believe with some care it's possible to use Arduino as a signal generator to drive 100kHz PWM signal to grounded surfaces and detect it with the depressed point. I'll try and experiment with this to confirm I can detect PWM without a common ground.

Your thoughts?

Hi @Yohannfra

Firstly what a great project. This is something I have tried to implement myself over the years and I am excited to see that you have solved some of the problems I encountered. I would be keen to hear how you solve them.

On target sensing for foil? How did you manage this, was it with the capacitive sensor on the attacking fencer?

Then the timing between the 2 fencers, particularly lockout. How do you synchronise the 2 clients and then ensure that if an NRF packet is lost and needs to be re transmitted that it doesnt mess with the timing? Do you put a time stamp in the packet that is synced to the client clock?

Again, awesome project. I am keen to collaborate if you are interested to take this further.

Regards

W (Author of https://github.com/wnew/fencing_scoring_box)

For now each device is powered with 3xAA alkaline batteries, maybe a 3.7v lipo rechargeable battery would be better.

Pro :

• rechargeable
• open the road to arduino pro mini 3.3v (Logic level shifter will be needed for the neopixel)
• makes all the boxes smaller and lighter

Cons:

• Need to recharge the devices
• Lipo batteries are more expensive than AA alkaline batteries

Hello Yohann and first of all, congrats for this great project!

everything is fine now! again, good job for this terrific project!

Hi there,

Very cool project and I'm interested in knowing more. I'm wondering if you have some research material to tackle this project. Feel free to contact me by dropping me an email [email protected]

This would allow for a much better control of the volume

Hello, I recently did a project for my graduation in Eletrotecnic Engineering but my capacitive sensor sometimes works, sometimes not. I'm interested in your capacitive sensor, does it always work without any problem?
Thanks

Hi @Yohannfra,

I have been looking at this project and love what you have done. I am the author of the https://github.com/wnew/fencing_scoring_box.

I have been upgrading and creating a couple of PCB designs for my design and would like to collaborate. Would you be interested in having a chat sometime?

Regards

Wes

I've built the boxes and checked that they are working by enabling debug mode. I'm able to see messages between the client and server, and it seems like epee touches work. Unfortunately, they also trigger on the bell guard. Is the capacitive sensor supposed to detect the bell guard and disable the signal?

Also, I'm not sure foil is working correctly, and it seems like the pins might be mixed up. Normally, the middle pin on the foil body cord carries the voltage up the wire in the weapon; however, the voltage seems to be on the alligator clip instead. Can you explain how the pins are intended to work with this system? I only get foil touches if I connect the weapon (not the tip) to the alligator clip--not if I press the tip.

Thanks!