Changing device ID returning errors

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

capture.PNG

00_LEDWALL_SCRIPT4.py (519 Bytes)

capture 4.png

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

Capture 5.PNG

···

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

00_LEDWALL_SCRIPT3_(working).py (458 Bytes)

···

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

Will take a look tonight when I’m back at said Windows machine :slight_smile:

···

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly tom@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

received_462688164261174.png

···

On Thu, 3 Jan 2019, 13:29 Adam Haile <adammhaile@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly tom@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Interesting… that will definitely help debug. But unfortunately Windows doesn’t always give the same device the same COM port number after reboot… which is why the ID system exists.
I’ll see what I can find tonight.

···

On Thu, Jan 3, 2019 at 7:34 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

On Thu, 3 Jan 2019, 13:29 Adam Haile <adammhaile@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly tom@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Is there any fix on the com port issue?

···

On Thursday, January 3, 2019 at 1:36:56 PM UTC+1, Adam Haile wrote:

Interesting… that will definitely help debug. But unfortunately Windows doesn’t always give the same device the same COM port number after reboot… which is why the ID system exists.
I’ll see what I can find tonight.

On Thu, Jan 3, 2019 at 7:34 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

On Thu, 3 Jan 2019, 13:29 Adam Haile <adamm...@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly t...@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

I’ve not been able to reproduce it yet on my end. Still working on it and will try a couple more things this evening.

···

On Mon, Jan 7, 2019 at 7:11 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Is there any fix on the com port issue?

On Thursday, January 3, 2019 at 1:36:56 PM UTC+1, Adam Haile wrote:

Interesting… that will definitely help debug. But unfortunately Windows doesn’t always give the same device the same COM port number after reboot… which is why the ID system exists.
I’ll see what I can find tonight.

On Thu, Jan 3, 2019 at 7:34 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

On Thu, 3 Jan 2019, 13:29 Adam Haile <adamm...@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly t...@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/62ce409d-ec7c-481e-969e-86813e457fc7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Ok… bad news. It’s a bad bad bug that we missed. And it’s been broken for quite a while -> https://github.com/ManiacalLabs/BiblioPixel/issues/1126

Which mostly means that you are the first to use that feature in nearly 2 years.

Honestly, all I can suggest at the moment is to use BiblioPixel v2 -> https://github.com/ManiacalLabs/BiblioPixel2
At least until the issue is patched.

···

On Mon, Jan 7, 2019 at 7:17 AM Adam Haile adammhaile@gmail.com wrote:

I’ve not been able to reproduce it yet on my end. Still working on it and will try a couple more things this evening.

On Mon, Jan 7, 2019 at 7:11 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Is there any fix on the com port issue?

On Thursday, January 3, 2019 at 1:36:56 PM UTC+1, Adam Haile wrote:

Interesting… that will definitely help debug. But unfortunately Windows doesn’t always give the same device the same COM port number after reboot… which is why the ID system exists.
I’ll see what I can find tonight.

On Thu, Jan 3, 2019 at 7:34 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

On Thu, 3 Jan 2019, 13:29 Adam Haile <adamm...@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly t...@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/62ce409d-ec7c-481e-969e-86813e457fc7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Alfred, I’d need to see the actual animation code you are running. Some animations just don’t run quickly. I might be able to give you some tips to optimize your code.

···

On Wed, Jan 9, 2019 at 4:50 AM Tom Swirly tom@swirly.com wrote:

Ah, sorry, I didn’t see that this was addressed just to me!

First, we have a fix for the original issue.

Unfortunately, we got held up on pushing that fix because of an unrelated problem in the continuous integration system that :-/ almost certainly we didn’t cause. https://github.com/ManiacalLabs/BiblioPixel/issues/1130

But we’ll get this in today, if we have to ignore the bogus warnings from the system to do so!

As for the framerates - not entirely sure what’s going on there! Adam?

On Tue, Jan 8, 2019 at 12:13 PM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Thank you for the support. So far were getting by with defining the ports manually on windows. Using the pi it finds them automatically. The issue were running into at the moment is that we are trying to run 2494 leds using 4 all pixels and were getting low framrates (9fps). When running half of it using 2 all pixels its at around 20fps but when we add the other 2 drivers with around 600 leds on each it drops. When using 4 drivers to run only half the leds it still remains at 20fps when it should have ran at sround 40. On the pi we get around 4 fps and when we use threaded update the prompt prints that its acheiving around 18fps but it doesnt output properly to the matrix but on the pc it seems to work at 30 fps using threaded update. While trying to use anim.run on a new thread the join thread variable cannot be found and setting threaded to true seems to run the script and then exits. Any idea what we could do to increase the framerate?

