I think I may be going a wee bit potty.....

 

I think I'm going nuts.

 

In this case, last night I was having a problem with a Pic chip.

 

I'd changed the output pin for one of the serial communication modules. nothing flashy, done it before.

 

 The problem was, it appeared to be giving an inverted output on the original pin as well....

 

 

 

 

 

Yellow trace is the output I want, red trace is the old pin - Inverted output right?

Weird right? 

 

I couldn't find any reference to it anywhere, so several hours later I give up and go to bed.

 

 

This morning, I rock up with a cuppa... I turn everything on.

 

That's it.

Nothing else.

 

 

It's bloody working.

 

 

We ain't dead!

 

 

Nope, we’re still here and kicking around, despite having a "smal"l break over the 2^nd half of last year – though I think given the year it was…. It’s hardly a surprise

 

Still, development has been going ahead now, Oled display drivers are working

 

And Bluetooth based comms are up and running, as is development on pc based sections as well… once I’ve wrapped my head around GTK+ toolkit for the Gui side of things. (That has the added advantage of working with both Linux and Windows unlike some of thither gui tools).

That’s especially handy now I’ve finally been able to move all the development tools to a Linux platform (My preferred OS for many years now) 

 

 The only disadvantage is the Hantek oscilloscope software, while working perfectly well is a little harder to make out parts of the display. Still, that’s a minor issue, soon to be solved with the purchase of a spanky new ‘scope for myself

 So yeah…. While this time last year we had tentative plans to be showing something at LarpcCon 2021…. Circumstances have conspired to kinda shoot that down Current (tentative)  plans are to have something spanky put together for LarpCon 2022

 

We shall see.

Post Larpcon comedown

Well...

It's been a little while since LarpCon and in all honesty - I think it went well, it was certainly interesting for networking and spreading awareness.

The only real issue was it felt like the venue is getting a little small for it, and it was only a month until the next game - we were advising that we are planning on running next year as well. Mind you, the next game has now been postponed until December...

Equipment wise, lots of chats. Including some around using an Android app as the medic/ref boxes, which I've looked into and it's either a lot of faffing to get the sensors/emitters to communicate via USB protocols, plus costs to just sign up to the Android store so that apps may be downloaded. Overall it's been given up as a not-economically-viable-at-the-moment option.

What I am going to do for the sensors is enable them to receive the information from medic/ref boxes via IR or possibly via an additional UART module that uses usb sockets and cables to connect to the  boxes,  but not using USB protocols, just a handy, readily available connector set and add a small, relatively cheap Oled display. It's just a matter of finding a suitable PIC chip and sitting down to figure out and code.

The emitter ciruits are going to get the option for a similar usb socket to enable them to be updated via ref boxes to different damage/damage types - I'm picturing this more for Crew kit to give maximum flexibility for the circuits.

There was also talk around adding a nextion touchscreen to the sensors as I've found a source for reasonable sized ones for about a tenner each. BUT that's still adding a tenner plus to the cost of each sensors, along with higher current requirements for the battery. So that has gone out the window :)

However, a touch screen display for the Medic/Ref boxes on the other hand.... That's a thing that can be done, as can a small display for the sensors as well.

LarpCon definitely helped get the creative juices flowing and kick me out of the little bit of a funk I'd gotten in around the Arcturus gear.

Additionally there has been a rather handy video from Larpcon posted:

If you fast forward to 02:54 then the kit may look and sound familiar :)

Time flies & Larp-con

Oh blimey......

Where does time go?

Still ,nothing much to update as yet, though I will be at Larp-Con 2020 this coming weekend .

Come find me - I'll be in with the promoters - Look for Starlore/Babylon 5: Call of light and I'll have some of the basic level kit with me :)

Come & Find us!

TTFN

New sounds....

So. I’ve recently worked out how to get an alternate audio module working for the various circuits.

But Why? I hear you asking(1)

Simples.

Cost.

The previous circuits used the DFplayer audio module. Which work out at a round a little over £1 each, depending on the exchange rate. The new modules, cost a little bit more, but not by much.

HOWEVER. The new modules have onboard Flash Memory whereas the DFPlayer modules use microSD cards. Which increase the cost substantially. It’s fine when your making just one or two things, but the last big project for Babylon 5 earlier this year, needed around 50 audio modules. That’s a LOT of extra money to find.

The only possible concern is the capacity of the flash memory – I’ve not fully checked out how much it can hold yet. They are also slightly larger, and a different pin layout which is more of an issue when working with Veroboard, as when I get the professionally made boards designed and sorted they are a lot easier to fit on. Even if it’s looking like I’ll have to do the design work and layout for the module myself for using in EAGLE PCB software (straight forward enough as I can start of with the DF player and edit it)

So, along with the change to Pic chips, the new audio modules with drastically lower the basic cost of emitter or sensor circuits by a good £3-£6 each.

I’ve not done the full working out yet, but I’m hoping, when everything is finally ready and released open source, to also be able to offer pre-programmed Pic chips, or Pre-flashed sound modules as well as professionally etched boards, and fully assembled boards for as close to £10-£15 each as possible for the emitters and whatever it works out at for the sensors.