Thanks and regards

On Tue, 8 Jan 2019, 10:14 Tom Swirly <tom@swirly.com wrote:

The fix probably isn’t so terrible - we can likely get it out pretty fast.

On Tue, Jan 8, 2019 at 5:23 AM Adam Haile adammhaile@gmail.com wrote:

Ok… bad news. It’s a bad bad bug that we missed. And it’s been broken for quite a while -> https://github.com/ManiacalLabs/BiblioPixel/issues/1126

Which mostly means that you are the first to use that feature in nearly 2 years.

Honestly, all I can suggest at the moment is to use BiblioPixel v2 -> https://github.com/ManiacalLabs/BiblioPixel2
At least until the issue is patched.

On Mon, Jan 7, 2019 at 7:17 AM Adam Haile adammhaile@gmail.com wrote:

I’ve not been able to reproduce it yet on my end. Still working on it and will try a couple more things this evening.

On Mon, Jan 7, 2019 at 7:11 AM alfred spiteri hili alfredspiterihili@gmail.com wrote:

Is there any fix on the com port issue?

On Thursday, January 3, 2019 at 1:36:56 PM UTC+1, Adam Haile wrote:

Interesting… that will definitely help debug. But unfortunately Windows doesn’t always give the same device the same COM port number after reboot… which is why the ID system exists.
I’ll see what I can find tonight.

On Thu, Jan 3, 2019 at 7:34 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Update: we managed to force it to connect by defining the com ports it needs to connect to before looking for the id and trying to find the com automatically. We added for example dev=com9

On Thu, 3 Jan 2019, 13:29 Adam Haile <adamm...@gmail.com wrote:

Will take a look tonight when I’m back at said Windows machine :slight_smile:

On Thu, Jan 3, 2019 at 5:01 AM Tom Swirly t...@swirly.com wrote:

Hmm, you do seem to be getting some sort of legit communications error with the new code… but unfortunately I personally don’t have a Windows machine to test it on to reproduce the issue.

BP does support multiple devices and it should go much as you are indicating.

Adam will be on later and has the ability to test multiple devices on Windows, so let’s see what he says!

On Thu, Jan 3, 2019 at 10:40 AM alfred spiteri hili alfredsp...@gmail.com wrote:

Just to add we are able to connect them and run them separately using a modified code of the original posted one. attaching it here

On Thursday, January 3, 2019 at 10:26:00 AM UTC+1, alfred spiteri hili wrote:

Okay so just realised the new release of bibliopixel came out and that fixed the device id changing problem however we still are having a problem running the previously attached script. It is now returning the error attached.

On Thursday, January 3, 2019 at 10:12:33 AM UTC+1, alfred spiteri hili wrote:

Hi All,

I was wondering if you could help me with an issue I am having while trying to use multiple all pixels together as a strip.

The first problem I am running into seems that bibliopixel cannot find the devices listed in the script (for example driver A being device 0 and driver B being device 1)

This I imagine is because they all come with a device ID of 0 out of the box and it runs into problems when there is more than one device with the same id.

When I try changing the device id using " Bp Devices" or “bibliopixel devices” or “bp -v devices” it keeps returning this error: “Programmer error with exception can’t concat int to bytearray”

Ive attached the script we are trying to run and a picture of the outcome aswell.

Any Ideas of what might be happening as we kind of ran into a wall here?

Thanks!!

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/ba0d76a5-ef2a-41be-91b8-bf6259d7e174%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAOuQWfWLtff6R%3DJ6Nkjug6wEZ%2B_TMHr4jDf%2BCYUDGsZ5naXEZg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/62ce409d-ec7c-481e-969e-86813e457fc7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups “Maniacal Labs Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to maniacal-labs-users+unsubscribe@googlegroups.com.

To post to this group, send email to maniacal-labs-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/maniacal-labs-users/CAG8g-TYbJaKicPK5k7eOH%2B7z0P5RxKb-FheG4fOJHVA1pPGi2A%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.


/t

https://tom.ritchford.com

https://tom.swirly.com


/t

https://tom.ritchford.com

https://tom.swirly.com