Essentially, as well as the plans and both hex files and code to build the things to be able to offer kits, or pre-built circuits that just need the various buttons and speakers attaching (I’m thinking of including the Emitters, as the ones I use, weirdly have the legs setup so that positive/negative are indicated the opposite way round to pretty much every other LED I’ve seen… Or at least, pre-wired emitters with the traditional red/black for positive/negative.

But that’s for the future. In the meantime, the only separate thing I need to sort out for the pic circuits, before smooshing it all together in the code is counting the pulses to check the frequency….

And I’d have had that done by now if I wasn’t waiting for new IR receivers to arrive(4)

1: I do…. I can hear EVERYTHING(2)

2: Or I may just be overtired and having audio-hallucinations.. Hey-ho

3: Normally, positive is on the longer leg, negative on the shorter… Not on these puppies.. Oh no….

4: So, it turns out, that if you accidentally wire the +ve and -ve on an IR receiver backwards on your development breadboard and blow it… It’s a good idea to correct the wiring before going “Oops” and just replacing the blown one with the last one you’ve got in the house…..

Another nail in the Picaxe sensor's coffin...

More work done on migrating the circuits to Pic this weekend in between watching the Rugby World cup and Ghostbusters 35th anniversary…

 

I was originally planning on having pic and picaxe development running concurrently and releasing both open source as Picaxe use Basic.

However a snag has been found.

 

Picaxe has two commands for dealing with reading serial data SERIN and HSERIN. SERIN enables serial communication on pretty much any pin. HSERIN uses the hardware of the underlying pic. There is a difference between the two – Over the weekend, I was working on constructing the signal – having got the baud rates set and the timings sorted down to the millisecond (Well… nanosecond pretty much) The Legacy side of the hit works fine. The problem is the SEROUT/SERIN command for output/input – the actual length of time it takes to send the serial data is longer than the equivalent from the Pic, or from HSEROUT.

This in itself isn’t too much of a problem, apart from when it comes to reading the signal. SEROUT creates a much longer serial code than the hardware equivalent. Meaning that a sensor as they currently stand, cannot read the serial data part of the signal if it has been generated by a PIC. I think this can be mitigated by changing from SEROUT/SERIN to HSEROUT/HSERIN to use the underlying pic hardware.

 

But, given the other limitations of the Picaxe based sensors, I just cannot be bothered to faff around with something that I already know won’t be able to handle everything I want it to.

Changing the Picaxe based sensors to Pic is straight forward enough – I’ve got to reprogram the chips back to their underlying pic chip (Programming a Picaxe as the underlying Pic removes the Picaxe bootstrap/compiler from the chip) swap two pins around on the hardware – which should be basically move 1 wire and 1 resistor – all it’ll cost is 1 resistor unless I get lucky with the leg length, but that’s not really an issue to worry about.

 

It is essentially another nail in the coffin of the advanced Picxe based sensors 😊

 

The whole project would be even easier if I wasn’t also trying to make sure that Legacy WoW kit worked with it as well, as in that case I’d change the signal to a relatively straight forward serial data stream and get rid of the 1800hz 50ms hit frequency. BUT I am, so I’m not 😊 )

PIC'ing the chips :)

Well, PIC migration has started in earnest now…

 

Following a few setbacks…..

Bit of a pain when the programmer you have is no longer supported.

More of a pain when the new programmer doesn’t have one of the useful features of the old one – I’ve moved to Pickit3 programmer from Pickit2. The only drawback I’m finding is that the Pickit3 programmer does not seem to have the capability to act as a serial communication interface – by which I mean with the Pickit2 (and picaxe cables) you could use them to communicate with a terminal program on the PC so you could see the results of serial output, or simulate a serial input – which was rather useful.. actually.. fairly critical in being able to get the serial communication part of the Arcturus signal working. It’s also useful in seeing what is being sent to the audio modules to ensure the correct commands are being sent.

I can’t do that with the Pickit3.

Bugger.

I CAN get a usb-serial interface doohickey that will let me do that and that should be arriving tomorrow all being well. Even though it’ll mean an extra thing cluttering the workbench – But that’s a definite 1^st world problem 😊

Once that arrive I’ll be able to figure out what I’m doing wrong with the serial signal at the moment and get it sorted. Then after that all I need to do is internally modulate the signal and the hardware side of the migration is sorted – It’s just a case of writing the code to slot it all into.

YAY 😊

 

HOWEVER…. Yeah.. There is always a however ain’t there 😊

 

What I CAN’T do (at least for the emitter circuits) is a pin for pin replacement of Picaxe for Pic.

Why? Well, it seems that for some of the functions of the processor, rather than using the hardware modules on the underlying Pic, the Picaxe uses software equivalents.

For example: Interrupts

Interrupts are useful little things that enable you to tell the processor that something has happened and to well.. interrupt what it’s doing and deal with it. This is useful for things like detecting button presses or incoming signals (Y’know… nothing much.. just something that makes up most of what I want 😊 ).

Now, the Picaxe 14M2 chip I use has external interrupts (for button presses) available on pins 5,6 & 7. The underlying Pic chip (16F1825) has external interrupts on PortA – that is, pins 2,3,4,11,12 & 13 – While this is handy as I need more interrupts, it’s a pita – not a HUGE pita as it’s a  minor change going forwards. The biggest problem is the sensors – Luckily the interrupts on the pic used in the sensors are fine – the possible issue with those is the signal input/reading may need to change pin. Handily though if that’s the case, the sensors boards are modular so it’s not too much to change them out (at the cost of some Veroboard, couple resistors, IC chip socket and some soldering).

It’s a similar case with the serial comms, the Picaxe has it on a number of the pins, but the Pic there are a choice of 2 pins – and one of those is the one that will output the modulated signal so that narrows it down even more. The Picaxe has a dedicated command to output/input via the same pin as the Pic.

 

Still. Things are coming along steadily, and given that the Picaxe chips were initially intended as a teaching/learning tool, they have certainly done that, as if I’d have gone straight into the Pic development, I wouldn’t have known where to even begin so in that respect they have been perfect.

 

But it’s time to move on.

Mind you, it also helps that the Pic chips are slightly less than half the price of the Picaxe based on them 😊